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

Add option to display t-statistics instead of standard errors below coefficients #88

Closed
wants to merge 1 commit into from

Conversation

maruoss
Copy link
Contributor

@maruoss maruoss commented Sep 23, 2022

Compared to the open #78 pull request, this one takes the t statistics from the statsmodels models directly. Also, the tstats are displayed below the coefficients with e.g. "t=1.9645" instead of (1.9645). For conf. intervals and standard errors, brackets are kept.

@toobaz
Copy link
Collaborator

toobaz commented Sep 27, 2022

Thanks @maruoss . First, sorry ( @carterkd ) for not reacting #78

Then, on the t= replacing the brackets, I have no objection but I have never seen it: @carterkd what do you think? What does R/other packages do?

This said, small bug (of both PRs):

table = stargazer([something])
table.show_t_statistic(True)
table.show_confidence_intervals(True)
table

... will not show confidence interrvals. In other words, once we have two variables regulating what is shown, each command must change both. It's not nice, and I'm open to a more elegant solution, but as a temporarily solution (we'll have to change the API anyway) it's fine to just do so (changing both).

@Jiacheng-Liu
Copy link

Jiacheng-Liu commented Nov 21, 2022

I just want to pitch in here that I think an option to display t-stat is quite essential for some areas of research. In terms of display design, In my experience, I've seen two options in literature (1) put t-stat and replace std. errors altogether, (2) use squared brackets to differentiate from round brackets used for std. error (or robust t-stat). So maybe the way to go is to allow multiple designs of t-stat style, although I think option 1 is far more common.

Regardless of the reporting design, I think this is a very important feature.

@maruoss maruoss closed this by deleting the head repository Feb 6, 2024
@toobaz toobaz mentioned this pull request Jun 14, 2024
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 this pull request may close these issues.

3 participants