On Thu, 1 Feb 2007, Mark Taylor wrote:
> On Wed, 31 Jan 2007, Brad Cavanagh wrote:
>
>> Here's one that Tim and I both remember happening in the past, but we
>> can't find any record of it, so I'm mailing with hopes that it'll twig
>> some memories.
>>
>> It would seem that FLATCOR doesn't close GLOBAL.sdf. When I run ORAC-DR
>> through a batch of files, an NDFTRACE that directly follows a FLATCOR
>> results in:
>>
>> #63 Err: !! Requested data extends beyond the end of the record; record
>> length is 8
>> # 63 Err: ! bytes (possible corrupt HDS container file
>> # 63 Err: !
>> /home/bradc/data/oracdr/reduced/uist/20060815/adam_26042/GLOBAL.sdf).
>> # 63 Err: ! HDS_OPEN: Error opening an HDS container file.
>> # 63 Err: ! SUBPAR: Failed to update GLOBAL file for parameter NDF
>> # 63 Err: !! DAT__INCHK: Integrity check
>> # 63 Err: Error in obeyw to monolith ndfpack_mon (task=ndftrace): 147358691
>>
>> If I take the FLATCOR call out, the error message disappears. Does this
>> ring any bells? We believe that FLATCOR isn't closing GLOBAL.sdf, but
>> don't want to go barking up the wrong tree.
>
> Brad,
>
> I had a conversation in Oct/Nov 2000 with Malcolm and Alan Chipperfield
> which featured some similar error messages. Seems like Brian fixed it
> in HDS, so it's probably not what's up here. However I attach some
> excerpts from that conversation to see if it looks like what you thought
> you/Tim rememberd.
There have been similar occurences twice for me too. First in 1995, second
in 1998. Each time the error went away by deleting the GLOBAL file and
then couldn't be repeated again, so where put down to some random glitch.
Could this GLOBAL file be mixed mode in some sense? Since we've recently
switched to 64bit format by default? (I'd guess not since the adam
directory looks bespoke). Is the file NFS mounted? Maybe there's a local
caching issue.
Peter.
|