Stata/se 8 Console For Mac
Dear Statalist, I have ~50GB tab delimited.txt file and I'm having trouble with importing it to Stata. Stata keeps crashing after 10-15 mins. The dataset has ~20 vars and ~1.2 billion observations.
Gabriel I found this very useful for text cleaning. You can use them even if you can’t code perl yourself, for instance to transpose a dataset just download “transpose.pl” script to your /scripts directory and enter the shell command: perl /scripts/transpose.pl rowcol.txt colrow.txt The transpose script is particularly useful to me as I’ve never gotten Excel’s transpose function to work and for some bizarre reason Stata’s “xpose” command only works with numeric variables. You can even use these scripts from directly in a do-file like so: tempfile foo1 tempfile foo2 outsheet using `foo1'.txt shell perl /scripts/transpose.pl `foo1'.txt `foo2'.txt insheet using `foo2'.txt, clear. Gabriel Yesterday I attended the ATS workshop on the in Stata 11.
Despite the usual statistical usage of the word “factor,” this has nothing to do eigenvectors and multi-dimensional scaling but is really about dummy sets and interactions. I might still be missing something, but it seems like the factor variables syntax is only an incremental improvement over the old “xi” syntax, mostly because it’s more elegant. However the margin command is really impressive and should go a long way to making nonlinear models (including logit) more intelligible. I think a big reason people have p-fetishism is because with a lot of models it’s difficult to understand effects size. For this reason I like to close my results section with predicted values for various vignettes. I had been doing this in Excel or Numbers but “margin” will make this much easier, especially if I continue to experiment with specifications. (In general, I find that if you’re doing something once, GUI is faster than scripting, but we never just do something once so scripting is better in the long run).
Anyway, it’s a very promising command. My only reservation about both “factor variables” and “margin” is the value labeling. First, (like “xi”) neither command carries through value labels so you have to remember what occupation 3 is instead of it saying “sales.” Second, the numbers aren’t even consistent between factor and margin. Internet explorer download for mac. Factor shows the value of the underlying variable whereas margin numbers the categories sequentially.
So for instance, your basic dummy would be “0”for no and “1” for yes in factor variables because that’s how it’s stored in memory and “1” for no and “2” for yes in margin because “no” is the first category. What is this, SPSS? Anyway, margin is a very useful command, but it would be even more useful if the command itself or some kind of postestimation or wrapper ado file made the output more intuitive. Not that I’m volunteering to write it.
Help us Ben Jann, you’re our only hope! Gabriel I just realized that Stata SE/MP includes the console version of Stata. Since the Stata GUI adds only about 15 or 16 megs of RAM and a comparably light load to the CPU, it doesn’t really improve the performance that much for most things, but I still thought it was pretty cool in a dorky ASCII art kind of way. The only place where I notice a substantial performance jump is with one do-file that generates hundreds of graphs (and saves them to disk) — not only is console mode much faster but it’s less distracting as graphs aren’t constantly popping up. To invoke console mode on a mac, go to the terminal and write: /Applications/Stata/StataMP.app/Contents/MacOS/stata-mp To get the GUI you’d do the same thing but change the last bit to “stataMP” (note the case-sensitivity).
On Aug 3, 2010, at 4:01 AM, Francesca Fabbri wrote: I use STATA 11 on my Mac and I have a problem. On Windows I can open several STATA sessions (to look at different data sets) simultaneously, but I haven't worked out how to do it on the Mac. Does anybody know?
Two comments. First, Stata's paradigm is to have one dataset in memory at any given time. Launching multiple instances of GUI Stata just so you can view multiple datasets at once is really just a kludge to mimic a hypothetical Stata where you could have multiple datasets in memory at once, and view them simultaneously.
Of course, what you'd really want to be able to do is to have access to both datasets from the same process, which this kludge wouldn't permit anyway. So, working within the Stata paradigm, if you want to view both datasets (in Stata) together, you should first bring them together (i.e., via - merge-, -append-, etc.). Second, OS X works hard to keep you from running multiple instances of its GUI applications. Doing so is confusing, and can cause problems (e.g., as multiple copies of the same application try to access and/or modify the same configuration files, cache files, etc.). It simply isn't the way the Finder was designed. Mac development has always emphasized using multiple windows within the same instance of an application rather than running multiple instances. That said, in the spirit of full disclosure, you can launch multiple instances of GUI Stata on OS X by using open with the -n switch.
Stata/se 8 Console For Mac Free
For example, on my machine open -n /Applications/Stata/StataSE.app (you might have to modify the path, depending upon which version of Stata you have installed, and where it is installed). I believe this should be fairly safe (the most you might do is corrupt your preference file(s)), but can't guarantee it. Note that I would strongly suggest finding another approach.
For example, if your dataset(s) are small and you want to look at them side-by-side, open one in Stata and the other in a text editor, or perhaps a spreadsheet program. You can also summarize both datasets using -codebook-, -inspect-, etc., write these to separate log files, and then open the logs side-by-side. Finally, if you're really doing a lookup type of operation between the two datasets, then this would likely be more efficient if you merge the two together into a single dataset.
Stata/se 8 Console For Macbook Pro
What I've said above applies only to GUI Stata, of course; running multiple instances of console Stata or multiple batch jobs is a perfectly reasonable thing to do. For searches and help try:.