Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.
| From | Nick Cox <n.j.cox@durham.ac.uk> |
| To | "'statalist@hsphsun2.harvard.edu'" <statalist@hsphsun2.harvard.edu> |
| Subject | st: RE: managing updates of stata |
| Date | Tue, 1 Mar 2011 17:08:32 +0000 |
Only by keeping a complete copy of all files as of that date in one place, I believe. That is, in principle StataCorp, with you as willing -update-r can overwrite its own files within a release, so if you need to guarantee absolute repeatability, you must copy everything. In practice, it is rare that this will bite, but I don't think rare means impossible. I'm happy to be free of such worries. I like the spirit of being able to replicate everything, very much, but not to this extent. Nick n.j.cox@durham.ac.uk Argyn Kuketayev is there a document, which would describe a recommended approach on managing updates to Stata? let's say i'm developing a model using Stata. if i download the updates, it can change the results, the model coefficients etc. how would i be able to verify the results later? suppose on Jan 1st 2011 i updated Stata, regressed the model, got the coefficients, and used to report financial results for Q4 2010. Now 2 years later, the internal audit wants to verify how I got the coefficients. How would I be able to reproduce the state of Stata software as of Jan 2011? * * For searches and help try: * http://www.stata.com/help.cgi?search * http://www.stata.com/support/statalist/faq * http://www.ats.ucla.edu/stat/stata/