[daip] strange DELAY error
Andrew Biggs
abiggs at eso.org
Tue Mar 12 05:15:08 EDT 2013
Hi Eric. You're right about the header being corrupted. Instead of a
256x256 image, it now claims to be a 1024x1024 image. In fact, the entire
header information for this file (facet 64 - the last) has been copied
from facet 31!
This is probably an important clue - when the data are UVSUB'd (I'm
peeling) AIPS does it in two passes, facets 1-30 and 31-64 - presumably
this isn't a coincidence. So, it is probably nothing to do with CCEDT.
I tried to recover the situation last night by renaming the corrupted file
and replacing it with a copy of a previous map of facet 64. I then copied
the CC table from the corrupted to copied file - this looks fine with
PRTCC. When I then ran UVSUB I got the following message:
UVSUB2 Task UVSUB (release of 31DEC13) begins
UVSUB2 You are using a non-standard program
UVSUB2 SETGDS: imaging done with reprojected tangent point(s)
UVSUB2 Using Clean Component source model
UVSUB2 FACSET: 0.879338 Jy found from 2553 components
UVSUB2 Create GROTHN3 .UVSUB . 3 (UV) on disk 2 cno 269
UVSUB2 QINIT: did a GET of 120570 Kwords, OFF 1772161
UVSUB2 ALGMEM field 1 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 2 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 3 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 4 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 5 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 6 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 7 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 8 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 9 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 10 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 11 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 12 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 13 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 14 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 15 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 16 Ipol gridded model subtraction chns 1- 240
AIPS 2: ** press RETURN for more, enter Q or next line to quit print **
#
localhos AIPS (31DEC13) 4003 12-MAR-2013 09:06:31 Page 3
Task messages for user 4003
UVSUB2 ALGMEM field 17 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 18 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 19 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 20 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 21 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 22 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 23 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 24 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 25 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 26 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 27 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 28 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 29 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM: at visibility number 1
UVSUB2 ALGMEM: at visibility number 200001
UVSUB2 ALGMEM: at visibility number 400001
UVSUB2 ALGMEM: at visibility number 600001
UVSUB2 ALGMEM: at visibility number 800001
UVSUB2 ALGMEM: 1024 - 0 cells, with 800104 Pts
UVSUB2 TABINI: Recovering old CC table version 3
UVSUB2 ALGMEM field 31 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 32 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 33 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 35 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 36 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 37 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 38 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 40 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 42 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 43 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 45 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 47 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 48 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 52 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 56 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 57 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 58 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 59 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 60 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 62 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 63 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM field 64 Ipol gridded model subtraction chns 1- 240
UVSUB2 ALGMEM: at visibility number 1
UVSUB2 ALGMEM: at visibility number 200001
UVSUB2 ALGMEM: at visibility number 400001
UVSUB2 ALGMEM: at visibility number 600001
UVSUB2 ALGMEM: at visibility number 800001
UVSUB2 ALGMEM: 1024 - 0 cells, with 800104 Pts
UVSUB2 Copied FQ file from vol/cno/vers 2 268 1 to 2 269 1
UVSUB2 Copied AN file from vol/cno/vers 2 268 1 to 2 269 1
UVSUB2 Appears to have ended successfully
UVSUB2 localhos 31DEC13 TST: Cpu= 3426.0 Real= 3913 IO= 17647
The "recovering old CC table version 3" is a bit strange and, looking this
morning, the copied facet 64 again has the header information from facet
31.
I'm not sure if this has ever happened on my Linux box - could this be an
external disk issue?
I'll probably be doing more of this today so I'll try and be alert for
weirdness.
Cheers,
Andy
On 11/03/2013 23:25, "Eric Greisen" <egreisen at nrao.edu> wrote:
>Andrew Biggs wrote:
>> Hi there. I've recently been experiencing quite a few instances of the
>> following error when I try and, say, TVLOD an image:
>>
>> AIPS 2: ZMI2: DELAY 1
>> AIPS 2: ZMI2: DELAY 2
>> AIPS 2: ZMI2: REQUEST FOR BYTES 1 THRU = 524288
>> AIPS 2: ZMI2: BEYOND EOF = 262144
>> AIPS 2: ZMIO: OPER=READ LUN=16 BLKNO= 1 8-BIT-BYTES=524288
>> AIPS 2: ZERROR: IN ZMI2 ERRNO = 22 (Invalid argument)
>> AIPS 2: TVLOAD: MINIT DISK I/O ERROR = 3
>>
>> This seems to be related to having earlier run CCEDT on the image - a
>> missing CC table somehow seems to result e.g. 1 and 3 are there, but
>>not 2.
>>
>>
>> Do you have any idea what might be causing this? Can the image be
>> recovered?
>
>The DELAY messages are there to defend us from file systems that do not
>keep their file size info up to date (Lustre here at Socorro for one).
>They are real time delays of 1 sec and are done to try to prevent the
>error that follows. The TVLOD thinks that the data file 524288 bytes
>long while it is in fact 1/2 of that. Has the image header become
>corrupted? Can you provide details of the CCEDT issue? Do this
>promptly, I leave Thursday on vacation until April.
>
>Eric
More information about the Daip
mailing list