[daip] IMAGR problem

[Eric Greisen]

Hanno Spreeuw writes:
 > Thank you, I should have added that this is not the most common dataset.
 > When we import WSRT UVFITS files in AIPS (using FITLD), we change one of 
 > the header elements, using PUTHEAD, from -5 to -1, with keyw 'CRVAL2' en 
 > keyv -1,0 as indicated on Robert Braun's website:
 > http://www.astron.nl/wsrt/WSRTsoft/cookbook.html

    That changes the Stokes from XX, YY, etc to RR, LL, etc which aips
understands better.  That is not your problem.  In fact the issue is
with the random parameters which I do not understand at all.  The
array that is being displayed in the error message should - from the
header below - be 0, 1, 2, 3, 4, -1, 5, -1, -1 where -1 means a type
of parameter was not found (no SOURCE, INTTIM, CORR-ID)  The messages
from UVPGET and IMAGR indicate that twice (completely separate code
areas) the first random parameter is not (in the 1st 4 characters)
UU-L despite what imheader says.  I was first thinking that perhaps
the header is not blank filled but null chars but aips only looks at
the first 4 chars in the UU-L case.  That could be the explanation for
why FREQSEL is also not recognized.  Is there some error in what is
actually in these strings that somehow does not stop IMHEADER from
making what appears to be a correct display?  (E.g. bad char,
backspace char, then UU-L and FREQSEL with nulls trailing rather than
blanks).

Note PRTUV is a good enough test, rather than the more complex IMAGR.

Eric Greisen


 > 
 > But this is not a WSRT dataset, this is a UVFITS made from a LOFAR 
 > teststation measurement set, I tried the same trick. Anyway, this is imh:
 > 
 >  >imh
 > AIPS 3: Image=BEAM_0    (UV)         Filename=CS1JUPSRT   .UVDATA.   2
 > AIPS 3: Telescope=LOFAR              Receiver=LOFAR
 > AIPS 3: Observer=LofarSim            User #=  134
 > AIPS 3: Observ. date=27-FEB-2007     Map date=13-APR-2007
 > AIPS 3: # visibilities    147424     Sort order  TB
 > AIPS 3: Rand axes: UU-L  VV-L  WW-L  TIME1  BASELINE  FREQSEL
 > AIPS 3: ----------------------------------------------------------------
 > AIPS 3: Type    Pixels   Coord value     at Pixel     Coord incr   Rotat
 > AIPS 3: COMPLEX      3   1.0000000E+00       1.00  1.0000000E+00    0.00
 > AIPS 3: STOKES       4  -1.0000000E+00       1.00 -1.0000000E+00    0.00
 > AIPS 3: FREQ       256   2.6561890E+07     128.00  6.1035156E+02    0.00
 > AIPS 3: IF           2   1.0000000E+00       1.00  1.0000000E+00    0.00
 > AIPS 3: RA           1    17 06 24.703       1.00       3600.000    0.00
 > AIPS 3: DEC          1   -21 50 33.983       1.00       3600.000    0.00
 > AIPS 3: ----------------------------------------------------------------
 > AIPS 3: Coordinate equinox 2000.00
 > AIPS 3: Maximum version number of extension files of type HI is   1
 > AIPS 3: Maximum version number of extension files of type FQ is   1
 > AIPS 3: Maximum version number of extension files of type AN is   1
 > AIPS 3: Maximum version number of extension files of type SU is   1
 > 
 > 
 > 
 > 
 > Eric Greisen wrote:
 > > Hanno Spreeuw writes:
 > >  > Hello, when running IMAGR, I get this error:
 > >  > CASTOR> IMAGR3: Task IMAGR  (release of 31DEC04) begins
 > >  > CASTOR> IMAGR3: UVPGET: RANDOM PARMS NOT ALL THERE: -1  1  2  3  4 -1 -1 
 > >  > -1 -1
 > >  > CASTOR> IMAGR3: I DO NOT WORK FOR UV DATA OF TYPE '??'
 > >  > CASTOR> IMAGR3: Purports to die of UNNATURAL causes
 > >  > 
 > >  > Do you know what is wrong?
 > > 
 > > There is something odd about the first axis in the header - if you
 > > send me the output of IMHEADER I couild say more.  It is looking for a
 > > COMPLEX axis.
 > > 
 > > Eric Greisen
 > >