[daip] Another question (SQASH)

[Eric Greisen]

Farhad Zadeh wrote:
> Hi Eric,
> Trying to use sqash on a GBT cube with 700 channels but
> aips fails.  This is the message I get.
> I also include the FITS header. What are we doing wrong?
> I appreciate the advice,
> Farhad
> 
>   Image=GC        (MA)         Filename=RRL_GBT     .cube  .   1
> AIPS 1: Telescope=NRAO_GBT           Receiver=Rcvr8_10
> AIPS 1: Observer=Marc Roy            User #=  110
> AIPS 1: Observ. date=14-MAR-2011     Map date=12-OCT-2011
> AIPS 1: Pixel type: FLOATING         Magic value blanking
> AIPS 1: Minimum=-9.29580629E-02      Maximum= 7.48742640E-01 Jy
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: Type    Pixels   Coord value     at Pixel     Coord incr   Rotat
> AIPS 1: GLON-SIN   256   3.5994468E+02     128.00 -8.3333338E-03    0.00
> AIPS 1: GLAT-SIN   128  -4.6189833E-02      65.00  8.3333338E-03    0.00
> AIPS 1: VELO-LSR   700   0.0000000E+00     312.63  7.2020032E+02    0.00
> AIPS 1: STOKES       1   1.0000000E+00       1.00  1.0000000E+00    0.00
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: Map type=DIRTY               Number of iterations=       0
> AIPS 1: Conv size=  80.89 X  80.89   Position angle=   0.00
> AIPS 1: Rest freq   9173.320         Vel type: RADIO   wrt LSR
> AIPS 1: Alt ref. value  9.17316E+09  wrt pixel  320.00
> AIPS 1: Maximum version number of extension files of type HI is   1
> townes> SQASH1: ZMI2: REQUEST FOR BYTES 1 THRU = 64512
> townes> SQASH1: ZMI2: BEYOND EOF = 13312
> townes> SQASH1: ZMIO: OPER=WRIT LUN=18 BLKNO=           1 8-BIT-BYTES= 
> 64512
> townes> SQASH1: ZERROR: IN ZMI2 ERRNO = 22 (Invalid argument)
> townes> SQASH1: SQASH3: ERROR   3 ON WRITE A ROW
> townes> SQASH1: Destroyed MA image file: catno=     25 disk=10
> townes> SQASH1: Purports to die of UNNATURAL causes
> townes> SQASH1: townes 31DEC11 TST: Cpu=      0.5  Real=      5  IO= 
This is bizarre - your output image (assuming BLC=0, TRC=0) is 128 
kbytes and yet only 13 kbytes are in the file.  Something is wrong with 
your disk IO system.  We use lustre here and that sometimes gives false 
information about file sizes.  I have added code way down in tasks to 
detect this failure, wait 1 sec, ask again about file size, and repeat 
once more if needed (each time with a message).  I did not link it into 
SQASH until just now.  If you are running 31DEC12, you can get this fix 
with a MNJ starting Jan 22.  Even in 31DEC11 a MNJ will get another fix
for SQASH having to do with the history file writing at the end.

Eric Greisen