Dear Statalisters,
I have Stata SE and I have found that its quite useful to open multiple sessions of Stata to use the computing power more efficiently and thereby split up time intensive jobs (Briefly described here http://www.stata.com/statalist/archi.../msg00098.html). There are two features in this area that would be extremely useful and might exist but I did not discover them so far.
Firstly, is there a way to control the Stata sessions in my do file? For instance is there a way to tell Stata to open a new session within a do file.
Something like:
forvalues i=1/5 {
open new Stata window
start some calculations
}
So far I have done this "by hand" but is there a more efficient way?
Secondly, is there a way to stop Stata from accepting further commands? Let me explain: When doing this by hand I often executed a do file in the wrong window (a window that had already a code running) which messed up the calculations. Is there a way that I can prevent myself from doing so? I suppose one would need to get rid somehow of the command window until a job has been completed, but I did not find a way to do so yet.
Best
Stefan
I have Stata SE and I have found that its quite useful to open multiple sessions of Stata to use the computing power more efficiently and thereby split up time intensive jobs (Briefly described here http://www.stata.com/statalist/archi.../msg00098.html). There are two features in this area that would be extremely useful and might exist but I did not discover them so far.
Firstly, is there a way to control the Stata sessions in my do file? For instance is there a way to tell Stata to open a new session within a do file.
Something like:
forvalues i=1/5 {
open new Stata window
start some calculations
}
So far I have done this "by hand" but is there a more efficient way?
Secondly, is there a way to stop Stata from accepting further commands? Let me explain: When doing this by hand I often executed a do file in the wrong window (a window that had already a code running) which messed up the calculations. Is there a way that I can prevent myself from doing so? I suppose one would need to get rid somehow of the command window until a job has been completed, but I did not find a way to do so yet.
Best
Stefan
