[daip] AIPS and ALMA?
swood
swood at nrao.edu
Wed Feb 10 15:28:15 EST 2016
Hello Glen,
The computing staff says there is a way to run AIPS. The user can run AIPS on the cluster after invoking the shell script:
. /home/aips/LOGIN.SH
Let me know if it works. If there is a bug in CASA, you should submit a help desk ticket so we can figure it out.
Thanks, Sarah-------- Original message --------From: "Langston, Glen" <glangsto at nsf.gov> Date: 2/10/2016 5:15 PM (GMT+01:00) To: Eric Greisen <egreisen at nrao.edu> Cc: daip at nrao.edu, awootten at nrao.edu, Ken Kellermann <kkellerm at nrao.edu>, swood at nrao.edu Subject: Re: AIPS and ALMA?
Hi Eric,
Thanks of your quick response. Sounds like a very
good diagnosis.
The NRAO should appreciate the value of keeping a
second analysis system going for diagnosis of CASA issues.
Glen
To summarize, CASA needs an upgrade to their
“exportuvfits” program to fill values in an associated table of the uvdata.
This may be manually fixable inside of AIPS.
Glen I Langston, Ph. D.
Program Director
National Science Foundation
4201 Wilson Blvd, Suite 1045
Arlington, VA 22230
P: 703-292-4937
glangsto at nsf.gov
> On Feb 10, 2016, at 10:21 AM, Eric Greisen <egreisen at nrao.edu> wrote:
>
> On 02/09/2016 04:09 PM, Langston, Glen wrote:
>> Hi Eric,
>>
>> Hope all is well with you. After some fiddling inside of CASA I decided to
>> try to export some UV data to AIPS for a test.
>>
>> However this is not going too well either.
>>
>> The UVLOD step looks good to start with:
>>
>> IPS 1: Image=Saturn (UV) Filename=Saturn .UVDATA. 1
>> AIPS 1: Telescope=ALMA Receiver=ALMA
>> AIPS 1: Observer=Unknown User #= 1256
>> AIPS 1: Observ. date=14-JAN-2012 Map date=09-FEB-2016
>> AIPS 1: # visibilities 1200 Sort order TB
>> AIPS 1: Rand axes: UU-L VV-L WW-L TIME1 SUBARRAY FREQSEL ANTENNA1
>> AIPS 1: ANTENNA2
>> AIPS 1: ----------------------------------------------------------------
>> AIPS 1: Type Pixels Coord value at Pixel Coord incr Rotat
>> AIPS 1: COMPLEX 3 1.0000000E+00 1.00 1.0000000E+00 0.00
>> AIPS 1: STOKES 2 -5.0000000E+00 1.00 -1.0000000E+00 0.00
>> AIPS 1: FREQ 3840 2.3053812E+11 1921.00 2.4414062E+05 0.00
>> AIPS 1: IF 1 1.0000000E+00 1.00 1.0000000E+00 0.00
>> AIPS 1: RA 1 13 50 42.054 1.00 3600.000 0.00
>> AIPS 1: DEC 1 -08 44 30.927 1.00 3600.000 0.00
>> AIPS 1: ----------------------------------------------------------------
>> AIPS 1: Coordinate equinox 2000.00
>> AIPS 1: Maximum version number of extension files of type HI is 1
>> AIPS 1: Maximum version number of extension files of type FQ is 1
>> AIPS 1: Maximum version number of extension files of type AN is 1
>> AIPS 1: Maximum version number of extension files of type WX is 1
>> AIPS 1: Maximum version number of extension files of type NX is 1
>> AIPS 1: Maximum version number of extension files of type PL is 2
>>
>> However the imagr step is not yielding any good results.
>>
>> Any idea why the frequency error messages are appearing (below)?
>>
>>
>> Thanks
>>
>> Glen
>>
>>
>>
>> uclid> IMAGR1: UVGET: doing no flagging this time
>> euclid> IMAGR1: WARNING: uncalibrated linear polarization data may be a problem
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: Create Saturn .IMAGR . 1 (UV) on disk 1 cno 13
>> euclid> IMAGR1: Beginning channel 1 through 2 with 1 IFs
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: IMACPY: Copied 1200 visibilities to be imaged
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: QINIT: did a GET of 5120 Kwords, OFF -63346538
>> euclid> IMAGR1: UVWAIT: begin finding uniform weights
>> euclid> IMAGR1: UVWAIT: Average grid weight 2.733E-01
>> euclid> IMAGR1: UVWAIT: Adding temperance S 5.466E-02
>> euclid> IMAGR1: UVWAIT: begin applying uniform or other weights
>> euclid> IMAGR1: UVWAIT: Sum of weights in 2.733E-01 and out 2.733E-01
>> euclid> IMAGR1: UVWAIT: Noise is increased by a factor 1.000 due to weighting
>> euclid> IMAGR1: UVWAIT: Average summed weight 2.733E-01 over 2400. vis
>> euclid> IMAGR1: Create Saturn .IBM001. 4 (MA) on disk 1 cno 14
>> euclid> IMAGR1: Create Saturn .ICL001. 4 (MA) on disk 1 cno 16
>> euclid> IMAGR1: CHANGED FREQ = 0 TO 1 HZ TO AVOID BIGGER HURTS
>> euclid> IMAGR1: GRDFLT: X and Y convolution type = SPHEROIDAL
>> euclid> IMAGR1: GRDFLT: X and Y parms = 3.0000 1.0000
>> euclid> IMAGR1: GRDFLT: convolution function sampled every 1/100 of a cell
>> euclid> IMAGR1: GRDMEM: FREQUENCIES UNKNOWN BEGINNING WITH CHANNEL 2
>> euclid> IMAGR1: OUVIMG: MAKING BEAM BEAM field number 0001
>> euclid> IMAGR1: OUVIMG: FROM UVdata work object
>> euclid> IMAGR1: CLNINI: ERROR OPENING CLEAN process object
>> euclid> IMAGR1: CLNUV : ERROR CLEANING CLEAN process object
>> euclid> IMAGR1: Deleting UV work file:
>> euclid> IMAGR1: Destroyed 1 extension files of type AN
>> euclid> IMAGR1: Destroyed 1 extension files of type FQ
>> euclid> IMAGR1: Destroyed UV image file: catno= 13 disk= 1
>> euclid> IMAGR1: Purports to die of UNNATURAL causes
>> euclid> IMAGR1: euclid 31DEC15 NEW: Cpu= 4.8 Real= 5 IO= 180
>
> people have done ALMA data in AIPS but ALMA believes that uv data should never be given to users and so there is no support for FITS readers and writers.
>
> Take a look at the FQ table. Since this is a simple data set - 1 FQ, 1 IF, single source - you should be able to fix the values in the FQ table to match those you see in the header.
>
> TABPUT is the verb you will probably need.
>
> Eric Greisen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/daip/attachments/20160210/7e289ef1/attachment-0001.html>
More information about the Daip
mailing list