Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • esttab and incorrect significance stars

    Hello everyone,

    My current code for esttab is not providing the wanted significance stars. I want to have significance stars at 10%, 5% and 1% level when I export to excel. Now they are at 5%, 1% and 0.1% level. I know there have been discussions on this topic.
    https://www.statalist.org/forums/for...sts-of-margins
    https://www.statalist.org/forums/for...sttab-command/
    https://www.statalist.org/forums/for...ficance-levels

    Yet, I tried to implement the code into mine but it doesn’t work. Can someone please take a look?
    I am not sure where in my esttab code I should put the option: star(* .10 ** .05 *** .01) or starlevels(* .10 ** .05 *** .01)

    My current (adjusted) esttab code looks like this:

    xtset cu month

    eststo table2_1:xtreg ri2 pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3. cashtoassets L3.dividends_complete_asstes L3.leverage2 i.month,fe
    eststo table2_2:xtreg ri2 L1.ri2 pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3. cashtoassets L3.dividends_complete_asstes L3.leverage2 i.month,fe
    eststo table2_3:xtreg RM_2 pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3. cashtoassets L3.dividends_complete_asstes L3.leverage2 i.month,fe

    esttab,table2_1 table2_2 table2_3 using table2.csv, scalars( r2_w ) keep(L.ri2 _cons pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3.cashtoassets L3.dividends_complete_asstes L3.leverage2 )


    Or is maybe trying outreg2 a better option with a fixed effects monthly panel?

    Kind regards
    philip

  • #2
    Originally posted by philip schulting View Post
    Hello everyone,

    My current code for esttab is not providing the wanted significance stars. I want to have significance stars at 10%, 5% and 1% level when I export to excel. Now they are at 5%, 1% and 0.1% level. I know there have been discussions on this topic.
    https://www.statalist.org/forums/for...sts-of-margins
    https://www.statalist.org/forums/for...sttab-command/
    https://www.statalist.org/forums/for...ficance-levels

    Yet, I tried to implement the code into mine but it doesn’t work. Can someone please take a look?
    I am not sure where in my esttab code I should put the option: star(* .10 ** .05 *** .01) or starlevels(* .10 ** .05 *** .01)

    My current (adjusted) esttab code looks like this:

    xtset cu month

    eststo table2_1:xtreg ri2 pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3. cashtoassets L3.dividends_complete_asstes L3.leverage2 i.month,fe
    eststo table2_2:xtreg ri2 L1.ri2 pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3. cashtoassets L3.dividends_complete_asstes L3.leverage2 i.month,fe
    eststo table2_3:xtreg RM_2 pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3. cashtoassets L3.dividends_complete_asstes L3.leverage2 i.month,fe

    esttab,table2_1 table2_2 table2_3 using table2.csv, scalars( r2_w ) keep(L.ri2 _cons pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3.cashtoassets L3.dividends_complete_asstes L3.leverage2 )


    Or is maybe trying outreg2 a better option with a fixed effects monthly panel?

    Kind regards
    philip
    I believe this should work:
    Code:
    esttab table2_1 table2_2 table2_3 using table2.csv, star(* 0.10 ** 0.05 *** 0.01) scalars(r2_w ) keep(L.ri2 _cons pm_2 ps_2 lagged_return_positive lagged_return_negative L3.booktomarket L3.ln_total_assets L3.cashtoassets L3.dividends_complete_asstes L3.leverage2)
    A side note is that in the journals I am familiar with, I would be more familiar with * representing p < 0.05, ** p < 0.01, and *** p < 0.001. There might be a different symbol entirely if one is adding a p < 0.1 threshold. Practices are going to differ from journal to journal, of course.
    Be aware that it can be very hard to answer a question without sample data. You can use the dataex command for this. Type help dataex at the command line.

    When presenting code or results, please use the code delimiters format them. Use the # button on the formatting toolbar, between the " (double quote) and <> buttons.

    Comment

    Working...
    X