In no instance can I recall a change in the data set format occurring without there being a meaningful improvement in functionality that necessitated it. You will have to search far and wide in the world to find a person who has a more mistrustful attitude towards the ethics of businesses than I. It seems almost as if it is a strategy of planned obsolescence for older versions of Stata. I will take a note and describe this better on the support site, and perhaps will introduce a warning for large files. The fix is not easy (since fseek is used in a few places, and it seems the map structure is assuming the reader will seek to the necessary locations).Ī workaround is possible, but it's probably better to use alternative tools (read Stat\Transfer) for files larger than 2GB for now. But thank you, I take this trust as a compliment ! But importantly Stata 12 and earlier are no longer updated, so this bug will remain for those versions where it is most harmful.Īpplying -use13- to such huge datasets is a bit of a stretch, especially because it is not optimized for such volumes of data and even for smaller datasets can take into hours (depending on the machine). The bug was reproduced in 64-bit versions of Stata 12.1 and 13.0 on Windows, and interested parties may try it in Stata 14 environment. ![]() Since it takes a while to run, here are the highlights: Specifically the documentation describes that:Ĭode: do ""(64-bit Stata 13 is required for it to run, but you can change the version statement to experiment with other versions of Stata). The exact bug is in fseek() implementation in mata. Notably, if a data file is smaller than 2GB then there is never a problem.īecause -use13- is a module for Stata, any defects in Stata limit the stability of use13. ![]() It appears that a bug in Stata prevents -use13- from working correctly and the exact failure is data-dependent, which means that for different files the program will fail with potentially a different error message. Because the error message was different from what Sean has quoted I decided to investigate in more detail. In my trial -use13- was crunching the data for 1 hour and 2 minutes before it stopped with an error. It takes a while to reproduce the problem, depending on the actual data and machine performance. Which means he has either carefully read the FAQ of statalist carefully, or the use13 troubleshooting reference, or both. Sean has provided enough information about his Stata environment and the exact commands he had typed and Stata response. Sean is aware of the importance of 2GB limit, and is correct that the documentation for use13 is not restricting such a use. ![]() Sean has done search and found an earlier thread in which a problem was reported but not resolved. Sean Lambert reports an error message produced by a user-written Stata module - use13- while processing a large file produced by a 64-bit version of Stata 13.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |