[daip] UVFLG issue.
R. Craig Walker
cwalker at nrao.edu
Sun Jan 14 00:29:07 EST 2007
Something seems to be wrong with the zero fringe rate flagging
option in UVFLG. I have some very clean 18 cm data where the
effects of zero fringe rate correlation of pulse cal (or clipper
offset or whatever) is obvious so I'm trying to flag it. It
sort of works, but not completely. It looks like whether or
not you actually get a flag around a zero fringe rate time
depends on aparm(6). Here are some examples from what UVFLG
reports (some from message screen, some from PRTMSG):
aparm(6)=5
UVFLG2: Task UVFLG (release of 31DEC07) begins
UVFLG2: 3C48 1 - 5 0/ 2: 3:55.9 U= .00 V= 9005.86
UVFLG2: 3C120 6 - 7 0/ 2:21:38.9 U= .00 V= -8406.15
UVFLG2: 3C120 8 - 9 0/ 3: 9: 4.1 U= .00 V= 1925.58
UVFLG2: 3C120 3 -10 0/ 3:36:42.3 U= .00 V= 13901.46
UVFLG2: 3C120 1 - 2 0/ 5: 5:41.7 U= .00 V= 9125.39
UVFLG2: 3C120 1 - 4 0/ 6:28:52.7 U= .00 V= 8195.66
UVFLG2: 3C120 1 - 8 0/ 8:12:38.4 U= .00 V= 5295.38
UVFLG2: 0420-014 5 - 9 0/11:51:19.3 U= .00 V= 711.13
UVFLG2: 3C120 3 - 4 0/12: 9: 3.3 U= .00 V= 7089.26
UVFLG2: 3C120 3 - 8 0/12:45:60.0 U= .00 V= 4638.54
UVFLG2: 3C138 3 - 4 0/12:56:56.1 U= .00 V= 10598.26
UVFLG2: B0329+54 2 - 4 0/13:22:30.0 U= .00 V= 2891.88
UVFLG2: DA193 3 - 4 0/13:31:16.6 U= -.01 V= 16391.41
UVFLG2: 3C279 1 - 9 0/13:51:26.6 U= .00 V= 5528.61
UVFLG2: Writing flagging information in FG table 4
aparm(6) = 50
UVFLG2: Task UVFLG (release of 31DEC07) begins
UVFLG2: 3C120 6 - 7 0/ 2:21:38.9 U= .00 V= -8406.15
UVFLG2: 3C120 8 - 9 0/ 3: 9: 4.1 U= .00 V= 1925.58
UVFLG2: 3C120 3 -10 0/ 3:36:42.3 U= .00 V= 13901.46
UVFLG2: 3C120 1 - 2 0/ 5: 5:41.7 U= .00 V= 9125.39
UVFLG2: 3C120 1 - 4 0/ 6:28:52.7 U= .00 V= 8195.66
UVFLG2: 3C120 1 - 8 0/ 8:12:38.4 U= .00 V= 5295.38
UVFLG2: 0420-014 5 - 9 0/11:51:19.3 U= .00 V= 711.13
UVFLG2: 3C120 3 - 4 0/12: 9: 3.3 U= .00 V= 7089.26
UVFLG2: 3C120 3 - 8 0/12:45:60.0 U= .00 V= 4638.54
UVFLG2: 3C138 3 - 4 0/12:56:56.1 U= .00 V= 10598.26
UVFLG2: B0329+54 2 - 4 0/13:22:30.0 U= .00 V= 2891.88
UVFLG2: DA193 3 - 4 0/13:31:16.6 U= -.01 V= 16391.41
UVFLG2: 3C279 1 - 9 0/13:51:26.6 U= .00 V= 5528.61
UVFLG2: Writing flagging information in FG table 6
aparm(6) = 200
>UVFLG1: 3C48 1 - 5 0/ 2: 3:55.9 U= .00 V= 9005.86
UVFLG1: 3C120 3 -10 0/ 3:36:42.3 U= .00 V= 13901.46
UVFLG1: 3C120 1 - 2 0/ 5: 5:41.7 U= .00 V= 9125.39
UVFLG1: 3C120 1 - 5 0/ 4:58:55.5 U= .00 V= 6316.46
UVFLG1: 3C120 1 - 4 0/ 6:28:52.7 U= .00 V= 8195.66
UVFLG1: 3C120 1 - 8 0/ 8:12:38.4 U= .00 V= 5295.38
UVFLG1: 0420-014 5 - 9 0/11:51:19.3 U= .00 V= 711.13
UVFLG1: 3C120 3 - 4 0/12: 9: 3.3 U= .00 V= 7089.26
UVFLG1: 3C120 3 - 5 0/12: 6:38.9 U= .00 V= 4878.31
UVFLG1: 3C120 3 - 9 0/12: 6:18.7 U= .00 V= 5711.83
UVFLG1: 3C120 3 - 8 0/12:45:60.0 U= .00 V= 4638.54
UVFLG1: 3C138 3 - 4 0/12:56:56.1 U= .00 V= 10598.26
UVFLG1: B0329+54 2 - 4 0/13:22:30.0 U= .00 V= 2891.88
UVFLG1: DA193 3 - 4 0/13:31:16.6 U= -.01 V= 16391.41
UVFLG1: DA193 3 - 5 0/13:28:52.1 U= .00 V= 12970.50
UVFLG1: DA193 7 - 9 0/13:32:10.2 U= .00 V= 8152.12
UVFLG1: 3C279 1 - 9 0/13:51:26.6 U= .00 V= 5528.61
UVFLG1: Writing flagging information in FG table 2
aparm(6) = 1000
UVFLG2 21:37:18 Task UVFLG (release of 31DEC07) begins
UVFLG2 21:37:18 3C48 1 - 5 0/ 2: 3:55.9 U= .00 V= 9005.86
UVFLG2 21:37:18 3C120 6 - 7 0/ 2:21:38.9 U= .00 V= -8406.15
UVFLG2 21:37:18 3C120 8 - 9 0/ 3: 9: 4.1 U= .00 V= 1925.58
UVFLG2 21:37:18 3C120 3 -10 0/ 3:36:42.3 U= .00 V= 13901.46
UVFLG2 21:37:18 3C120 1 - 2 0/ 5: 5:41.7 U= .00 V= 9125.39
UVFLG2 21:37:18 3C120 1 - 5 0/ 4:58:55.5 U= .00 V= 6316.46
UVFLG2 21:37:18 3C120 1 - 4 0/ 6:28:52.7 U= .00 V= 8195.66
UVFLG2 21:37:18 3C120 1 - 8 0/ 8:12:38.4 U= .00 V= 5295.38
UVFLG2 21:37:18 0420-014 5 - 9 0/11:51:19.3 U= .00 V= 711.13
UVFLG2 21:37:18 3C120 3 - 4 0/12: 9: 3.3 U= .00 V= 7089.26
UVFLG2 21:37:18 3C120 3 - 5 0/12: 6:38.9 U= .00 V= 4878.31
UVFLG2 21:37:18 3C120 3 - 7 0/12: 2:50.9 U= .00 V= 1352.17
UVFLG2 21:37:18 3C120 3 - 9 0/12: 6:18.7 U= .00 V= 5711.83
UVFLG2 21:37:18 3C120 5 - 9 0/12: 1:14.0 U= .00 V= 833.54
UVFLG2 21:37:18 3C138 3 - 4 0/12:56:56.1 U= .00 V= 10598.26
UVFLG2 21:37:18 B0329+54 2 - 4 0/13:22:30.0 U= .00 V= 2891.88
UVFLG2 21:37:18 DA193 3 - 4 0/13:31:16.6 U= -.01 V= 16391.41
UVFLG2 21:37:18 DA193 3 - 5 0/13:28:52.1 U= .00 V= 12970.50
UVFLG2 21:37:18 DA193 7 - 9 0/13:32:10.2 U= .00 V= 8152.12
UVFLG2 21:37:18 3C279 1 - 9 0/13:51:26.6 U= .00 V= 5528.61
UVFLG2 21:37:18 Writing flagging information in FG table 4
Here is a scan listing to help identify events in and out of scans.
1 3C84 : 0000 V 1 0/01:28:52 - 0/01:42:34 1
1 17473
2 3C48 : 0000 V 1 0/01:43:35 - 0/01:51:20 1
17474 29584
3 B0329+54 : 0000 1 0/01:52:38 - 0/02:00:22 1
29585 39541
4 3C48 : 0000 V 1 0/02:01:39 - 0/02:09:25 1
39542 51717
5 B0329+54 : 0000 1 0/02:10:46 - 0/02:18:30 1
51718 61648
6 3C120 : 0000 V 1 0/02:19:58 - 0/02:37:41 1
61649 75894
7 B0329+54 : 0000 1 0/02:39:11 - 0/02:40:56 1
75895 78640
8 3C120 : 0000 V 1 0/02:42:22 - 0/03:00:06 1
78641 101241
9 3C48 : 0000 V 1 0/03:02:01 - 0/03:03:50 1
101242 103994
10 3C120 : 0000 V 1 0/03:05:47 - 0/03:23:31 1
103995 126815
11 3C138 : 0000 V 1 0/03:24:00 - 0/03:25:53 1
126816 129108
12 3C120 : 0000 V 1 0/03:26:31 - 0/03:44:16 1
129109 151908
13 3C138 : 0000 V 1 0/03:44:56 - 0/03:46:41 1
151909 154186
14 3C120 : 0000 V 1 0/03:47:23 - 0/04:05:02 1
154187 176849
15 0420-014 : 0000 V 1 0/04:05:19 - 0/04:07:20 1
176850 179478
16 3C120 : 0000 V 1 0/04:07:25 - 0/04:25:33 1
179479 198631
17 3C138 : 0000 V 1 0/04:26:32 - 0/04:28:17 1
198632 200891
18 3C120 : 0000 V 1 0/04:29:11 - 0/04:46:54 1
200892 223655
19 3C138 : 0000 V 1 0/04:47:59 - 0/04:49:44 1
223656 225923
20 3C120 : 0000 V 1 0/04:50:51 - 0/05:08:28 1
225924 248462
21 0420-014 : 0000 V 1 0/05:08:33 - 0/05:10:49 1
248463 251432
22 3C120 : 0000 V 1 0/05:10:53 - 0/05:29:10 1
251433 279362
23 3C138 : 0000 V 1 0/05:30:40 - 0/05:32:25 1
279363 281657
24 3C120 : 0000 V 1 0/05:33:57 - 0/05:51:40 1
281658 309534
25 3C84 : 0000 V 1 0/05:53:17 - 0/06:01:00 1
309535 321710
26 3C120 : 0000 V 1 0/06:02:37 - 0/06:20:18 1
321711 349398
First look at the 4C48 (1-5) flag at 02:03:55.9. That is inside the
time range of scan 4. For aparm(6) = 5, 200, or 1000, it is flagged.
For 50, it is not.
Then for the 3C120 (1-5) flag at 04:58:55.5, which I clearly see in
the data and which is inside scan 20, the flag is only there for
aparm(6) of 200 and 1000. Unfortunately, those high attenuation
factors cause too much data to be lost, so I don't want to use them.
But the flag should be there for the low attenuations too.
Looking at the actual FG tables, it is clearly not so simple as
indicated in the feedback to the user. Each zero crossing can
generate several flags to deal with wanting to flag data from several
scans and provide a separate flag for each IF. In fact the apar(6)
case generated 365 rows for 20 reported crossings. Also there are
some flags for crossings (or one anyway) that was not reported and
might possibly have its center outside the experiment. I'm suspicious
that the effort to relate crossings, flags, and scans is not fully
logically correct, but that is just a wild guess.
Meanwhile, it looks like I'll have to deal with the 3C120 even by hand
while doing most with a low aparm(6).
Cheers,
Craig
PS. Please excuse any nasty wrapping issues above caused by the web mail
tool. I don't seem to have any control over that with a cut and paste.
---------------------------------------------------------------------
R. Craig Walker Array Operations Center
cwalker at nrao.edu National Radio Astronomy Observatory
Phone 505 835 7247 P. O. Box O
Fax 505 835 7027 Socorro NM 87801 USA
--------------------------------------------------------------web
More information about the Daip
mailing list