[daip] Exporting and Import DATA areas
Eric Greisen
egreisen at nrao.edu
Tue Feb 16 10:30:29 EST 2010
Karim.Elatov at colorado.edu wrote:
> It looks like it worked. Here is exactly what I did:
> ================================================================
> BEARS:[102] >source /usr/local/aips/LOGIN.CSH
> BEARS:[103] >aips notv
>
>
> Disk 8 (8) is /arlstorage/data/faculty/ab/cs2/AIPS
> ZMSGOP: FILE DA01:MSD001000.001; NOT FOUND
> MSGWRT ERROR 2 AT OPEN
To get rid of this, login once as user 1 password is AMANAGER, then
restart as some other user number
> AIPS 2: Enter user ID number
> ?17727
Some AIPS routines assume that the user number is <= 4 digits and
smaller numbers may be easier to remember
> AIPS 2: ZCREA2: ERROR OPENING SPACE LOCK FILE = DA08:SPACE
> AIPS 2: ZERROR: ON FILE DA08:CAD000000.DOF;
> AIPS 2: ZERROR: IN ZCREA2 ERRNO = 13 (Permission denied)
> AIPS 2: CATCR: CREATE CATLG ON VOL 8 ERROR 4
This causes an error below - the data area # 8 /arlstorage/ etc does not
have write privilege for you. I recommend either fixing that or taking
the area out of your list of disk areas ($NET0/DADEVS.LIST).
> AIPS 2: Loading a brand new POPS vocabulary
>> task = 'imlod'
>> datain = 'PWD:DISK01C0153'
>> go
> IMLOD2: Task IMLOD (release of 31DEC09) begins
> IMLOD2: Reading from disk file: PWD:DISK01C0153
> AIPS 2: Resumes
>> IMLOD2: ZOPEN: FILE DA08:CAD000000.DOF; NOT FOUND
> IMLOD2: ZOPEN: FILE DA08:CAD000000.DOF; NOT FOUND
> IMLOD2: Create IMLOD .TEMP . 1 (MA) on disk 1 cno 1
> IMLOD2: ZOPEN: FILE DA08:CAD000000.DOF; NOT FOUND
> IMLOD2: RNAM ZETAURJAN98X.ICL001. 1 (MA) ON DISK 1 CNO 1
> IMLOD2: Image=ZETA_AUR (MA) Filename=ZETAURJAN98X.ICL001. 1
> IMLOD2: Telescope=VLA Receiver=VLA
> IMLOD2: Observer=AH603 User #=17727
> IMLOD2: Observ. date=27-JAN-1998 Map date=20-JUL-2004
> IMLOD2: Minimum=-1.24413476E-04 Maximum= 2.64193339E-04 JY/BEAM
> IMLOD2: ----------------------------------------------------------------
> IMLOD2: Type Pixels Coord value at Pixel Coord incr Rotat
> IMLOD2: RA---SIN 1024 05 02 28.653 512.00 -2.200 0.00
> IMLOD2: DEC--SIN 1024 41 04 16.219 513.00 2.200 0.00
> IMLOD2: FREQ 1 8.4601000E+09 1.00 1.0000000E+08 0.00
> IMLOD2: STOKES 1 1.0000000E+00 1.00 1.0000000E+00 0.00
> IMLOD2: ----------------------------------------------------------------
> IMLOD2: Coordinate equinox 2000.00
> IMLOD2: Map type=NORMAL Number of iterations= 35
> IMLOD2: Conv size= 7.30 X 6.82 Position angle= -0.75
> IMLOD2: Rest freq 0.000 Vel type: OPTICAL wrt YOU
> IMLOD2: Alt ref. value 0.00000E+00 wrt pixel 1.00
> IMLOD2: Maximum version number of extension files of type HI is 1
> IMLOD2: Maximum version number of extension files of type CC is 1
> IMLOD2: Maximum version number of extension files of type MF is 1
> IMLOD2: Appears to have ended successfully
> IMLOD2: bears 31DEC09 TST: Cpu= 0.0 Real= 1 IO= 5
perfect
> but not all the way, cause after if I run mcat it doesn't work:
>
> =================================================================
> mcat
> AIPS 2: Catalog on disk 1
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: 1 **** ZETAURJAN98X.ICL001. 1 MA 15-FEB-2010 17:31:14
> AIPS 2: Catalog on disk 2
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: Catalog on disk 3
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: Catalog on disk 4
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: Catalog on disk 5
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: Catalog on disk 6
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: Catalog on disk 7
> AIPS 2: Cat Usid Mapname Class Seq Pt Last access Stat
> AIPS 2: ZOPEN: FILE DA08:CAD000000.DOF; NOT FOUND
The 2 "errors" above are **** from a format not large enough for a 5
digit user number and ZOPEN from your lack of write access to disk area
8. It could not create a CA file for you there. I suspect that my
diagnosis below is actually correct. DO NOT access your Linux areas
with your Solaris machine.
Eric Greisen
>> I am at my wits end with only one last idea.
>>
>> Is it possible that your Solaris aips version has had access to the
>> data areas for the Linux version? If the Solaris version creates the
>> CA catalog file and then the Linux version reads it, there will be
>> problems just like we are seeing. The CA file has 2 words at the
>> beginning that tell it the file size parameters. If they are written
>> by a big endian machine (sun) and then read by a little endian machine
>> (Intel Linux) the sizes will seem very different.
>>
>> Do a
>>
>> restart
>>
>> then enter a new aips number - any number except 1 and the one you
>> have been using
>>
>> then task = 'imlod'
>> datain = 'PWD:DISK01C0153'
>> go
>>
>> and see what happens.
>>
>> Eric Greisen
>>
>
More information about the Daip
mailing list