[daip] question regarding VBGLU

[Amy Mioduszewski]

Dear Chengyu,

O.K., well I think I am confused because there are two different concepts here, 
FREQIDs (which are different frequency bands or frequency setups) and multiple 
passes with the same FREQID with different IFs in each pass.  Also it looked 
like the messages from VBGLU indicated that those data had been UVCOPed so I was 
just wondering what exactly had been done to the data.

Anyway, I looked at the schedule for BB242H and it you have atmospheric blocks 
and regular blocks plus multiple passes.  My guess looking at the messages from 
VBGLU is that you are trying to glue the atmospheric blocks, is that correct?  I 
think I may have to download your data and experiment, but I need to know 
exactly what you did.  Since both files are .UVCOP. you must have done something 
more than INDXR, unless you renamed them .UVCOP. for some reason.

Amy

Cheng-Yu Kuo wrote:
>            Dear Amy:
> 
>      My data was correlated into two different freqids. So I loaded the 
> two freqids separately
> from the tape into two different files. Then I INDXRed both files and 
> did VBGLU. Is it possible
> that I loaded the data wrongly? Thanks.
> 
> regards
> chengyu
> 
> On Thu, 17 Jul 2008 13:40:31 -0600
>  Amy Mioduszewski <amiodusz at nrao.edu> wrote:
>> Dear Chengyu,
>>
>> What did you do the the data before you VBGLUed them?
>>
>> Amy
>>
>> Cheng-Yu Kuo wrote:
>>>           Dear VLBI experts in AIPS helpdesk:
>>>
>>>         My name is Chengyu Kuo, a UV graduate student. I have a 
>>> question about AIPS again!
>>> Part of my VLBA observation is to observe many geodetic calibrators 
>>> to determine the zenith
>>> atmosphere delays and clock errors. For one of my geodetic datasets, 
>>> I have problems to
>>> do VGBLU properly.
>>>
>>>         The program ID for this dataset is BB242H. There are two 
>>> freqids for the geodetic observation,
>>> and I need to VBGLU  the two freqids to stick all 8 IF bands 
>>> together. However, for some unknown
>>> reasons, VBGLU cannot stick them properly. The AIPS message is 
>>> attached at the end of this email.
>>> I also attach the jpec image of what I see by using EDITA to view the 
>>> TY table with this email. There are many data that have zero system 
>>> temperature. However, if I do this for each freqid separately, there 
>>> is no such a problem.
>>>
>>>         In addition, this problem seem to affect the calibration 
>>> process. I cannot do instrumental
>>> delay calibration properly. There are big phase offsets between the 
>>> two freqids for GBT for the geodetic blocks affected by the mis-match 
>>> after VBGLU. I did not see this problem in my other datasets. Could 
>>> you help me to take a look of this problem. Thank you for your time!
>>>
>>> regards
>>> chengyu
>>>  
>>> chimp.> VBGLU3: Task VBGLU  (release of 31DEC06) begins
>>> chimp.> VBGLU3: Create GEODET0419  .VBGLU .   5 (UV)  on disk  5  
>>> cno    3
>>> chimp.> VBGLU3: File GEODET0419  .UVCOP . 124 on disk   5 covers
>>> chimp.> VBGLU3: time range   0/ 13 39  3 -   0/ 14 20  5 and has    
>>> 45087 vis
>>> chimp.> VBGLU3: File GEODET0419  .UVCOP . 528 on disk   5 covers
>>> chimp.> VBGLU3: time range   0/ 13 39  3 -   0/ 14 20  5 and has    
>>> 45045 vis
>>> chimp.> VBGLU3: Wrote      154 visibilities with data merged in from 
>>> 1 files
>>> chimp.> VBGLU3: Wrote    44989 visibilities with data merged in from 
>>> 2 files
>>> chimp.> VBGLU3: Operation required       1 I/O re-initializations
>>> chimp.> VBGLU3: Copied OB file from vol/cno/vers  5    1   1 to  5    
>>> 3  1
>>> chimp.> VBGLU3: Copied AN file from vol/cno/vers  5    1   1 to  5    
>>> 3  1
>>> chimp.> VBGLU3: Copied FG file from vol/cno/vers  5    1   1 to  5    
>>> 3  1
>>> chimp.> VBGLU3: Copied WX file from vol/cno/vers  5    1   1 to  5    
>>> 3  1
>>> chimp.> VBGLU3: Copied NX file from vol/cno/vers  5    1   1 to  5    
>>> 3  1
>>> chimp.> VBGLU3: GLUTAB TABLE: AT MISSING REQUIRED COLUMNS, FILE 1
>>> chimp.> VBGLU3: IM table copied:    462 rows containing data from 1 
>>> input files
>>> chimp.> VBGLU3: IM table copied:    110 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3:     THIS SUGGESTS THAT THESE IM TABLES WERE NOT WELL 
>>> MATCHED
>>> chimp.> VBGLU3: CL table copied:   3980 rows containing data from 1 
>>> input files
>>> chimp.> VBGLU3: CL table copied:   1258 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3:     THIS SUGGESTS THAT THESE CL TABLES WERE NOT WELL 
>>> MATCHED
>>> chimp.> VBGLU3: MC table copied:   1302 rows containing data from 1 
>>> input files
>>> chimp.> VBGLU3: MC table copied:    311 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3:     THIS SUGGESTS THAT THESE MC TABLES WERE NOT WELL 
>>> MATCHED
>>> chimp.> VBGLU3: TY table copied:    980 rows containing data from 1 
>>> input files
>>> chimp.> VBGLU3: TY table copied:    280 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3:     THIS SUGGESTS THAT THESE TY TABLES WERE NOT WELL 
>>> MATCHED
>>> chimp.> VBGLU3: PC table copied:    542 rows containing data from 1 
>>> input files
>>> chimp.> VBGLU3: PC table copied:    109 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3:     THIS SUGGESTS THAT THESE PC TABLES WERE NOT WELL 
>>> MATCHED
>>> chimp.> VBGLU3: SU table copied:      2 rows containing data from 1 
>>> input files
>>> chimp.> VBGLU3: SU table copied:     28 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3: GC table copied:     32 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3: CQ table copied:      1 rows containing data from 2 
>>> input files
>>> chimp.> VBGLU3: CT table col. TRANGE1 not the same in row   6 in 
>>> files 1 and 2
>>> chimp.> VBGLU3: ******************************************************
>>> chimp.> VBGLU3: ** CT tables are not identical, will not copy to    **
>>> chimp.> VBGLU3: ** output dataset.  See EXPLAIN file for more info. **
>>> chimp.> VBGLU3: ******************************************************
>>> chimp.> VBGLU3: GLUTAB: CT tables not copied
>>> chimp.> VBGLU3: Run INDXR to create a new index (NX) table for the 
>>> output file
>>> chimp.> VBGLU3: Appears to have ended successfully
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Daip mailing list
>>> Daip at listmgr.cv.nrao.edu
>>> http://listmgr.cv.nrao.edu/mailman/listinfo/daip
>