Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: RE: hunting for the source of an error - r(603) - Dual Core problem?

From   "David Radwin" <>
To   <>
Subject   st: RE: hunting for the source of an error - r(603) - Dual Core problem?
Date   Thu, 27 Dec 2012 09:34:21 -0800 (PST)


Maybe Stata is processing too fast for your computer to read and write the
temp files. I know I would be loathe to add -sleep- commands to slow down
a program that already takes 8 hours, but that might be the solution. See:

David Radwin
Senior Research Associate
MPR Associates, Inc.
2150 Shattuck Ave., Suite 800
Berkeley, CA 94704
Phone: 510-849-4942
Fax: 510-849-0794

> -----Original Message-----
> From: [mailto:owner-
>] On Behalf Of Ben Hoen
> Sent: Thursday, December 27, 2012 5:43 AM
> To:
> Subject: st: hunting for the source of an error - r(603) - Dual Core
> problem?
> Hi all,
> I have a relatively simple looping function that repeatedly saves and
> calls
> up temp files while looping through each case in a dataset, which, if
> successful, should take ~ 8 hours to run, though, I have yet to have it
> execute properly.  The last four times I have tried to run it will the
> full
> sample I have gotten the same error:
> "file C:\Users\Ben\AppData\Local\Temp\ST_0500000x.tmp could not be
> r(603);
> end of do-file
> r(603);"
> where x=3, 4 or 6
> Each time the error has happened on a different case.  The most recent
> three
> occurred on the 794th, 25,835th and the 20,633rd  cases (and before that
> had runs out to the 70,000 and 60,000th (or so) cases.  There are a
> of
> 166,181 cases.
> Is it something outside my code that is likely making this occur?  I am
> wondering if this has something to do with a dual-core processor.  I am
> running Windows 7- 64bit, with an Intel Duo Core E8600 - 3.33 Ghz
> processor
> with 8 GB of RAM, and am running Stata MP 12.1 for Windows - 64bit.
> that is a GUESS (and nothing more).  My thought was that this error is
> occurring when the file is in use or is stored in one processor while
> other is trying to access it?
> I have tried to force the error by running the code using many different
> subsamples and have never been able to get it to crash, and
> breaking the sample down into smaller sample somewhat defeats the
> of
> the code in the first place (which is creating nearest neighbor weights
> using, in part, geonear(SSC)).  It seems important that the error has
> occurred on a different case, potentially indicating that the problem is
> not
> with the sample.
> Any ideas?  Thank you in advance for any assistance/advice you can
> Ben

*   For searches and help try:

© Copyright 1996–2017 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index