[daip] gain missing in APCAL
Amy Mioduszewski
amiodusz at nrao.edu
Thu Sep 11 18:01:52 EDT 2014
Hi Arnaud,
So you never user TY/1 or GC/1?
O.K., I just ran ANTAB and APCAL using the rdv98_reste_X_v2_OUT.antabfs you sent
me and the inputs/loops you specify below and I get no errors:
APCAL4: Task APCAL (release of 31DEC14) begins
APCAL4: Writing SN table 1 for subarray 1
APCAL4: Appears to have ended successfully
APCAL4: thor 31DEC14 TST: Cpu= 0.2 Real= 0 IO= 38
AIPS 4: Resumes
AIPS 4: APCAL was not found to be running
APCAL4: Task APCAL (release of 31DEC14) begins
APCAL4: Writing SN table 2 for subarray 2
APCAL4: Appears to have ended successfully
APCAL4: thor 31DEC14 TST: Cpu= 0.2 Real= 0 IO= 33
AIPS 4: Resumes
AIPS 4: APCAL was not found to be running
APCAL4: Task APCAL (release of 31DEC14) begins
APCAL4: Writing SN table 3 for subarray 3
APCAL4: Appears to have ended successfully
APCAL4: thor 31DEC14 TST: Cpu= 0.1 Real= 0 IO= 19
AIPS 4: Resumes
AIPS 4: APCAL was not found to be running
APCAL4: Task APCAL (release of 31DEC14) begins
APCAL4: Writing SN table 4 for subarray 4
APCAL4: Appears to have ended successfully
APCAL4: thor 31DEC14 TST: Cpu= 0.0 Real= 0 IO= 1
AIPS 4: Resumes
So, I am at somewhat of a loss. My only thought is that we ran the stuff before
ANTAB/APCAL differently. How did you copy out the X-band data? I notice that
there seems to be a spurious second FQID in the original data that appears never
to be used. What where your inputs for USUBA?
Amy
On 09/08/2014 04:23 AM, Arnaud Collioud wrote:
> Hi Amy,
>
> I am using the up-to-date 31DEC14 version.
>
> With ANTAB, I created one TY/GC table per subarray, which mean I used a loop over subarrays :
> for i=1 to 4 ; subarray i ; tyver i+1 ; gcver i+1; go antab ; wait ; end
> (TY1 and GC1 are kept by using the i+1 indices)
>
> The other ANTAB params are :
> AIPS 1: ANTAB Task to read amplitude calibration info. into AIPS
> AIPS 1: Adverbs Values Comments
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: INNAME 'RDV98_X' Input UV file name (name)
> AIPS 1: INCLASS 'UVDATA' Input UV file name (class)
> AIPS 1: INSEQ 1 Input UV file name (seq. #)
> AIPS 1: INDISK 1 Input UV file disk unit #
> AIPS 1: CALIN 'rdv98_reste_X.antabfs' Calibration file name.
> AIPS 1: SUBARRAY 1 Subarray (0=> 1)
> AIPS 1: Output table versions:
> AIPS 1: TYVER 2 TY table to update
> AIPS 1: GCVER 2 GC table to update
> AIPS 1: BLVER -1 BL table to update
> AIPS 1: SPARM *all ' ' List of stations to ignore
> AIPS 1: PRTLEV 0 Print level (0=>none;
> AIPS 1: 1=> echo cal. file)
> AIPS 1: OFFSET 0 Increase the scan length of
> AIPS 1: each side, minutes
>
> For the CALIN parameter, you already have the antabfs file for the EVN/IVS stations. I also use an antabfs file for the VLBA stations ; it is attached to this email.
>
> Then, in APCAL, I created one SN table per subarray in the same way:
> for i=1 to 4 ; subarray i ; tyver i+1 ; gcver i+1; go apcal ; wait ; end
>
> AIPS 1: APCAL Task to generate an amplitude calibration SN table
> AIPS 1: Adverbs Values Comments
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: INNAME 'RDV98_X' Input UV file name (name)
> AIPS 1: INCLASS 'UVDATA' Input UV file name (class)
> AIPS 1: INSEQ 1 Input UV file name (seq. #)
> AIPS 1: INDISK 1 Input UV file disk unit #
> AIPS 1:
> AIPS 1: ANTENNAS *all 0 Antennas to calibrate
> AIPS 1: SUBARRAY 1 Subarray 0 -> all
> AIPS 1: STOKES ' ' Stokes type ('R','L',' ')
> AIPS 1: BIF 1 Start IF number
> AIPS 1: EIF 4 End IF number
> AIPS 1: FREQID -1 Freq. ID to calibrate
> AIPS 1: SOURCES *all ' ' Sources to calibrate
> AIPS 1: TIMERANG *all 0 Time range to calibrate
> AIPS 1:
> AIPS 1: TYVER 2 TY table version number.
> AIPS 1: GCVER 2 GC table version number.
> AIPS 1: SNVER 0 Output SN table version.
> AIPS 1: 0 -> highest unique
> AIPS 1: OPCODE ' ' Opacity correction opcode:
> AIPS 1: ' ' -> no opacity corr.
> AIPS 1: 'GRID','GRDR','OPAC','OPCR',
> AIPS 1: 'LESQ' -> fit for opacity
> AIPS 1: APARM *all 0 Calibration parameters:
> AIPS 1: (1) -> B factor (def. 1.0)
> AIPS 1: Opacity parameters:
> AIPS 1: (2) -> ZA limit (deg)
> AIPS 1: (3) >=0 use spillover
> AIPS 1: correction
> AIPS 1: (4) > 0 use all FQ in
> AIPS 1: opac. soln.
> AIPS 1: (5) Limit to sec(z) plotted
> AIPS 1: SOLINT 0 Solution interval (min)
> AIPS 1: 0 -> use all data
> AIPS 1: INVERS 0 WX table version number.
> AIPS 1: 0 -> use text file
> AIPS 1: CALIN *all ' ' Text file with weather info.
> AIPS 1: Must be ' ' if using WX
> AIPS 1: table (INVERS).
> AIPS 1: TRECVR *all 0 Receiver temperatures (K);
> AIPS 1: in (R,L) pairs.
> AIPS 1: TAU0 *all 0 Zenith opacities (per ant.)
> AIPS 1: DOFIT *all 0 Fit type (per ant.)
> AIPS 1: -1 -> no opacity correction
> AIPS 1: 0 -> apply TRECVR only
> AIPS 1: 1 -> solve for Trec using
> AIPS 1: fitting method spec.
> AIPS 1: in OPCODE; then apply
> AIPS 1: PRTLEV 0 Print level
> AIPS 1: DOTV 1 TV selection (<0 -> PL file)
> AIPS 1: LTYPE 3 Plot labeling
> AIPS 1: GRCHAN 0 TV Graphics channel to use
>
> Cheers,
> Arnaud
>
>
>
>
> Le 6 sept. 2014 à 00:27, Amy Mioduszewski a écrit :
>
>> Hi Arnaud,
>>
>> I have loaded your data run USUBA, VLBAMCAL, INDXR and ANTAB. I have encountered the similar error as you but I suspect it has a different cause. Namely when I use ANTAB, instead of writing into the designated TY/GC tables, it replaces them. So I think this is a separate bug from the one you are seeing (although similar message, but on ante 1, rather than 3). Anyway, what exact inputs do you use in ANTAB for the different subarrays?
>>
>> Also what version of AIPS are you running?
>>
>> Amy
>
>
>
>
> _______________________________________________
> Daip mailing list
> Daip at listmgr.nrao.edu
> https://listmgr.nrao.edu/mailman/listinfo/daip
>
More information about the Daip
mailing list