Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Drop Coefficient Section in etable Using drop.section = "coef" #530

Open
Oravishayrizi opened this issue Nov 12, 2024 · 0 comments
Open

Comments

@Oravishayrizi
Copy link

Description:
When trying to display only fit statistics (e.g., F-statistic, RMSE) in an etable call by dropping the coefficient section, the argument drop.section = "coef" does not work as expected.

According to the documentation for drop.section:

Character vector which can be of length 0 (i.e. equal to NULL). Can contain the values "coef", "fixef", "slopes" or "stats". It would drop, respectively, the coefficients section, fixed-effects section, the variables with varying slopes section, or the fit statistics section.

Expected Behavior

The table should display only the fit statistics (F-statistic and RMSE), excluding the coefficients.

Actual Behavior
The following error is returned:

The (nullable) argument drop.section must be a character vector with values equal to 'fixef', 'slopes' or 'stats'. Problem: no match was found for 'coef'.

Minimal Working Example (MWE)

# Load necessary libraries
library(fixest)

# Create a simple dataset
data(mtcars)

# Run basic regression models
model1 <- feols(mpg ~ cyl + hp + wt, data = mtcars)
model2 <- feols(mpg ~ hp + wt + qsec, data = mtcars)

# Attempt to use etable to display only fit statistics without coefficients
etable(
  model1, model2,
  drop.section = "coef",
  fitstat = c("f", "rmse")
)
kylebutts added a commit to kylebutts/fixest that referenced this issue Feb 19, 2025
@kylebutts kylebutts mentioned this issue Feb 19, 2025
kylebutts added a commit to kylebutts/fixest that referenced this issue Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant