I am using Robert Picard's excellent project package. I would like to keep track of the number of observations dropped while cleaning and merging my data, along with the reasons.
I know how to do the counts, but my question is how to keep track and generate a final tally.
It can be written to the logs, but then I have to manually go and extract them from the logs.
If I append them to a separate file (e.g. a text file), I will have an issue when one file that drops observations is edited and another file is not, since the non-edited file may not be re-run (if nothing it depends on is changed, which is managed by project), and the counts will get lost.
I was thinking along the line of a .dta file with a variable for each of the different drop reasons, so that the counts can each be changed individually, but this seems like a very "hacky" solution. Also, the project package doesn't seem to have a way to handle a file that will be changed by more than one do-file.
I would love to hear any suggestions.
Thank you!
Related Posts with Tracking dropped observation counts
Choosing model specification: region*time FEs vs. country-specific time trendsHello! I am trying to find the effect of drought on agricultural production using a model of the fo…
Treatment , Post Treat in case of heterogeneous treatment timingHello all, Would like to create an event study but I'm trying to make sure I'm creating treatment, …
Difference in Difference estimation on carbon emissions in STATA 17.Dear STATA community, I have some questions regarding my analysis for my DID estimation. I am looki…
changing bar color Code: local barcall upper activemonth_final if inrange(activemonth_final, `=tm(2018m6)', `=tm(2018m…
Why inlist is limited to 250 argumentsI don't have a coding issue, I have more of a query about the inner workings of Stata. I'm using a s…
Subscribe to:
Post Comments (Atom)
0 Response to Tracking dropped observation counts
Post a Comment