[daip] Split CSLGET error
Arnaud Collioud
Arnaud.Collioud at obs.u-bordeaux1.fr
Fri Jun 21 09:18:17 EDT 2013
Hi Eric,
> I have read your data in (as I guessed the copy job finished before 11 pm despite the 2-3 day estimates it was getting during the day) and looked at the issues. I cannot get CSLGET to run off the end of the CL table as it did for you. However, I did find an issue with subarray 2 on the 1706-174 source that caused it to find no usable data. I have fixed that - so a MNJ on Thursday should correct that issue and (I hope) the other. Your CL table lacks entries for a lot of your data.
After applying the last MNJ, I tried again to split my data (with CL4).
It successfully worked for the source 1706-174. But I now have the same issue for 5 new sources.
BTW, I am using 31DEC13 on a Mac laptop (Snow Leopard 10.6.8) if that could be of any help...
1 2 21-JUN-2013 13:39:14 SPLIT Create 0454-234 .SPLIT . 6 (UV) on disk 1 cno 375
1 8 21-JUN-2013 13:39:29 SPLIT TABIO: BAD LRNO= 50581 LIMIT 50580
1 8 21-JUN-2013 13:39:29 SPLIT CSLGET: ERROR 2 READING CALIBRATION TABLE
1 4 21-JUN-2013 13:39:29 SPLIT Destroyed 1 extension files of type NX
1 4 21-JUN-2013 13:39:29 SPLIT Destroyed UV image file: catno= 375 disk= 1
1 6 21-JUN-2013 13:39:29 SPLIT PROBLEM WITH SOURCE: 0454-234
1 2 21-JUN-2013 13:39:31 SPLIT Create 1800+440 .SPLIT . 6 (UV) on disk 1 cno 376
1 8 21-JUN-2013 13:39:32 SPLIT TABIO: BAD LRNO= 50581 LIMIT 50580
1 8 21-JUN-2013 13:39:32 SPLIT CSLGET: ERROR 2 READING CALIBRATION TABLE
1 4 21-JUN-2013 13:39:32 SPLIT Destroyed 1 extension files of type NX
1 4 21-JUN-2013 13:39:32 SPLIT Destroyed UV image file: catno= 376 disk= 1
1 6 21-JUN-2013 13:39:32 SPLIT PROBLEM WITH SOURCE: 1800+440
1 2 21-JUN-2013 13:40:08 SPLIT Create 1424-418 .SPLIT . 6 (UV) on disk 1 cno 387
1 6 21-JUN-2013 13:40:09 SPLIT SPLCOP FOUND NO SAMPLES OUT OF 38107 POSSIBLE
1 6 21-JUN-2013 13:40:09 SPLIT IS SUBARRAY 2 IN CL/SN TABLE?
1 8 21-JUN-2013 13:40:10 SPLIT TABIO: BAD LRNO= 50581 LIMIT 50580
1 8 21-JUN-2013 13:40:10 SPLIT CSLGET: ERROR 2 READING CALIBRATION TABLE
1 4 21-JUN-2013 13:40:10 SPLIT Destroyed 1 extension files of type NX
1 4 21-JUN-2013 13:40:10 SPLIT Destroyed UV image file: catno= 387 disk= 1
1 6 21-JUN-2013 13:40:10 SPLIT PROBLEM WITH SOURCE: 1424-418
1 2 21-JUN-2013 13:39:37 SPLIT Create 0119+115 .SPLIT . 6 (UV) on disk 1 cno 378
1 8 21-JUN-2013 13:39:42 SPLIT TABIO: BAD LRNO= 50581 LIMIT 50580
1 8 21-JUN-2013 13:39:42 SPLIT CSLGET: ERROR 2 READING CALIBRATION TABLE
1 4 21-JUN-2013 13:39:42 SPLIT Destroyed 1 extension files of type NX
1 4 21-JUN-2013 13:39:42 SPLIT Destroyed UV image file: catno= 378 disk= 1
1 6 21-JUN-2013 13:39:42 SPLIT PROBLEM WITH SOURCE: 0119+115
1 2 21-JUN-2013 13:45:22 SPLIT Create 1546+027 .SPLIT . 6 (UV) on disk 1 cno 478
1 8 21-JUN-2013 13:45:28 SPLIT TABIO: BAD LRNO= 50581 LIMIT 50580
1 8 21-JUN-2013 13:45:28 SPLIT CSLGET: ERROR 2 READING CALIBRATION TABLE
1 4 21-JUN-2013 13:45:28 SPLIT Destroyed 1 extension files of type NX
1 4 21-JUN-2013 13:45:28 SPLIT Destroyed UV image file: catno= 478 disk= 1
1 6 21-JUN-2013 13:45:28 SPLIT PROBLEM WITH SOURCE: 1546+027
Finally, compared to the previous split execution, in this run...
I "lost" the sources :
0119+115 (*above*)
0454-234 (*above*)
1424-418 (*above*)
1546+027 (*above*)
1800+440 (*above*)
and I recover:
1706-174
2059+034
2355-106
Well, the problem seems not to be solved...especially if you cannot reproduce the issue.
> I don't know what you are doing - but if the subarrays are all really the same set of antennas with any particular antenna being in one subarray at one time and another at another time then you should be aware of the following. If the CL table column for subarray is zero, then it applies to all subarrays. The same is true of the source and frequency ID columns. You can force this with TABPUT or probably TABED.
Yes, all subarrays normally include the same stations. Some sources are observed by a given subnet (resulting in data in a given subarray) and a station cannot observe 2 sources at the same time.
Do you suggest I should put 0 in the subarray column of the CL table without any problem?
> For source however, care is needed. The CL table can contain amplitude and phase corrections that are very source dependent (clock, antenna and source position, atmosphere, antenna gain curves, etc.). If it has those, then you do not want to set the source column to zero.
>
> I will hang on to your file in case the new fix does not solve all issues. Thanks for your help.
No, thanks for *YOUR* help and time!
Cheers,
Arnaud
More information about the Daip
mailing list