[daip] trouble reading VLA data in archival format into FILLM

Eric Greisen egreisen at nrao.edu
Sun May 23 17:09:57 EDT 2004


Ruth Daly writes:

 > I have VLA data obtained by O'Dea et al., and am having
 > trouble reading the data into FILLM.  The D array data set is called
 > AO170_B030411.XP11.  This data is in archival format.

     cd wherever you have these data
     setenv MYAREA=`pwd`    (for tcsh)
     export MYAREA=`pwd`    (for bash - note the back tick marks)
     aips
     <user-number>
     infile 'MYAREA:AO170_B030411.XP1'
     tphead
     nfiles = 0
     go fillm       (after outdisk et al are also set)

this should work

 > We have tried many different ways of reading in the data file, and each 
 > time we
 > get a similar error message: ZTPOPN: DISK DEVICE = (whatever we used)1 NOT
 > FOUND.  FLDKIO: ERROR
 > 
 > We have tried using a direct path, as described in section 3.10.1 in the 
 > COOKBOOK; and
 > we have tried defining user data area assignments in a .dadevs file in my 
 > home directory.

      Data areas in .dadevs, $NET0/DADEVS.LIST et al are for main data
areas.  They are not a user disk directory per se and should not be
used to hold random files of e.g. FITS format or archive format.  You
may use any disk area but you must point at it properly

 > Neither of these worked.  We also tried adding destinations to the 
 > DADEVS.LIST file, and
 > this seemed to have no effect.
 > 
 > We are wondering: where do we put the data to be read in by FILLM?

   anywhere is fine if you follow instructions on how to specify
infile.

 > 
 > The output from AIPS is:
 > 
 > START_AIPS: User data area assignments:
 >    (Using private file /home/daly/.dadevs)
 >     Disk 1 (1) is /home/daly/L219-2/VLADATA/
 >     Disk 2 (2) is /usr/AIPS/DATA/L219-2_1
 >     Disk 3 (3) is /usr/AIPS/DATA/L219-2_VLADATA
 > 
 > L219-2> FILLM1: Task FILLM  (release of 31DEC03) begins
 > L219-2> FILLM1: UV data will be written in compressed format
 > L219-2> FILLM1: Shadow flag limit =  2.500E+01 meters.
 > L219-2> FILLM1: Opacity correction in CL table weighted average of weather
 > and
 > L219-2> FILLM1:    season.  Weight for weather = 0.50
 > L219-2> FILLM1: Gain curve correction in CL table read from file,
 > L219-2> FILLM1:    with variation as function of antenna and band.
 > L219-2> FILLM1: Opening AO170_B30411.XP111
 > L219-2> FILLM1: ZTPOPN: DISK DEVICE = AO170_B30411.XP111 NOT FOUND

   in theis case INFILE='AO170_B30411.XP11' with no logical area
defined at all and with too many 1's at the end of the name.  FILLM as
is stated in the help file add the file number to the end of the file
- which is why the file you received ended in a 1.  If you had gotten
2 files the other would have ended in a 2.  The absence of a logical
area here should be okay if the default area when you started aips is
the data area where the file is found.

Eric Greisen




More information about the Daip mailing list