Re: [udf-dlm-develop] nasty problem 2.

[Ed S. <es...@la...>]

How utterly weird.  I've never seen that here, but perhaps it's
because Los Alamos is at 7,000 feet elevation, thus closer to
the projected IMAGE orbit.  Perhaps UDF is sensitive to that?

Ya know, I'm not entirely sure if I'm joking here or not.

What I _am_ certain of is that UDF is not designed for the
purposes we're using it.  UDF seems to like having a program
run it, and letting the OS clean up.  The IDL model, where
you sit in an active session for hours/days/weeks, is not
to UDF's liking.  

That's the explanation for the problem.  We still need to
find a solution.

You mention that you rebuilt the database.  Are you certain
that it rebuilt correctly?

Could you try mv'ing away the files 

	$UDF_DATA/IMAGE/IMAGE-1/Database/FUV*.HD.*

(don't delete them, in case something else breaks)

...and _then_ try again to rebuild the database?


If that doesn't help, could you mail me the results of

  IDL> print,udf_times(key)

...to see if there's something out-of-sequence that UDF could
be choking on?

Also, I really think we need to trace the errors returned by
file_open(), ToThisTime(), file_pos(), and so on.  If you
don't feel comfortable instrumenting the code, could you
perhaps make a tarfile of your _exact_ data tree, and send
it my way?  

Thanks,
^E

PS sorry about such a late reply.  It's been a hectic evening.