Stata is clunky with time series analysis. You will be routinely forced to run for example panel LR heteroskedasticity test on random subsamples even with the most expensive edition.Ĭreating beautiful graphics in Stata is nearly impossible - now don’t get me wrong you can make some decent graphics in Stata but it pales in contrast to what you can do with Python or R. Stata has some serious limitations on matrix sixes even in the most expensive edition the max mat size is 11000 which is serious limit when you work with panel data and have to run some iterative model with large number of variables. Stata is a program not a language so if you want to create a new complex function you need to separately get and learn Mata (statas programming language).
If you can get it for free from uni then you probably don’t care about that but still it’s something to keep in mind. Stata is not a freeware and i don’t think that the price tag is justified given that it’s inferior product compared to free ware programs like R and Python. To be honest I don’t like stata for several reasons: When it comes to Stata I use it only for a educational purposes (I teach econometric tutorials at university). I always recommend to people around me to learn both Python and R - the difference between them is not that big and with R you don’t really need to invest heavily into programming skills but just basics and then use packages.Īlso, Jupyter Notebooks that can accommodate both R and Python make using both of them easier. Also, I prefer to use Python when I need to set up my own program as programming in Python is more natural (if that makes any sense) than in R, unless the program can be build easily from ready made functions from various packages. However, Python is far superior for web-scraping, numerical analysis and sentiment text analysis (although R has some good packages for that as well). I find also producing nice standard statistics graphics with R easier (but for maps I prefer Python). For that reason for most econometric analysis I usually default to R. The prob > chi2 gives us the probability of observing a more extreme chi2 value, and here our p-value of 0.16 indicates we won't be rejecting the null this time around -> the effect of diabetes in elevated BP vs normal BP versus stage 2 HTN vs normal BP is similar.Python can do everything that R can do and R can do everything that Python does, but I must say R is superior to Python when it comes to the packages.
We can use the test command and indicate the level of the outcome in 's.īy writing the test statement out that the values are equal to each other, we are testing the null hypothesis that they are equal, or that their difference is zero. For example, does the effect of diabetes differ when we look at elevated BP vs normal BP versus stage 2 hypertension vs normal BP? You may be interested if the effect of one covariate is the same across levels of the outcome. I've interpreted the RRR for elevated BP vs normal BP in the grey box. If you use a calculator and exponentiate the betas in the original output you'll see they match up. The output format when we run -mlogit, rrr- is the same as before, but we have exponentiated betas.