James Van Buskirk <not_valid@comcast.net> schrieb:
> "David Jones" wrote in message news:tkr3gq$nkk$1@gioia.aioe.org...
>
>> > James Van Buskirk wrote:
>> > However, this caused a problem because the last and of
>> > course most important *.ppm doesn't complete writing
>> > before its thread closes, so I don't get that *.ppm file.
>> > I tried putting a FLUSH(iunit) statement before the
>> > CLOSE(iunit) statement, but still no joy. How am I
>> > supposed to tell the thread to wait for the *.ppm file
>> > to get properly written and saved before returning?
>
>> Have you tried a WAIT or SLEEP function to provide the required delay
>> of a small faction of a second, as judged by experience?
>
> Yeah, that's the first thing I plan to try when I get the
> resources (time and energy) to struggle with this problem
> again.

Another possibility: Have the writing thread open the file under
another name, and upon completion, rename it to the final name
(using the non-standard RENAME function or subroutine).

The other thread can then INQUIRE for the existence of
the file in a loop, possibly with a SLEEP thrown in.

> "Thomas Koenig" wrote in message
> news:tktvdu$3amf6$1@newsreader4.netcologne.de...

> James Van Buskirk <not_valid@comcast.net> schrieb:
> > "David Jones" wrote in message news:tkr3gq$nkk$1@gioia.aioe.org...

> >> > James Van Buskirk wrote:
> >> > However, this caused a problem because the last and of
> >> > course most important *.ppm doesn't complete writing
> >> > before its thread closes, so I don't get that *.ppm file.
> >> > I tried putting a FLUSH(iunit) statement before the
> >> > CLOSE(iunit) statement, but still no joy. How am I
> >> > supposed to tell the thread to wait for the *.ppm file
> >> > to get properly written and saved before returning?

> >> Have you tried a WAIT or SLEEP function to provide the required delay
> >> of a small faction of a second, as judged by experience?

> > Yeah, that's the first thing I plan to try when I get the
> > resources (time and energy) to struggle with this problem
> > again.

> Another possibility: Have the writing thread open the file under
> another name, and upon completion, rename it to the final name
> (using the non-standard RENAME function or subroutine).

> The other thread can then INQUIRE for the existence of
> the file in a loop, possibly with a SLEEP thrown in.

Given that the 'right' solution is asynchronous I/O and that
I have a workaround with Sleep, I have put this issue on the
backburner for now.

At this point the graphics isn't too bad if you consider the
lack of Greek characters and subscripts in the axis labels
and title, so I am back to the calculational component.
I am trying to determine whether I need arbitrary
precision and how much good it will do me. The present
limit seems to be due to an ill-conditioned Jacobian in a
context where another approach may be able to make
forward progress.