[daip] Problem with CRSFRING

Tuomas Savolainen tsavolainen at mpifr-bonn.mpg.de
Thu Mar 22 11:43:59 EDT 2007


Hello!

I have noticed the following problem with the CRSFRING procedure in AIPS versions 31DEC06 and 31DEC07. With the parameters given
below...

AIPS 1: CRSFRING: Procedure to calibrate cross pol. delays
AIPS 1: Adverbs     Values                 Comments
AIPS 1: ----------------------------------------------------------------
AIPS 1:                                    Use RUN CRSFRING first
AIPS 1: INNAME     'BS150E'                UV file name (name)
AIPS 1: INCLASS    '43GHZ'                 UV file name (class)
AIPS 1: INSEQ         1                    UV file name (seq. #)
AIPS 1: INDISK        2                    UV file disk drive #
AIPS 1: OUTDISK       2                    Disk for temporary files
AIPS 1: FLAGVER       1                    Flag table to use
AIPS 1: GAINUSE       6                    Calibration table to use
AIPS 1:                                    NO DEFAULT
AIPS 1: SUBARRAY      0                    Selected subarray
AIPS 1: ANTENNAS   *all 0                  List of antennas, 0->use all
AIPS 1: REFANT        8                    Reference antenna
AIPS 1: CALSOUR    *all ' '                Calibrator sources to use.
AIPS 1:                                    See note in HELP file!
AIPS 1: TIMERANG      0          18        Time range
AIPS 1:              22          57           0          18
AIPS 1:              27          44
AIPS 1: SOLINT        0.4                  Pre-averaging interval (min)
AIPS 1: BADDISK    *all 0                  Disk drive #'s to avoid

...the procedure crashes when it tries to run FRING, giving the following output:

vlb022> BLAVG1: Task BLAVG  (release of 31DEC07) begins
vlb022> BLAVG1: You are using a non-standard program
vlb022> BLAVG1: OUTPUT BASELINE   1 -  8
vlb022> BLAVG1: Create CROSSPOL TMP.BLAVG . 666 (UV)  on disk  2  cno    2
vlb022> BLAVG1: BLAVDO:          6 Visibility records written
vlb022> BLAVG1: Copied FQ file from vol/cno/vers  2    1   1 to  2    2   1
vlb022> BLAVG1: Copied OB file from vol/cno/vers  2    1   1 to  2    2   1
vlb022> BLAVG1: Copied AN file from vol/cno/vers  2    1   1 to  2    2   1
vlb022> BLAVG1: Copied SU file from vol/cno/vers  2    1   1 to  2    2   1
vlb022> BLAVG1: Copied WX file from vol/cno/vers  2    1   1 to  2    2   1
vlb022> BLAVG1: Appears to have ended successfully
vlb022> BLAVG1: vlb022       31DEC07 TST: Cpu=       2.1  Real=       7
vlb022> INDXR1: Task INDXR  (release of 31DEC07) begins
vlb022> INDXR1: Appears to have ended successfully
vlb022> INDXR1: vlb022       31DEC07 TST: Cpu=       0.0  Real=       0
vlb022> FRING1: Task FRING  (release of 31DEC07) begins
vlb022> FRING1: You are using a non-standard program
vlb022> FRING1: WARNING: Input int. time (DPARM(4)) is greater than
vlb022> FRING1:          than that found in the data.  Please be aware
vlb022> FRING1:          that this can cause odd errors.
vlb022> FRING1: Selecting the data
vlb022> FRING1: Dividing data by source flux densities
vlb022> FRING1: Determining solutions
vlb022> FRING1: Writing SN table    1
vlb022> FRING1: Time=   0/ 18 25 10, Polarization = 1
vlb022> FRING1: QINIT: did a GET  of    1280 Kwords, OFF       -341843661
vlb022> FRING1: Time=   0/ 18 25 10, Polarization = 2
vlb022> FRING1: ERROR: NO VALID SOLUTIONS FOUND
vlb022> FRING1: Purports to die of UNNATURAL causes
vlb022> FRING1: vlb022       31DEC07 TST: Cpu=       0.0  Real=       0

CRSFRING works perfectly in version 31DEC05 (and earlier) with the same data and with exactly the same input parameters. Has
something changed in FRING between versions 31DEC05 and 31DEC06?

Best regards,
Tuomas Savolainen

-- 
Dr. Tuomas Savolainen
Postdoctoral research fellow
Max-Planck-Institut f. Radioastronomie
Auf dem Huegel 69
D-53121 Bonn
GERMANY

tel. +49 (228) 525 473
gsm. +358 50 581 9717




More information about the Daip mailing list