[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]
st: Re: running a simulation program
Justin Fenty (email@example.com) wrote
> I have a simulation program comparing two types of analysis, one of
> which is based on permutation tests. The program contains a postfile
> within a postfile and it all works fine unless I try to run large
> numbers of simulations. For example, if I try to run 1000 simulations,
> with 1000 permutations per simulation I (eventually) get a message stating:
> Error-stata exiting
> Check Results Window for filename
> Then when I click -OK- I get something like:
> 2. C:\Docume~1\jf48\LOCALS~1\Temp\ST_001iir.tmp
> 1. C:\Docume~1\jf48\LOCALS~1\Temp\ST_001iir.tmp
This error message is extremely rare. In fact, it is so rare that
I cannot recall a prior instance of a user encountering it.
What has happened is that Stata has -preserve-d the data in a
temporary file (the filename listed in Justin's output) and is
trying to -restore- it. For some reason, Stata is unable to
restore this file. This puts Stata in a very bad state, and it
refuses to proceed. Stata informs the user where it thinks the
-preserve-d dataset is stored so that the user may retrieve it if
it contained anything important, and then Stata exits.
There are several things that could lead to this, the most likely
being that due to the various things loaded into memory, Stata is
unable to re-load that dataset into memory when it thinks it should be
able to. Other possibilities are that the permissions on the
temporary directory or file have changed, that the file was somehow
erased between the time Stata -preserve-d it and tried to -restore-
it, or that some other error occurred reading the file.
Given Justin's description of the problem, I believe that allocating
a little more memory to Stata may prevent the problem from recurring.
If Justin still encounters the problem, he should contact Stata Technical
Services, as they will need to start asking him a series of questions
to further diagnose why he is receiving this error message.
* For searches and help try: