[daip] Strange behaviour of CALIB
Dmitrijs Docenko
dima at MPA-Garching.MPG.DE
Sun Aug 12 16:00:31 EDT 2007
Dear Eric,
While performing primary calibration with CALIB, I encountered its strange
behaviour. In two words, it is writing irrelevant (and probably wrong in some
respect) data to SN table. Below I describe the problem, adding also some
command inputs and outputs.
I am calibrating 1-IF 1-FQ multisource file obtained by VLA using two
primary and one secondary calibration source. I use 31DEC2007 version of AIPS.
>imh
AIPS 1: Image=MULTI (UV) Filename=CASAL FQ1IF1.UVCOP . 4
AIPS 1: Telescope=VLA Receiver=VLA
AIPS 1: Observer=AD500 User #= 53
AIPS 1: Observ. date=28-MAR-2004 Map date=02-AUG-2007
AIPS 1: # visibilities 241056 Sort order TB
AIPS 1: Rand axes: UU-L-SIN VV-L-SIN WW-L-SIN BASELINE TIME1
AIPS 1: SOURCE FREQSEL
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 4 -1.0000000E+00 1.00 -1.0000000E+00 0.00
AIPS 1: IF 1 1.0000000E+00 1.00 1.0000000E+00 0.00
AIPS 1: FREQ 1 1.2850000E+09 1.00 1.2500000E+07 0.00
AIPS 1: RA 1 00 00 00.000 1.00 3600.000 0.00
AIPS 1: DEC 1 00 00 00.000 1.00 3600.000 0.00
AIPS 1: ----------------------------------------------------------------
AIPS 1: Coordinate equinox 1950.00
AIPS 1: Maximum version number of extension files of type FQ is 1
AIPS 1: Maximum version number of extension files of type HI is 1
AIPS 1: Maximum version number of extension files of type OF 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 CL is 1
AIPS 1: Maximum version number of extension files of type SU is 1
AIPS 1: Maximum version number of extension files of type TY 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 FG is 1
AIPS 1: Keyword = 'CORRMODE' value = ' '
AIPS 1: Keyword = 'VLAIFS ' value = 'ABCD '
This is the scan list:
>go
nca-2 LISTR(31DEC07) 53 12-AUG-2007 21:33:28 Page 1
File = CASAL FQ1IF1.UVCOP . 4 Vol = 5 Userid = 53
Freq = 1.285000000 GHz Ncor = 4 No. vis = 241056
Scan summary listing
Scan Source Qual Calcode Sub Timerange FrqID START VIS END VIS
1 2352+495 : 0000 A 1404/09:55:54 - 404/09:57:39 1 1 3270
2 CASA : 0000 1404/10:01:00 - 404/10:15:51 1 3271 24126
3 2352+495 : 0000 A 1404/10:31:45 - 404/10:33:52 1 24127 28786
4 2352+495 : 0000 A 1404/11:53:14 - 404/11:54:59 1 28787 32756
5 CASA : 0000 1404/11:58:20 - 404/12:13:00 1 32757 57073
6 2352+495 : 0000 A 1404/12:28:55 - 404/12:31:12 1 57074 62215
7 2352+495 : 0000 A 1404/13:51:00 - 404/13:52:51 1 62216 66810
8 CASA : 0000 1404/13:56:25 - 404/14:11:11 1 66811 95470
9 2352+495 : 0000 A 1404/14:27:13 - 404/14:29:20 1 95471 100878
10 0134+329 : 0000 A 1404/15:23:28 - 404/15:27:09 1 100879 110994
11 0518+165 : 0000 A 1404/15:34:27 - 404/15:38:19 1 110995 121254
12 2352+495 : 0000 A 1404/16:35:53 - 404/16:37:39 1 121255 126182
13 CASA : 0000 1404/16:41:20 - 404/16:55:50 1 126183 157896
14 2352+495 : 0000 A 1404/17:11:50 - 404/17:13:57 1 157897 162675
15 2352+495 : 0000 A 1404/18:34:01 - 404/18:35:46 1 162676 168800
16 CASA : 0000 1404/18:39:15 - 404/18:53:50 1 168801 207202
17 2352+495 : 0000 A 1404/19:09:50 - 404/19:11:51 1 207203 213386
18 0134+329 : 0000 A 1404/20:40:50 - 404/20:44:32 1 213387 225220
19 0518+165 : 0000 A 1404/20:52:21 - 404/20:58:51 1 225221 241056
Source summary
Velocity type = ' ' Definition = ' '
ID Source Qual Calcode RA(1950.0) Dec(1950.0) IFlux QFlux UFlux VFlux No. vis
1 2352+495 : 0000 A 23:52:37.7834 49:33:26.800 0.000 0.000 0.000 0.000 49061
2 CASA : 0000 23:21:10.0000 58:32:30.000 0.000 0.000 0.000 0.000 143949
3 0134+329 : 0000 A 01:34:49.8264 32:54:20.260 17.174 0.000 0.000 0.000 21950
4 0518+165 : 0000 A 05:18:16.5141 16:35:26.834 8.824 0.000 0.000 0.000 26096
ID Source Freq(GHz) Velocity(Km/s) Rest freq (GHz)
1 All Sources 1.2850 0.0000 0.0000
Frequency Table summary
FQID IF# Freq(GHz) BW(kHz) Ch.Sep(kHz) Sideband
1 1 1.28500000 12500.0010 12500.0010 1
(note, that the day number is 404, not 1404 or similar)
I am trying to run CALIB on the secondary calibrator 2352+495 with its flux yet set to zero.
AIPS 1: CALIB: Task to determine calibration for data.
AIPS 1: Adverbs Values Comments
AIPS 1: ----------------------------------------------------------------
AIPS 1: Input uv data.
AIPS 1: INNAME 'CASAL FQ1IF1' UV file name (name)
AIPS 1: INCLASS 'UVCOP' UV file name (class)
AIPS 1: INSEQ 4 UV file name (seq. #)
AIPS 1: INDISK 5 UV file disk drive #
AIPS 1: Data selection (multisource):
AIPS 1: CALSOUR '2352+495' Calibrator sources
AIPS 1: *rest ' '
AIPS 1: QUAL -1 Calibrator qualifier -1=>all
AIPS 1: CALCODE ' ' Calibrator code ' '=>all
AIPS 1: SELBAND -1 Bandwidth to select (kHz)
AIPS 1: SELFREQ -1 Frequency to select (MHz)
AIPS 1: FREQID -1 Freq. ID to select.
AIPS 1: TIMERANG *all 0 Time range to use.
AIPS 1: BCHAN 1 Lowest channel number 0=>all
AIPS 1: ECHAN 0 Highest channel number
AIPS 1: ANTENNAS *all 0 Antennas to select. 0=all
AIPS 1: DOFIT *all 0 Subset of ANTENNAS list for
AIPS 1: which solns are desired.
AIPS 1: ANTUSE *all 0 Mean gain is calculated
AIPS 1: (CPARM(2)>0) using only the
AIPS 1: listed antennas. See explain.
AIPS 1: SUBARRAY 0 Subarray, 0=>all
AIPS 1: UVRANGE 0 0 Range of uv distance for full
AIPS 1: weight
AIPS 1: WTUV 0 Weight outside UVRANGE 0=0.
AIPS 1: WEIGHTIT 0 Modify data weights function
AIPS 1: Cal. info for input:
AIPS 1: DOCALIB -1 > 0 calibrate data & weights
AIPS 1: > 99 do NOT calibrate weights
AIPS 1: GAINUSE 2 CL table to apply.
AIPS 1: DOPOL -1 If >0 correct polarization.
AIPS 1: BLVER -1 BL table to apply.
AIPS 1: FLAGVER 1 Flag table version
AIPS 1: DOBAND -1 If >0 apply bandpass cal.
AIPS 1: Method used depends on value
AIPS 1: of DOBAND (see HELP file).
AIPS 1: BPVER -1 Bandpass table version
AIPS 1: SMOOTH *all 0 Smoothing function. See
AIPS 1: HELP SMOOTH for details.
AIPS 1:
AIPS 1: CLEAN map. See HELP.
AIPS 1: IN2NAME ' ' Cleaned map name (name)
AIPS 1: IN2CLASS ' ' Cleaned map name (class)
AIPS 1: IN2SEQ 0 Cleaned map name (seq. #)
AIPS 1: IN2DISK 0 Cleaned map disk unit #
AIPS 1: INVERS 0 CC file version #.
AIPS 1: NCOMP *all 0 # comps to use for model.
AIPS 1: 1 value per field
AIPS 1: FLUX 0 Lowest CC component used.
AIPS 1: NMAPS 0 No. Clean map files
AIPS 1: CMETHOD ' ' Modeling method:
AIPS 1: 'DFT','GRID',' '
AIPS 1: CMODEL ' ' Model type: 'COMP','IMAG'
AIPS 1: SMODEL *all 0 Source model, 1=flux,2=x,3=y
AIPS 1: See HELP SMODEL for models.
AIPS 1:
AIPS 1: Output uv data file.
AIPS 1: OUTNAME ' ' UV file name (name)
AIPS 1: OUTCLASS ' ' UV file name (class)
AIPS 1: OUTSEQ 0 UV file name (seq. #)
AIPS 1: OUTDISK 1 UV file disk drive #
AIPS 1:
AIPS 1: Solution control adverbs:
AIPS 1: REFANT 6 Reference antenna
AIPS 1: SOLINT 2 Solution interval (min)
AIPS 1: SOLSUB 1 Solution subinterval
AIPS 1: SOLMIN 1 Min solution interval
AIPS 1: APARM 0 0 General parameters
AIPS 1: 0 0 1=min. no. antennas
AIPS 1: 0 2 2 > 0 => data divided
AIPS 1: *rest 0 3 > 0 => avg. RR,LL
AIPS 1: 5 > 0 => avg. IFs.
AIPS 1: 6=print level, 1=good,
AIPS 1: 2 closure, 3 SNR
AIPS 1: 7=SNR cutoff (0=>5)
AIPS 1: 8=max. ant. # (no AN)
AIPS 1: 9 > 0 => pass failed soln
AIPS 1: 10 < 99 cal output weights
AIPS 1: Phase-amplitude Parameters:
AIPS 1: DOFLAG 0 Flag on closure error?
AIPS 1: SOLTYPE 'R' Soln type,' ','L1','GCON',
AIPS 1: 'R', 'L1R', 'GCOR'
AIPS 1: SOLMODE 'A&P' Soln. mode: 'A&P','P','P!A',
AIPS 1: 'GCON',
AIPS 1: SOLCON 0 Gain constraint factor.
AIPS 1: MINAMPER 0 Amplitude closure error
AIPS 1: regarded as excessive in %
AIPS 1: MINPHSER 0 Phase closure error regarded
AIPS 1: as excessive in degrees
AIPS 1: CPARM *all 0 Phase-amp. parameters
AIPS 1: 1 = Min el for gain
AIPS 1: normalization (deg)
AIPS 1: 2 >0 => normalize gain
AIPS 1: 3 avg. amp. closure err
AIPS 1: 4 avg. ph. closure err
AIPS 1: 5 >0 => scalar average
AIPS 1: 6 limit clipping in robust
AIPS 1: 7 limit display of closure
AIPS 1: errors
AIPS 1: SNVER 1 Output SN table, 0=>new table
AIPS 1: ANTWT *all 0 Ant. weights (0=>1.0)
AIPS 1: GAINERR *all 0 Std. Dev. of antenna gains.
AIPS 1: BADDISK *all 0 Disk no. not to use for
AIPS 1: scratch files.
Though, when I do it, the printout of the SN table shows that it
contains not only data on the source "1" (i.e., 2352+495), but also
other (say, primary calibrator) sources. This seem to make their
gain calibration wrong affecting determined secondary calibrator flux.
(Note: it does not depend on SOLINT, SOLMIN, SOLSUB - I've tried it)
Printout of part of SN table made with PRTAB (note the source IDs):
CASAL FQ1IF1.UVCOP . 4 Disk= 5 SN Table version 1
Title: AIPS UV DATA FILE SOLUTION TABLE
Created by CALIB on 12-AUG-2007 21:43:58
Last written by CALIB on 12-AUG-2007 21:43:58
Ncol 22 Nrow 273 Sort cols:
Table has 8 keyword-value pairs:
NO_ANT = 29
NO_POL = 2
NO_IF = 1
NO_NODES = 0
MGMOD = 1.0000000000000D+00
APPLIED = F
REVISION = 10
ORIGIN = 0
Table can be written as a FITS ASCII table
COL. NO. 1 2 3 4 5 6 7 8
ROW TIME TIME INTER SOURCE ID ANTENNA SUBARRAY FREQ ID I.FAR.ROT NODE NO.
NUMBER D/HMS D/HMS RAD/M**2
1 404/09:56:49.3 00:01:40.2 1 1 1 1 0.000E+00 0
2 404/09:56:49.3 00:01:40.2 1 2 1 1 0.000E+00 0
....
118 404/14:28:16.3 00:01:53.4 1 26 1 1 0.000E+00 0
119 404/14:28:16.3 00:01:53.4 1 28 1 1 0.000E+00 0
120 404/14:29:19.6 00:00:00.0 3 1 1 1 0.000E+00 0
121 404/14:29:19.6 00:00:00.0 3 2 1 1 0.000E+00 0
...
140 404/14:29:19.6 00:00:00.0 3 27 1 1 0.000E+00 0
141 404/14:29:19.6 00:00:00.0 3 28 1 1 0.000E+00 0
142 404/16:36:46.1 00:01:40.2 1 1 1 1 0.000E+00 0
...
161 404/16:36:46.1 00:01:40.2 1 27 1 1 0.000E+00 0
162 404/16:36:46.1 00:01:40.2 1 28 1 1 0.000E+00 0
163 404/16:37:38.8 00:00:00.0 2 1 1 1 0.000E+00 0
164 404/16:37:38.8 00:00:00.0 2 2 1 1 0.000E+00 0
...
182 404/16:37:38.8 00:00:00.0 2 27 1 1 0.000E+00 0
183 404/16:37:38.8 00:00:00.0 2 28 1 1 0.000E+00 0
184 404/17:12:53.4 00:01:58.7 1 1 1 1 0.000E+00 0
...
201 404/17:12:53.4 00:01:58.7 1 26 1 1 0.000E+00 0
202 404/17:12:53.4 00:01:58.7 1 28 1 1 0.000E+00 0
203 404/17:54:54.1 01:21:46.9 1 1 1 1 0.000E+00 0
204 404/17:54:54.1 01:21:46.9 1 2 1 1 0.000E+00 0
...
225 404/17:54:54.1 01:21:46.9 1 27 1 1 0.000E+00 0
226 404/17:54:54.1 01:21:46.9 1 28 1 1 0.000E+00 0
227 404/18:35:48.9 00:00:00.0 2 2 1 1 0.000E+00 0
228 404/18:35:48.9 00:00:00.0 2 3 1 1 0.000E+00 0
...
248 404/18:35:48.9 00:00:00.0 2 27 1 1 0.000E+00 0
249 404/18:35:48.9 00:00:00.0 2 28 1 1 0.000E+00 0
250 404/19:10:53.0 00:01:56.0 1 1 1 1 0.000E+00 0
251 404/19:10:53.0 00:01:56.0 1 2 1 1 0.000E+00 0
...
You also may have noticed that there is a strange entries at 17:54:54.1 that CALIB seem
to interpret as observations of 1st source, whereas from scan list (see above) it follows
that no observations have been made during this period.
Please advise. Would it be enough just to flag the strange (questionable) entries in SN file?
Sincerely yours,
Dmitrijs
More information about the Daip
mailing list