Arecibo L-band Feed ArrayArecibo Galaxy Environment Survey (AGES)

AGES A2048 Observations & Results

Last Update:

Date Observer(s) Log file Output Files and Comments Comments
29/01/2008 RT RM wapp.20080129.a2048.0000 Scan: TOGS calibration, WAPP problems on beams 4, 5, 6. GALSPECT seems okay.
wapp.20080129.a2048.0001 Scan: AGES3193_p1_101, Aborted - WAPP failed to come good on restart
wapp.20080129.a2048.0003 Scan: AGES3193_p1_103, WAPPs now working - thanks Mikael! 05:26 UT - Beem 0B went bad (a bit over half way through the scan). Alarm for 0B amps went off 3 minutes later.
wapp.20080129.a2048.0004 Scan: AGES3193_p1_105, Finally, a scan where nothing happened (except for 0B continuing to wobble)
wapp.20080129.a2048.0005 Scan: AGES3193_p1_107, 
wapp.20080129.a2048.0006 Scan: AGES3193_p1_109, 
wapp.20080129.a2048.0007 Scan: AGES3193_p1_111, 
wapp.20080129.a2048.0008 Scan: AGESVC1A_p1_041, 6.5 min drive - made it!
wapp.20080129.a2048.0009 Scan: AGESVC1A_p1_043, 
wapp.20080129.a2048.0010 Scan: AGESVC1A_p1_045, 
wapp.20080129.a2048.0011 Scan: AGESVC1A_p1_047, 
wapp.20080129.a2048.0012 Scan: AGESVC1A_p1_049, 
wapp.20080129.a2048.0013 Scan: AGESVC1B_p1_041, First 3s (!) not on source
wapp.20080129.a2048.0014 Scan: AGESVC2_58, Follow-up with LBW
wapp.20080129.a2048.0015 Scan: AGESVC2_59, 
WAPP problems at start. The WAPPs got into single-board mode. The configuration had to be re-applied. They then crashed on a short 'run correlator'. After re-applying the configuration again they seem okay.
30/01/2008 RT RM wapp.20080130.a2048.0000 Scan: wapp.20080130.a2048.0000.fits, TOGS calibration
wapp.20080130.a2048.0001 Scan: AGES3193_p1_113, 
wapp.20080130.a2048.0002 Scan: AGES3193_p1_115, First two seconds not on source, oh deary me...
wapp.20080130.a2048.0003 Scan: AGES3193_p1_117, 
wapp.20080130.a2048.0004 Scan: AGES3193_p1_119, 
wapp.20080130.a2048.0005 Scan: AGES3193_p1_121, 
wapp.20080130.a2048.0006 Scan: AGES3193_p1_123, 
wapp.20080130.a2048.0007 Scan: AGESVC1A_p1_51, 
wapp.20080130.a2048.0008 Scan: AGESVC1A_p1_53, 
wapp.20080130.a2048.0009 Scan: AGESVC1A_p1_55, 
wapp.20080130.a2048.0010 Scan: AGESVC1A_p1_57, 
wapp.20080130.a2048.0011 Scan: AGESVC1A_p1_59, 
wapp.20080130.a2048.0012 Scan: AGESVC1B_p1_43, First four seconds off source
wapp.20080130.a2048.0013 Scan: AGESVC2_46, LBW follow up
31/01/2008 RT wapp.20080131.a2048.0000 Scan: TOGS calibration, 
wapp.20080131.a2048.0001 Scan: AGES3193_p1_125, 
wapp.20080131.a2048.0002 Scan: AGES3193_p1_127, 
wapp.20080131.a2048.0003 Scan: AGES3193_p1_129, 
wapp.20080131.a2048.0004 Scan: AGES3193_p1_131, 
wapp.20080131.a2048.0005 Scan: AGES3193_p1_133, 
wapp.20080131.a2048.0006 Scan: AGES3193_p1_135, 
wapp.20080131.a2048.0007 Scan: AGESVC1A_p1_61, 
wapp.20080131.a2048.0008 Scan: AGESVC1A_p1_63, 
wapp.20080131.a2048.0009 Scan: AGESVC1A_p1_65, 
wapp.20080131.a2048.0010 Scan: AGESVC1A_p1_67, 
wapp.20080131.a2048.0011 Scan: AGESVC1A_p1_69, 
wapp.20080131.a2048.0012 Scan: AGESVC1B_p1_45, First three seconds off-source
Beam OB appears stable again.
05/02/2008 RT wapp.20080205.a2048.0002 Scan: AGES3193_p1_47, 
wapp.20080205.a2048.0003 Scan: AGESVC1A_p1_71, 
wapp.20080205.a2048.0004 Scan: AGESVC1A_p1_73, 
wapp.20080205.a2048.0005 Scan: AGESVC1A_p1_75, 
wapp.20080205.a2048.0006 Scan: AGESVC1A_p1_77, 
wapp.20080205.a2048.0007 Scan: AGESVC1A_p1_79, 
wapp.20080205.a2048.0008 Scan: AGESVC1B_p1_47, First six seconds off source
During TOGS calibration scan, received an error "timed out waiting for ALFA rotation" despite ALFA being at required 19 degrees. TO investigated and ALFA can only be rotated anticlockwise. Problem was a loose cable, fixed with tape. First 2 hours lost. And beam OB is back down, just for good measure.
05/02/2008 RT wapp.20080205.a2048.0002 Scan: AGES3193_p1_47, 
wapp.20080205.a2048.0003 Scan: AGESVC1A_p1_71, 
wapp.20080205.a2048.0004 Scan: AGESVC1A_p1_73, 
wapp.20080205.a2048.0005 Scan: AGESVC1A_p1_75, 
wapp.20080205.a2048.0006 Scan: AGESVC1A_p1_77, 
wapp.20080205.a2048.0007 Scan: AGESVC1A_p1_79, 
wapp.20080205.a2048.0008 Scan: AGESVC1B_p1_47, First six seconds off source
During TOGS calibration scan, received an error "timed out waiting for ALFA rotation" despite ALFA being at required 19 degrees. TO investigated and ALFA can only be rotated anticlockwise. Problem was a loose cable, fixed with tape. First 2 hours lost. And beam OB is back down, just for good measure.
06/02/2008 RT wapp.20080206.a2048.0000 Scan: TOGS calibration, 
wapp.20080206.a2048.0001 Scan: AGES3193_p1_137, First seven seconds off source
wapp.20080206.a2048.0002 Scan: AGES3193_p1_139, First one second off source. How irritating.
wapp.20080206.a2048.0003 Scan: AGES3193_p1_141, First second off source.
wapp.20080206.a2048.0004 Scan: AGES3193_p1_143, 
wapp.20080206.a2048.0005 Scan: AGES3193_p1_145, First eight seconds off source
wapp.20080206.a2048.0006 Scan: AGES3193_p1_147, First seven seconds off source
wapp.20080206.a2048.0007 Scan: AGESVC1A_p1_81, WAPP errors, aborted
wapp.20080206.a2048.0010 Scan: AGESVC1A_p1_02, 
wapp.20080206.a2048.0011 Scan: AGESVC1A_p1_04, 
wapp.20080206.a2048.0012 Scan: AGESVC1A_p1_06, 
wapp.20080206.a2048.0013 Scan: AGESVC1A_p1_08, 
wapp.20080206.a2048.0014 Scan: AGESVC1B_p1_49, First seven seconds off source
wapp.20080206.a2048.0015 Scan: AGESVC2_44, 
Beam 0B continues to be an unpredictable yo-yo of mystery. "Timed out while waiting for ALFA rotation error" at start of scan 5. Re-ran the scan successfully. 0007-0009 had WAPP error "counts don't match between chip 0 and chip 10". TO informed that error not critical, aborted and resumed on next scan.
07/02/2008 RT wapp.20080207.a2048.0000 Scan: TOGS calibration, 
wapp.20080207.a2048.0001 Scan: AGES3193_p1_149, 
wapp.20080207.a2048.0002 Scan: AGESVC1A_p1_81, 
wapp.20080207.a2048.0003 Scan: AGESVC1A_p1_10, 
wapp.20080207.a2048.0004 Scan: AGESVC1A_p1_12, 
wapp.20080207.a2048.0005 Scan: AGESVC1A_p1_14, 
wapp.20080207.a2048.0006 Scan: AGESVC1A_p1_16, 
wapp.20080207.a2048.0007 Scan: AGESVC1B_p1_51, First seven seconds off source
wapp.20080207.a2048.0008 Scan: AGESVC2_50, L-wide follow up
14/02/2008 RM wapp.20080214.a2048.0000 Scan: AGES3193_p1_157, Mikael's new conditional 'LSTSLEW' seems to be working. 0B okay at start of scan
wapp.20080214.a2048.0001 Scan: AGES3193_p1_159, 
wapp.20080214.a2048.0002 Scan: AGESVC1A_p1_042, 
wapp.20080214.a2048.0003 Scan: AGESVC1A_p1_044, 
wapp.20080214.a2048.0004 Scan: AGESVC1A_p1_046, 
wapp.20080214.a2048.0005 Scan: AGESVC1A_p1_048, 
wapp.20080214.a2048.0006 Scan: AGESVC1A_p1_050, 
wapp.20080214.a2048.0007 Scan: TOGS Calibration, 
WAPP1 gave problems when WAPPS were restarted before observing, but re-restarted itself successfully. Transition from VC1A from VC1B was too tight so the conditional statement jumped the last scan. This needs to be given slightly more time.
16/02/2008 RM wapp.20080216.a2048.0000 Scan: TOGS Calibration, 
wapp.20080216.a2048.0001 Scan: AGES3193_p1_151, Started not on source. Running a little under 1 min late due to TOGS calibration overrunning.
wapp.20080217.a2048.0000 Scan: AGES3193_p1_153, Midnight roll-over. File numbers reset. Date now 17/02/2008
wapp.20080217.a2048.0001 Scan: AGES3193_p1_155, 
wapp.20080217.a2048.0002 Scan: AGES3193_p1_161, 
wapp.20080217.a2048.0003 Scan: AGES3193_p1_060, Even-numbered scans only through the central region. L3 beacon
wapp.20080217.a2048.0004 Scan: AGES3193_p1_062, 
wapp.20080217.a2048.0005 Scan: AGESVC1A_p1_052, 
wapp.20080217.a2048.0006 Scan: AGESVC1A_p1_054, 
wapp.20080217.a2048.0007 Scan: AGESVC1A_p1_056, 
wapp.20080217.a2048.0008 Scan: AGESVC1A_p1_058, 
wapp.20080217.a2048.0009 Scan: AGESVC1A_p1_060, 
wapp.20080217.a2048.0010 Scan: AGESVC1B_p1_053, 
Very bright, short-lived RFI at 1339.4 MHz at 07:32:40 - 07:32:45 in beam 4, 07:32:50 in beam 0. Less strong in other beams.
18/03/2008 RM wapp.20080318.a2048.0000 Scan: TOGS calibration, 
wapp.20080318.a2048.0001 Scan: AGES3193_p1_064, 
wapp.20080318.a2048.0002 Scan: AGES3193_p1_066, 
wapp.20080319.a2048.0000 Scan: AGESVC1_p1_062, Wrong Catalogue! Aborted.
wapp.20080319.a2048.0001 Scan: AGESVC1A_p1_062, Slightly late start
wapp.20080319.a2048.0002 Scan: AGESVC1A_p1_064, 
wapp.20080319.a2048.0003 Scan: AGESVC1A_p1_066, 
wapp.20080319.a2048.0004 Scan: AGESVC1A_p1_068, 
1350 radar.
13/04/2008 KLO wapp.20080413.a2048.e.g. (0001) Scan: scan name, 
wapp.20080413.a2048.0028 Scan: calibration, got "warning there are wapp channels with too little power"
wapp.20080413.a2048.0029 Scan: agesvc1A_p1_070, warning RA has already passed -- starting anyway
wapp.20080413.a2048.0030 Scan: agesvc1A_p1_070, got "warning there are wapp channels with too little power (~.48 < 0.8)"
wapp.20080413.a2048.0031 Scan: calibration, 
wapp.20080413.a2048.0032 Scan: agesvc1A_p1_072, 
wapp.20080413.a2048.0033 Scan: agesvc1A_p1_072, getting a warning that observing started when not on source (by 9 seconds); still have "too little power" warning; got hit by 1381 MHz rfi
wapp.20080413.a2048.0034 Scan: calibration, 
wapp.20080413.a2048.0035 Scan: agesvc1A_p1_074, 
wapp.20080413.a2048.0036 Scan: agesvc1A_p1_074, Getting a warning that observing started when not on source (by 4 seconds); still have "too little power" warning;
wapp.20080413.a2048.0001 Scan: calibration, 
wapp.20080413.a2048.0002 Scan: agesvc1A_p1_076, 
wapp.20080413.a2048.0003 Scan: agesvc1A_p1_076, Getting a warning that observing started when not on source (by 8 seconds); still have "too little power" warning;
wapp.20080413.a2048.0004 Scan: calibration, 
wapp.20080413.a2048.0005 Scan: agesvc1A_p1_078, 
wapp.20080413.a2048.0006 Scan: agesvc1A_p1_078, Getting a warning that observing started when not on source (by 7 seconds); still have "too little power" warning;
I had to run the "unusable" cima version to get things working (version 2.3.xx from 2008-04-12) based off advice from Mikhail.

Got three main warnings:
RA has passed, started anyway;
Warning observing when not on source (lasted 4-10 s)
WAPP channels with too little power (4.7 < 0.8) [but the data looked ok]
The observing file did not finish, due to the earlier lost time

14/04/2008 klo wapp.20080414.a2048.0002 Scan: AGESVC1A_p1_070, Got started a few minutes early; All looks ok
wapp.20080414.a2048.0003 Scan: AGESVC1A_p1_072, 
wapp.20080414.a2048.0004 Scan: AGESVC1A_p1_074, 
wapp.20080414.a2048.0005 Scan: AGESVC1A_p1_076, 
wapp.20080414.a2048.0006 Scan: AGESVC1A_p1_078, 
wapp.20080414.a2048.0008 Scan: AGESVC1B_p1_055, Got "observing when not on source" error for 7 seconds
I again got numerous messages saying there was too little power in some WAPP channels (0.5 < 0.8)
Finished early (about 15 minutes)
Note that all TOGS observations claimed to be observing when not on source :(
15/04/2008 klo wapp.20080415.a2048.0002 Scan: TOGS calibration, I had to restart during this command as the telescope slew was locked.
wapp.20080415.a2048.0003 Scan: AGES3193_p1_068, got "not on source" warning, but looks ok.
wapp.20080415.a2048.0004 Scan: AGES3193_p1_070, aborted, as we seemd too far off source
wapp.20080415.a2048.0005 Scan: AGES3193_p1_072, 
wapp.20080415.a2048.0006 Scan: AGES3193_p1_074, 
wapp.20080415.a2048.0007 Scan: AGES3193_p1_076, 
wapp.20080415.a2048.0008 Scan: AGES3193_p1_078, 
Scan 3 got warning: Warning: received duplicate AGC-datablock at 20:0127.299 (seconds 72087.299) Warning: extrapolating agc-datablock from 72086.0 to 72087.0 Warning: interpolating agc-data over 2.00 second time gap (72086.0 - 72088.0)
16/04/2008 klo wapp..a2048.0000 Scan: togs calibration, 
wapp..a2048.0001 Scan: AGES3193_p1_070, 
wapp..a2048.0002 Scan: AGES3193_p1_080, 
wapp..a2048.0003 Scan: AGES3193_p1_082, 
wapp..a2048.0004 Scan: AGES3193_p1_084, 
wapp..a2048.0005 Scan: AGES3193_p1_086, 
wapp..a2048.0006 Scan: AGES3193_p1_088, 
17/04/2008 klo wapp..a2048.0001 Scan: AGES3193_p1_092, 
wapp..a2048.0002 Scan: AGES3193_p1_094, 
wapp..a2048.0003 Scan: AGES3193_p1_096, 
wapp..a2048.0004 Scan: AGES3193_p1_098, wapp channels with too much power (1.559 > 1.4), (1.413 > 1.4)
wapp..a2048.0005 Scan: AGES3193_p1_100, 
wapp..a2048.0006 Scan: TOGS Calibration, 
Ran into problem at the start - 'aog generic if2Prog@da err 0x3f70010'- phil and mikael came in and fixed it.
skipped the togs script to save time
skipped first source as well (aborted scan)
18/04/2008 SS wapp.20080418.a2048.e.g. (0001) Scan: scan name, Any Comments?
wapp.20080418.a2048.0000 Scan: TOGS calibration, 
wapp.20080418.a2048.0001 Scan: AGES3193_pl_102, on source about 7sec late
wapp.20080418.a2048.0002 Scan: AGES3193_pl_104, 
wapp.20080418.a2048.0003 Scan: AGES3193_pl_106, 
wapp.20080418.a2048.0004 Scan: AGES3193_pl_108, 
wapp.20080418.a2048.0005 Scan: AGES3193_pl_110, 
wapp.20080418.a2048.0006 Scan: AGES3193_pl_112, 
wapp.20080418.a2048.0007 Scan: TOGS calibration, 
I need a bigger screen!
21/04/2008 SS wapp.20080421.a2048.e.g. (0001) Scan: scan name, Any Comments?
wapp.20080421.a2048.0000 Scan: TOGS calibration, 
wapp.20080421.a2048.0001 Scan: AGES3193_pl_114, 
wapp.20080421.a2048.0002 Scan: AGES3193_pl_116, duplicate AGC datablock warning?
wapp.20080421.a2048.0003 Scan: AGES3193_pl_118, 
wapp.20080421.a2048.0004 Scan: AGES3193_pl_120, 
wapp.20080421.a2048.0005 Scan: AGES3193_pl_122, 
wapp.20080421.a2048.0006 Scan: AGES3193_pl_124, 
22/04/2008 KLO wapp.20080422.a2048.0000 Scan: ROGS Calibration, 
wapp.20080422.a2048.0001 Scan: AGES3193_p1_126, 
wapp.20080422.a2048.0002 Scan: AGES3193_p1_128, 
wapp.20080422.a2048.0003 Scan: AGES3193_p1_130, 
wapp.20080422.a2048.0004 Scan: AGES3193_p1_132, 
wapp.20080422.a2048.0005 Scan: AGES3193_p1_134, 
wapp.20080422.a2048.0006 Scan: AGES3193_p1_136, 
wapp.20080422.a2048.0007 Scan: TOG Calibration, 
23/04/2008 SS wapp.20080423.a2048.e.g. (0001) Scan: scan name, Any Comments?
wapp.20080423.a2048.0000 Scan: TOGS calibration, 
wapp.20080423.a2048.0001 Scan: AGES3193_p1_138, 
wapp.20080423.a2048.0002 Scan: AGES3193_p1_140, 
wapp.20080423.a2048.0003 Scan: AGES3193_p1_142, 
wapp.20080423.a2048.0004 Scan: AGES3193_p1_144, 
wapp.20080423.a2048.0005 Scan: AGES3193_p1_146, 
wapp.20080423.a2048.0006 Scan: AGES3193_p1_148, 
wapp.20080423.a2048.0007 Scan: AGESVC1A_p1_080, 
wapp.20080423.a2048.0008 Scan: AGESVC1A_p2_041, a couple of warnings of chan. with low power
wapp.20080423.a2048.0009 Scan: AGESVC1A_p2_043, 
wapp.20080423.a2048.0010 Scan: AGESVC1A_p2_045, 
wapp.20080423.a2048.0011 Scan: AGESVC1A_p2_047, 
wapp.20080423.a2048.0012 Scan: AGESVC1B_p1_057, power and "counts don't match" warnings
received a duplicate AGC datablock warning about 13 minutes into each of first 3 scans.
24/04/2008 KLO wapp.20080424.a2048.0000 Scan: TOGS Calibration, galfatsrcpos
wapp.20080424.a2048.0001 Scan: AGES3193_p1_150, Got lots of messages that there are WAPP channels with too little power (0.6-0.7)
wapp.20080424.a2048.0002 Scan: AGES3193_p1_152, Got lots of messages that there are WAPP channels with too little power (0.6-0.7)
wapp.20080424.a2048.0003 Scan: AGES3193_p1_154, 
wapp.20080424.a2048.0004 Scan: AGES3193_p1_156, 
wapp.20080424.a2048.0005 Scan: AGES3193_p1_158, GPS 1381MHz RFI
wapp.20080424.a2048.0006 Scan: AGES3193_p1_160, 
wapp.20080424.a2048.0007 Scan: AGESVC1A_p2_049, 
wapp.20080424.a2048.0008 Scan: AGESVC1A_p2_051, Got errors that the WAPP power was ~8.2 in some channels!
wapp.20080424.a2048.0009 Scan: AGESVC1A_p2_053, dupkicate datablock error from 80602 to 80604; data was interpolated over that time
wapp.20080424.a2048.0010 Scan: AGESVC1A_p2_055, dupkicate datablock error from 82400 to 82402; data was interpolated over that time
wapp.20080424.a2048.0011 Scan: AGESVC1A_p2_057, 
wapp.20080424.a2048.0012 Scan: AGESVC1A_p2_059, GPS 1381MHz RFI; dupkicate datablock error from 85097 to 85099; data was interpolated over that time
wapp.20080424.a2048.0013 Scan: TOGs calibration, galfatcurpos
25/04/2008 EM, RM wapp.20080425.a2048.0000 Scan: TOGS calibration, 
wapp.20080425.a2048.0001 Scan: AGES3193_p2_001, 
wapp.20080425.a2048.0002 Scan: AGES3193_p2_003, 
wapp.20080425.a2048.0003 Scan: AGES3193_p2_005, 
wapp.20080425.a2048.0004 Scan: AGES3193_p2_007, 
wapp.20080425.a2048.0005 Scan: AGES3193_p2_009, strong GPS
wapp.20080425.a2048.0006 Scan: AGES3193_p2_011, GPS
wapp.20080425.a2048.0007 Scan: AGESVC1A_p2_059, 
wapp.20080425.a2048.0008 Scan: AGESVC1A_p2_061, 
wapp.20080425.a2048.0009 Scan: AGESVC1A_p2_063, 
wapp.20080425.a2048.0010 Scan: AGESVC1A_p2_065, 
wapp.20080425.a2048.0011 Scan: AGESVC1A_p2_067, 
wapp.20080425.a2048.0012 Scan: AGESVC1B_p1_061, 
FAA 1350 MHz radar seems to be off.
26/04/2008 SS wapp.20080426.a2048.0000 Scan: TOGS calibration, 
wapp.20080426.a2048.0001 Scan: AGES3193_p2_013, 
wapp.20080426.a2048.0002 Scan: AGES3193_p2_015, 
wapp.20080426.a2048.0003 Scan: AGES3193_p2_017, 
wapp.20080426.a2048.0004 Scan: AGES3193_p2_019, 
wapp.20080426.a2048.0005 Scan: AGES3193_p2_021, 
wapp.20080426.a2048.0006 Scan: AGES3193_p2_023, 
wapp.20080426.a2048.0007 Scan: AGESVC1A_p2_069, 
wapp.20080426.a2048.0008 Scan: AGESVC1A_p2_071, 
wapp.20080426.a2048.0009 Scan: AGESVC1A_p2_073, counts don't match error
wapp.20080426.a2048.0010 Scan: AGESVC1A_p2_075, 
wapp.20080426.a2048.0011 Scan: AGESVC1A_p2_077, 
wapp.20080426.a2048.0012 Scan: AGESVC1B_p1_063, several too little power warnings
tiedowns were not working until 8:45 pm because of bad weather.
several scans had duplicate AGC datablock warnings.
27/04/2008 SS wapp.20080427.a2048.0000 Scan: TOGS calibration, 
wapp.20080427.a2048.0001 Scan: AGES3193_p2_025, 
wapp.20080427.a2048.0002 Scan: AGES3193_p2_027, 
wapp.20080427.a2048.0003 Scan: AGES3193_p2_029 , 
wapp.20080427.a2048.0004 Scan: AGES3193_p2_031, better check to see if end of this scan is ok
wapp.20080427.a2048.0005 Scan: AGESVC1A_p2_079, 
wapp.20080427.a2048.0006 Scan: AGESVC1A_p2_081, 
wapp.20080427.a2048.0007 Scan: AGESVC1A_p2_042, 
wapp.20080427.a2048.0008 Scan: AGESVC1A_p2_044, 
wapp.20080427.a2048.0009 Scan: AGESVC1A_p2_046, 
wapp.20080427.a2048.0010 Scan: AGESVC1B_p1_065, a few minutes short--aborted
Everything looked pretty nominal until about 20:30 at start of what would have been new scan. Received errors saying "failed configuration" problem with setcal, etc. Tried restarting wapps, restarting cima, but errors continued.
Mikael did some troubleshooting. There was a problem with the correlator. After he restarted it, we restarted cima again and were able to observing after losing about 70 min. Sources after break reported being off source for a few seconds at start of scans.
28/04/2008 SS wapp.20080428.a2048.0000 Scan: TOGS calibration, 
wapp.20080428.a2048.0001 Scan: AGES3193_p2_031, 
wapp.20080428.a2048.0002 Scan: AGES3193_p2_033, 
wapp.20080428.a2048.0003 Scan: AGES3193_p2_035, 
wapp.20080428.a2048.0004 Scan: AGES3193_p2_037, 
wapp.20080428.a2048.0005 Scan: AGES3193_p2_039, 
wapp.20080428.a2048.0006 Scan: AGES3193_p2_041, 
wapp.20080428.a2048.0007 Scan: AGESVC1A_p2_048, 
wapp.20080428.a2048.0008 Scan: AGESVC1A_p2_050, 
wapp.20080428.a2048.0009 Scan: AGESVC1A_p2_052, 
wapp.20080428.a2048.0010 Scan: AGESVC1A_p2_054, 
wapp.20080428.a2048.0011 Scan: AGESVC1A_p2_056, many "too little power" warnings
wapp.20080428.a2048.0012 Scan: AGESVC1B_p1_065, many "too little power" warnings
29/05/2008 KLO wapp.20080429.a2048.0000 Scan: TOGs Calibration, 
wapp.20080429.a2048.0001 Scan: AGES3193_p1_002, Had to wait ~19 minutes to start;Many times had wapp channels with too little power (~0.6-0.7)
wapp.20080429.a2048.0002 Scan: AGES3193_p1_004, 
wapp.20080429.a2048.0003 Scan: AGES3193_p1_006, 
wapp.20080429.a2048.0004 Scan: AGES3193_p1_008, Duplicate AGC datablock from 72930-72932;
wapp.20080429.a2048.0005 Scan: AGES3193_p1_010, GPS L3
wapp.20080429.a2048.0006 Scan: AGES3193_p1_012, 
wapp.20080429.a2048.0007 Scan: AGESVC1A_p2_058, 
wapp.20080429.a2048.0008 Scan: AGESVC1A_p2_060, 
wapp.20080429.a2048.0009 Scan: AGESVC1A_p2_062, 
wapp.20080429.a2048.0010 Scan: AGESVC1A_p2_064, 
wapp.20080429.a2048.0011 Scan: AGESVC1A_p2_066, Had to wait ~19 minutes to start;Many times had wapp channels with too little power(~0.6-0.7)
wapp.20080429.a2048.0012 Scan: AGESVC1A_p2_067, Had to wait ~19 minutes to start;Many times had wapp channels with too little power(~0.6-0.7)
wapp.20080429.a2048.0013 Scan: TOGs Calibration, 
The first AGES scan had power problems, as usual.
30/04/2008 SS wapp.20080430.a2048.0000 Scan: TOGS calibration, 
wapp.20080430.a2048.0001 Scan: AGES3193_p1_014, lots of "too little power" warnings
wapp.20080430.a2048.0002 Scan: AGES3193_p1_016, again
wapp.20080430.a2048.0003 Scan: AGES3193_p1_018, 
wapp.20080430.a2048.0004 Scan: AGES3193_p1_020, 
wapp.20080430.a2048.0005 Scan: AGES3193_p1_022, 
wapp.20080430.a2048.0006 Scan: AGES3193_p1_024, 
wapp.20080430.a2048.0007 Scan: AGESVC1A_p2_068, 
wapp.20080430.a2048.0008 Scan: AGESVC1A_p2_070, 
wapp.20080430.a2048.0009 Scan: AGESVC1A_p2_072, 
wapp.20080430.a2048.0010 Scan: AGESVC1A_p2_074, 
wapp.20080430.a2048.0011 Scan: AGESVC1A_p2_076, "too little power" warnings again
wapp.20080430.a2048.0012 Scan: AGESVC1B_p1_069, and again
01/05/2008 SS wapp.20080501.a2048.0000 Scan: TOGS calibration, 
wapp.20080501.a2048.0001 Scan: AGES3193_p1_026, lots of "too little power" warnings
wapp.20080501.a2048.0002 Scan: AGES3193_p1_028, again
wapp.20080501.a2048.0003 Scan: AGES3193_p1_030, 
wapp.20080501.a2048.0004 Scan: AGES3193_p1_032, 
wapp.20080501.a2048.0005 Scan: AGES3193_p1_034, 
wapp.20080501.a2048.0006 Scan: AGES3193_p1_036, 
wapp.20080501.a2048.0007 Scan: AGESVC1A_p2_078, 
wapp.20080501.a2048.0008 Scan: AGESVC1A_p2_080, 
wapp.20080501.a2048.0009 Scan: AGESVC1A_p3_041, 
wapp.20080501.a2048.0010 Scan: AGESVC1A_p3_043, 
wapp.20080501.a2048.0011 Scan: AGESVC1A_p3_045, 
wapp.20080501.a2048.0012 Scan: AGESVC1B_p1_071, 
02/05/2008 SS wapp.20080502.a2048.0000 Scan: TOGS calibration, 
wapp.20080502.a2048.0001 Scan: AGES3193_p1_038, lots of "too little power" warnings
wapp.20080502.a2048.0002 Scan: AGES3193_p1_040, 
wapp.20080502.a2048.0003 Scan: AGES3193_p1_042, 
wapp.20080502.a2048.0004 Scan: AGES3193_p1_044, 
wapp.20080502.a2048.0005 Scan: AGES3193_p1_046, 
wapp.20080502.a2048.0006 Scan: AGES3193_p1_048, lots of "too little power" warnings
wapp.20080502.a2048.0007 Scan: AGESVC1A_p3_047, 
wapp.20080502.a2048.0008 Scan: AGESVC1A_p3_049, 
wapp.20080502.a2048.0009 Scan: AGESVC1A_p3_051, 
wapp.20080502.a2048.0010 Scan: AGESVC1A_p3_053, 
wapp.20080502.a2048.0011 Scan: AGESVC1A_p3_055, 
wapp.20080502.a2048.0012 Scan: AGESVC1B_p1_073, 
03/05/2008 EM wapp.20080503.a2048.0000 Scan: TOGS calibration, 
wapp.20080503.a2048.0001 Scan: AGES3193_p1_050, too little power warnings on WAPP channels
wapp.20080503.a2048.0002 Scan: AGES3193_p1_052, too little power warnings on WAPP channels
wapp.20080503.a2048.0003 Scan: AGES3193_p1_054, too little power warnings on WAPP channels
wapp.20080503.a2048.0004 Scan: AGES3193_p1_056, 
wapp.20080503.a2048.0005 Scan: AGES3193_p1_058, too much power warnings on WAPP channels. GPS burst around the end of the scan.
wapp.20080503.a2048.0006 Scan: AGES3193_p1_060, 
wapp.20080503.a2048.0007 Scan: AGESVC1A_p3_057, 
wapp.20080503.a2048.0008 Scan: AGESVC1A_p3_059, too little power warnings on WAPP channels
wapp.20080503.a2048.0009 Scan: AGESVC1A_p3_061, scan failed, error azimuth position -0.36 reported! changed it to +0.36 (so scan started late and was termintated a few minutes early to start the following scan on time)
wapp.20080503.a2048.0010 Scan: AGESVC1A_p3_063, beam 5 shows a strong burst at 1339 MHz that lasted for about 9 secs.
wapp.20080503.a2048.0011 Scan: AGESVC1A_p3_065, 
wapp.20080503.a2048.0012 Scan: AGESVC1B_p1_075, too little power warnings on WAPP channels
Scan AGESVC1A_p3_061 (FITS file # 0009) is incomplete (started late and ended early).

Beam 5 (both pols) showed a burst at 1339 MHz in scan AGESVC1A_p3_063 (FITS # 0010).
09/05/2008 LC wapp.20080509.a2048.0000 Scan: TOGS calibration, Warning: there are WAPP channel with too much power
wapp.20080509.a2048.0001 Scan: AGESVC1A_p3_061, 
wapp.20080509.a2048.0002 Scan: AGESVC1A_p3_067, 
wapp.20080509.a2048.0003 Scan: AGESVC1A_p3_069, 
wapp.20080509.a2048.0004 Scan: AGESVC1A_p3_071, 
wapp.20080509.a2048.0005 Scan: AGESVC1A_p3_073, 
wapp.20080509.a2048.0006 Scan: AGESVC1B_p1_077, 
wapp.20080509.a2048.0007 Scan: TOGS calibration, Warning: there are WAPP channel with too much power
Overall, smooth run.

Problems at the start with the ALFA on-line display. Another version was still running. Problem solved before the start of AGES obs.

At the start of the first AGES scan, got Warning: failed to get a response from the CIMA fronted when checking options for 'fixed azimuth drift map', even if the window was already active. However, it should not be a problem and I have double checked all the parameters.

For each scan, got Warning: there are WAPP channels with too much power during the ON calibration at the beginning of the scan.

FAA 1350 MHz radar seems to be off or, at least, extremely weak.

RFI @1340MHz
10/05/2008 LC wapp.20080510.a2048.0000 Scan: TOGS calibration, 
Warning: there are WAPP channel with too much power.
Warning: received duplicate AGC datablock at 20:27:53.301.

wapp.20080510.a2048.0001 Scan: AGESVC1A_p3_075, 
wapp.20080510.a2048.0002 Scan: AGESVC1A_p3_077, 
Warning received duplicate AGC-datablock at 20:57:51.302.
Warning WAPP=4: counts don't match at 21:08:06

wapp.20080510.a2048.0003 Scan: AGESVC1A_p3_079, 
Strong GPS burst @~1380.5-1382 MHz from ~01:22:55 to ~01:23:32.
Warning: received duplicate AGC-datablock at 21:27:49.322.

wapp.20080510.a2048.0004 Scan: AGESVC1A_p3_081, 
wapp.20080510.a2048.0005 Scan: AGESVC1A_p3_042, 
Warning received duplicate AGC-datablock at 22:12:46.303.

wapp.20080510.a2048.0006 Scan: AGESVC1B_p1_079, 
First 13s not on source! On source from 22:26:41.
Warning WAPP=4: counts don't match at 22:26:32

wapp.20080510.a2048.0007 Scan: TOGS calibration, 
Warning: there are WAPP channel with too much power.
Significant problems only for the last scan: AGESVC1B_p1_079, first 13sec not on source!

At the start of the first AGES scan, got againWarning: failed to get a response from the CIMA fronted when checking options for 'fixed azimuth drift map'. This time the window wasn't already open, but the warning is instantaneous (~1 sec!) and there is no time to place the window. Anyway, it should not be a problem and I have double checked all the parameters.

Duplicate AGC warnings for a few scans.

AGESVC1A_p3_077 & AGESVC1B_p1_079. Warning WAPP=4: counts don't match. Data appear ok and TO says it is usually a false allarm (as also suggested in previous AGES logs). So I completed the scans.

For every scan, got Warning: there are WAPP channels with too much power during the calibration at the beginning of the scan.

FAA 1350 MHz radar seems to be off or, at least, extremely weak.

RFI @1340MHz
11/05/2008 LC wapp.20080511.a2048.0000 Scan: TOGS calibration, 
wapp.20080511.a2048.0001 Scan: AGESVC1A_p3_044, Warning: received duplicate AGC datablock at 20:41:16.
wapp.20080511.a2048.0002 Scan: AGESVC1A_p3_046, Warning: received duplicate AGC datablock at 21:11:14.
wapp.20080511.a2048.0003 Scan: AGESVC1A_p3_048, 
wapp.20080511.a2048.0004 Scan: AGESVC1A_p3_050, Warning: received duplicate AGC datablock at 21:41:12 and at 21:56:11.
wapp.20080511.a2048.0005 Scan: AGESVC1A_p3_052, Warning: received duplicate AGC datablock at 22:11:10.
wapp.20080511.a2048.0006 Scan: AGESVC1B_p1_081, Warning: received duplicate AGC datablock at 22:26:09.
wapp.20080511.a2048.0007 Scan: TOGS calibration, 
All ok!

Duplicate AGC warnings for almost all scans.

For all scans, WAPP too much power warning during the calibration at the beginning of the scan.

RFI @1340MHz
12/05/2008 LC wapp.20080512.a2048.0000 Scan: TOGS calibration, 
wapp.20080512.a2048.0001 Scan: AGESVC1A_p3_054, 
Strong GPS @1381MHz from UT ~00:28:52 to 00:30:12.
Warning: received duplicate AGC datablock at 20:24:41.

wapp.20080512.a2048.0002 Scan: AGESVC1A_p3_056, Hundreds of Warnings counts do not match ABORTED: DO NOT USE
wapp.20080512.a2048.0003 Scan: AGESVC1A_p3_056, Hundreds of Warnings counts do not match ABORTED: DO NOT USE
wapp.20080512.a2048.0004 Scan: AGESVC1A_p3_056, Hundreds of Warnings counts do not match ABORTED: DO NOT USE

wapp.20080512.a2048.0005 Scan: AGESVC1A_p3_058, 
Strong GPS @1381MHz from UT ~01:16:17 to 01:17:30.
Warnings counts do not match every second until 21:24:22.
Warning received duplicate AGC-datablock at 21:24:37.
wapp.20080512.a2048.0006 Scan: AGESVC1A_p3_060, 
wapp.20080512.a2048.0007 Scan: AGESVC1A_p3_062, 
wapp.20080512.a2048.0008 Scan: AGESVC1B_p1_042, 
First 8 seconds not on source!
Everything fine, until the start of scan AGESVC1A_p3_056 when I started to get hundreds of warningsWAPP4 counts to not match (one every second). Since warnings didn't stop, I tried to abort the scan, restart WAPPS and restart the obs. However problem remained. TO contacted Mikeal who informed that as long as the difference between counts is small (e.g. 2 in my case) the data are ok, even if a new warning appears every second. If the difference starts to increase (e.g. ~1000) then data are not usable. Moreover he explained that, in this case, restart WAPP does not help because it is a software boot whereas the problem is hardware related.
AGESVC1A_p3_056 needs to be re-observed.

AGESVC1B_p1_042 first 8 seconds not on source!

Duplicate AGC warnings in some scans.

For all scans, WAPP too much power warning during the calibration at the beginning of the scan.

At the beginning of the first AGES scan got Warning: failed to get a response from the CIMA fronted when checking options for 'fixed azimuth drift map'.

RFI @1340MHz
13/05/2008 RT wapp.20080513.a2048.0000 Scan: TOGS calibration, Got several warnings "there are WAPP channels with too much power"
wapp.20080513.a2048.0001 Scan: AGESVC1A_p3_056, 
wapp.20080513.a2048.0002 Scan: AGESVC1A_p3_064, 
wapp.20080513.a2048.0003 Scan: AGESVC1A_p3_066, 
wapp.20080513.a2048.0004 Scan: AGESVC1A_p3_068, 
wapp.20080513.a2048.0005 Scan: AGESVC1A_p3_070, 
wapp.20080513.a2048.0006 Scan: AGESVC1B_p1_044, First 7 seconds off source. AGC datablock warnings.
wapp.20080513.a2048.0007 Scan: TOGS calibration, Warnings of WAPP channels with too much power
Just like being in Arecibo, but without the coquis or overpowered air conditioning....
The FAA radar seems off or at least much weaker.
For all scans, got a too much power warning during calibration.
14/05/2008 RM wapp.20080514.a2048.0000 Scan: TOGS Calibration, Beam 0 still looks dodgy on TOGS display, but looks okay on the 'Quickview' display.
wapp.20080514.a2048.0001 Scan: AGESVC1A_p3_072, 
wapp.20080514.a2048.0002 Scan: AGESVC1A_p3_074, 
wapp.20080514.a2048.0003 Scan: AGESVC1A_p3_076, 
wapp.20080514.a2048.0004 Scan: AGESVC1A_p3_078, 
wapp.20080514.a2048.0005 Scan: AGESVC1A_p3_080, 
wapp.20080514.a2048.0006 Scan: AGESVC1B_p1_046, Huge numbers of 'counts don't match' errors. Irritating (particularly as the computer keeps beeping - one advantage of remote observing!), but seemingly not a problem.
Very little interference today. Smooth run for the most part.
15/05/2008 RM wapp.20080515.a2048.0000 Scan: TOGS Calibration, 
wapp.20080515.a2048.0001 Scan: AGESVC1B_p1_046, Got warning 'failed to get a response from the CIMA frontend when checking options for 'fixed azimuth drift map'! Assuming that options are okay'. Fixed azimuth drift map is shown in CIMA observe window, so I don't know what caused this! Not enough time after TOGS to get a scan of VC1A in, so a long wait for VC1B to rise. Doing p1_046 again due to last nights chip-count issues.
wapp.20080515.a2048.0002 Scan: AGESVC1B_p1_048, 
wapp.20080515.a2048.0003 Scan: AGESVC1B_p1_050, 
wapp.20080515.a2048.0004 Scan: AGESVC1B_p1_052, 
wapp.20080515.a2048.0005 Scan: AGESVC1B_p1_054, 
wapp.20080515.a2048.0006 Scan: TOGS Calibration, Spare time at the end.
Conditionals based on LST were tested today. They seemed to work okay - the first scan would not have been reached in time and so was automatically skipped (it actually had to begin a couple of minutes before our time-slot started). Little interference again today.
16/05/2008 RM wapp.20080516.a2048.0000 Scan: TOGS Calibration, 
wapp.20080516.a2048.0001 Scan: AGESVC1A_p1_001, 
wapp.20080516.a2048.0002 Scan: AGESVC1B_p1_056, 
wapp.20080516.a2048.0003 Scan: AGESVC1B_p1_058, 
wapp.20080516.a2048.0004 Scan: AGESVC1B_p1_060, A burst of 'count doesn't match' warning on WAPP-4. Difference only 2 so probably no problem.
wapp.20080516.a2048.0005 Scan: AGESVC1B_p1_062, 
wapp.20080516.a2048.0006 Scan: AGESVC1B_[1_064, Funny RFI blob at ~1391 MHz for about 30s.
Smooth observing. Little RFI.
19/05/2008 RM wapp.20080519.a2048.0000 Scan: TOGS calibration, 
wapp.20080519.a2048.0001 Scan: AGESVC1A_p1_003, 
wapp.20080519.a2048.0002 Scan: AGESVC1B_p1_066, 
wapp.20080519.a2048.0003 Scan: AGESVC1B_p1_068, 
wapp.20080519.a2048.0004 Scan: AGESVC1B_p1_070, 
wapp.20080519.a2048.0005 Scan: AGESVC1B_p1_072, 
Smooth run.
22/05/2008 SS&WvD wapp.20080522.a2048.0000 Scan: TOGS calibration, 
wapp.20080522.a2048.0001 Scan: AGESVC1B_p1_074, 
wapp.20080522.a2048.0002 Scan: AGESVC1B_p1_076, lots of "counts don't match" warnings
wapp.20080522.a2048.0003 Scan: AGESVC1B_p1_078, 
wapp.20080522.a2048.0004 Scan: AGESVC1B_p1_080, 
wapp.20080522.a2048.0005 Scan: AGESVC1B_p2_041, 
wapp.20080522.a2048.0006 Scan: TOGS calibration, 
AGES haiku 22.05.08 spring stars flickering atoms coolly emitting: distant observing
23/05/2008 SS&WvD wapp.20080523.a2048.0000 Scan: TOGS calibration, 
wapp.20080523.a2048.0001 Scan: AGESVC1A_p1_007, 
wapp.20080523.a2048.0002 Scan: AGESVC1B_p2_043, 
wapp.20080523.a2048.0003 Scan: AGESVC1B_p2_045, 
wapp.20080523.a2048.0004 Scan: AGESVC1B_p2_047, 
wapp.20080523.a2048.0005 Scan: AGESVC1B_p2_049, 
wapp.20080523.a2048.0006 Scan: AGESVC1B_p2_051, 
AGES haiku 23.05.08 Wim's busy tonight no time for any haikus that makes me so sad
24/05/2008 RT wapp.20080524.a2048.0000 Scan: TOGS calibration, 
wapp.20080524.a2048.0001 Scan: AGESVC1A_p1_009, 
wapp.20080524.a2048.0002 Scan: AGESVC1B_p2_053, Got counts don't match error during calibration, but difference is small
wapp.20080524.a2048.0003 Scan: AGESVC1B_p2_055, 
wapp.20080524.a2048.0004 Scan: AGESVC1B_p2_057, 
wapp.20080524.a2048.0005 Scan: AGESVC1B_p2_059, Another counts don't match error during calibration, but difference is small. Then hundreds of the same error during the drift scan.
wapp.20080524.a2048.0006 Scan: AGESVC1B_p2_061, More of the same.
If we can have AGES haiku's then why not limericks ?
It's a survery for deep HI data,
From a telescope shaped like a crater,
It really takes AGES,
So it's done in small stages,
And has a fixed-temperature calibrator.
25/05/2008 RT wapp.20080525.a2048.0000 Scan: TOGS calibration, Lots of counts don't match errors, but difference is small
wapp.20080525.a2048.0001 Scan: AGESVC1A_p1_011, Burst of counts don't match errors, but again difference is small
wapp.20080525.a2048.0002 Scan: AGESVC1B_p2_063, 
wapp.20080525.a2048.0003 Scan: AGESVC1B_p2_065, 
wapp.20080525.a2048.0004 Scan: AGESVC1B_p2_067, 
wapp.20080525.a2048.0005 Scan: AGESVC1B_p2_069, 
wapp.20080525.a2048.0006 Scan: AGESVC1B_p2_071, 
wapp.20080525.a2048.0007 Scan: TOGS calibration, 
My attempt at a haiku :
Observing quite smooth
Not much RFI tonight
All beams are working.
26/05/2008 RT wapp.20080526.a2048.0000 Scan: TOGS calibration, 
wapp.20080526.a2048.0001 Scan: AGESVC1A_p1_013, 
wapp.20080526.a2048.0002 Scan: AGESVC1B_p2_073, 
wapp.20080526.a2048.0003 Scan: AGESVC1B_p2_075, 
wapp.20080526.a2048.0004 Scan: AGESVC1B_p2_077, 
wapp.20080526.a2048.0005 Scan: AGESVC1B_p2_079, 
wapp.20080526.a2048.0006 Scan: AGESVC1B_p2_081, 
wapp.20080526.a2048.0007 Scan: TOGS calibration, 
Observations fine Not many warnings at all Tea keeps me awake.
27/05/2008 SS&WvD wapp.20080527.a2048.0000 Scan: TOGS calibration, 
wapp.20080527.a2048.0001 Scan: AGESVC1A_p1_015, 
wapp.20080527.a2048.0002 Scan: AGESVC1B_p2_042, 
wapp.20080527.a2048.0003 Scan: AGESVC1B_p2_044, 
wapp.20080527.a2048.0004 Scan: AGESVC1B_p2_046, 
wapp.20080527.a2048.0005 Scan: AGESVC1B_p2_048, counts don't match errors throughout
wapp.20080527.a2048.0006 Scan: AGESVC1B_p2_050, errors continue--aborted and restart wapps
wapp.20080527.a2048.0007 Scan: AGESVC1B_p2_050, 
AGES haiku 27.05.08 starry night tonight no time for radio waves must install software
28/05/2008 SS&WvD wapp.20080528.a2048.0000 Scan: TOGS calibration, counts don't match errors - aborted, restart wapps
wapp.20080528.a2048.0001 Scan: TOGS calibration, counts don't match errors still
wapp.20080528.a2048.0002 Scan: AGESVC1A_p1_017, lots more errors
wapp.20080528.a2048.0003 Scan: AGESVC1B_p2_052, 
wapp.20080528.a2048.0004 Scan: AGESVC1B_p2_054, 
wapp.20080528.a2048.0005 Scan: AGESVC1B_p2_056, lots more errors
wapp.20080528.a2048.0006 Scan: AGESVC1B_p2_058, lots more errors
wapp.20080528.a2048.0007 Scan: AGESVC1B_p2_060, lots more errors
Lots of "counts don't match" errors. Norberto reports: "Wapp #4 chip12,13,15are acting up again." AGES haiku 28.05.08 Ginger beer drinking Alarms constantly sounding Chips misbehaving
29/05/2008 SS&WvD wapp.20080529.a2048.0000 Scan: TOGS calibration, 
wapp.20080529.a2048.0001 Scan: AGESVC1A_p1_019, 
wapp.20080529.a2048.0002 Scan: AGESVC1B_p2_062, counts don't match errors
wapp.20080529.a2048.0003 Scan: AGESVC1B_p2_064, 
wapp.20080529.a2048.0004 Scan: AGESVC1B_p2_066, 
wapp.20080529.a2048.0005 Scan: AGESVC1B_p2_068, 
wapp.20080529.a2048.0006 Scan: AGESVC1B_p2_070, 
AGES haiku 28.05.08 cajun spice smelling into Orchid dscending Lost season ending
30/05/2008 SS&WvD wapp.20080530.a2048.0000 Scan: TOGS calibration, 
wapp.20080530.a2048.0001 Scan: AGESVC1A_p1_021, 
wapp.20080530.a2048.0002 Scan: AGESVC1B_p2_072, lots of counts don't match errors
wapp.20080530.a2048.0003 Scan: AGESVC1B_p2_074, lots more
wapp.20080530.a2048.0004 Scan: AGESVC1B_p2_076, 
wapp.20080530.a2048.0005 Scan: AGESVC1B_p2_078, lots more
wapp.20080530.a2048.0006 Scan: AGESVC1B_p2_080, and more
wapp.20080530.a2048.0007 Scan: TOGS calibration, and more
AGES haiku 30.05.08 Zen rock gardening Manassas Stonewall standing AGES observing
31/05/2008 RT wapp.20080531.a2048.0000 Scan: TOGS calibration, Failed ! don't use
At start TO informed about problems with WAPP 2. Immediately got warnings about errors while sending VERBOSE, TIMEOUT 5 and PROJECT a2048 RT to WAPPCON2. Tried manually configuring the WAPPS but same errors. Tried restarting WAPPS, no luck. Waited until end of scheduled time but no-one was found to fix the problem.
01/06/2008 RT wapp.20080601.a2048.0000 Scan: AGESVC1A_p1_023, Due to initial problems, started several minutes late and aborted several minutes early to make the next scan on time.
wapp.20080601.a2048.0001 Scan: AGESVC1B_p1_041, 
wapp.20080601.a2048.0002 Scan: AGESVC1B_p1_043, Got some AGC datablock warnings but somehow I don't think it matters...
wapp.20080601.a2048.0003 Scan: AGESVC1B_p1_045, 
wapp.20080601.a2048.0004 Scan: AGESVC1B_p1_047, 
wapp.20080601.a2048.0004 Scan: AGESVC1B_p1_049, 
Informed by TO that WAPP2 still has problems. This time got a different set of still fatal errors that caused the script to abort. TO called Stephen Gibson. Manually changed WAPP configuration and disabled WAPP2. Data taken after that without any warnings, but only have beams 0A,1A,4A and 6B ! Probably should have gone to bed instead...
22/06/2008 wapp.20080622.a2048.0000 Scan: TOGS calibration, Started late due to typo in Had to abort to get to AGES observations on time
wapp.20080622.a2048.0001 Scan: AGES7448_p1_080, On source with 14s to spare
wapp.20080622.a2048.0002 Scan: AGES7448_p1_082, 
wapp.20080622.a2048.0003 Scan: AGES7448_p1_084, 
wapp.20080622.a2048.0004 Scan: AGES7448_p1_086, 
wapp.20080622.a2048.0005 Scan: TOGS calibration, 
A few things missed due to the last-minute nature of the observing - .conf files were not re-made for CIMA 3.0 so observing was using CIMA 2.3 and the was not updated, and was then updated with a typo, meaning that the TOGS calibration had to be aborted. TOGS calibration done successfully at the end of the night.
01/07/2008 RM wapp.20080701.a2048.0000 Scan: AGES7448_p1_088, 0B low again.
wapp.20080701.a2048.0001 Scan: AGES7448_p1_090, 
wapp.20080701.a2048.0002 Scan: AGES7448_p1_092, 
wapp.20080701.a2048.0003 Scan: AGES7448_p1_094, 
wapp.20080701.a2048.0004 Scan: AGES7448_p1_096, 
wapp.20080701.a2048.0005 Scan: TOGS Calibration, 
Using CIMA 3.0. Huge numbers of 'counts don't match' errors, without any significant difference. Remote observers just don't know what they're missing, not getting that beep every second!
04/07/2008 RA wapp.20080704.a2048.0000 Scan: TOGS, Tooooo many windows!!!! I need more screens!!
wapp.20080704.a2048.0001 Scan: AGES7448_p1_098, 
wapp.20080704.a2048.0002 Scan: AGES7448_p1_100, 
wapp.20080704.a2048.0003 Scan: AGES7448_p1_060, Telescope was not on source for first few seconds
wapp.20080704.a2048.0004 Scan: AGES7448_p1_062, 
wapp.20080704.a2048.0005 Scan: AGES7448_p1_064, Telescope was not on source for first few seconds
wapp.20080704.a2048.0006 Scan: AGES7448_p1_066, Telescope was not on source for first few seconds
RFI at 1339.95, 1350, 1367.25 Striping noticed in the time domain on beam 6B. Total power plots show a different pattern to the other beams, suggesting this is not from FAA radar. TO reports that the stage 3 has issues. No time for TOGS at end of run. Overran by a minute
05/07/2008 RA wapp.20080705.a2048.0000 Scan: TOGS CAL, 
wapp.20080705.a2048.0001 Scan: AGES7448_p1_68, 
wapp.20080705.a2048.0002 Scan: AGES7448_p1_70, 
wapp.20080705.a2048.0003 Scan: AGES7448_p1_72, 
wapp.20080705.a2048.0004 Scan: AGES7448_p1_74, 
wapp.20080705.a2048.0005 Scan: AGES7448_p1_76, 
wapp.20080705.a2048.0006 Scan: AGES7448_p1_78, 
wapp.20080705.a2048.0007 Scan: TOGS CAL, 
RFI: 1340, 1350, 1387.25 No problems with beam 6 today. Very strong continuum source noticed (off the scale).
06/07/2008 RT wapp.20080706.a2048.0000 Scan: AGES7448_p1_061, Hundreds of counts don't match errors but difference is small. Also warnings of WAPP channels with too little power.
wapp.20080706.a2048.0001 Scan: AGES7448_p1_063, First few seconds off-source. More warnings of too little power.
wapp.20080706.a2048.0002 Scan: AGES7448_p1_065, Hundreds of counts don't match errors, again difference is small. More too little power warnings.
wapp.20080706.a2048.0003 Scan: AGES7448_p1_067, Same warnings.
wapp.20080706.a2048.0004 Scan: AGES7448_p1_069, First two (!) seconds off source. Same warnings.
wapp.20080706.a2048.0005 Scan: AGES7448_p1_071, First few seconds off-source. Same warnings.
Home observing experiment. Missed initial TOGS as had problems with CIMA display initially, restarted and was fine.
Some ripple in beam 6B. Beam 0B seems to be at half-power.
Tried running command_galfacurpos but it failed. No time to find out why.
07/07/2008 RA wapp.20080707.a2048.0000 Scan: J223226+231111, on-off obs with ALFA. probably should have used radar blanker
wapp.20080707.a2048.0001 Scan: TOGS CAL, 
wapp.20080707.a2048.0002 Scan: AGES7448_p1_073, AGC-datablock warning at start.
wapp.20080707.a2048.0003 Scan: AGES7448_p1_075, first few seconds not on source
wapp.20080707.a2048.0004 Scan: AGES7448_p1_077, AGC-datablock warning at start.
wapp.20080707.a2048.0005 Scan: AGES7448_p1_079, duplicate AGC-datablock warning at start.
wapp.20080707.a2048.0006 Scan: AGES7448_p1_081, 
wapp.20080707.a2048.0007 Scan: AGES7448_p1_083, first few seconds not on source
wapp.20080707.a2048.0008 Scan: TOGS CAL, 
Started early, so squeezed in a standard on-off obs using ALFA. Beam 6B showing striping. Beam 0B at half power. Strong continuum source is causing "too much power" warnings. RFI: 1340, 1350, 1387.25
08/07/2008 RA wapp.20080708.a2048.0000 Scan: TOGS CAL, WAPP4 'counts don't match' warnings
wapp.20080708.a2048.0001 Scan: J223240+224548, Cheeky follow up obs. Forgot to apply radar blanking again. ZA close to 15 deg. Yesterday's followup may have only been an 'ON'.
wapp.20080708.a2048.0002 Scan: AGES7448_p1_085, Beam 0B at half power. WAPP4 'counts don't match' warnings
wapp.20080708.a2048.0003 Scan: AGES7448_p1_087, Beam 0B power levels back to normal.
wapp.20080708.a2048.0004 Scan: AGES7448_p1_089, No warning messages... is that a bad sign?
wapp.20080708.a2048.0005 Scan: AGES7448_p1_091, 
wapp.20080708.a2048.0006 Scan: AGES7448_p1_093, 
wapp.20080708.a2048.0007 Scan: AGES7448_p1_095, Not on source first few seconds. duplicate AGC datablock warnings
Lost internet connectivity 10s into first scan. TO reports no power failure, so someone must have kidnapped the internet. TO noted that command file still running. TO informed to keep an eye on things and shut down when observing file is complete. Meanwhile I'll try and reconnect.... reconnection after half an hour. Everything ticking along nicely. VNC is really rather useful you know. Strongest continuum source in the region is 4C +15.77, but this is only 330 mJy at 1.4 GHz. Could this be the strong source causing the power warnings? RFI at 1340, 1350, 1387.25 No time for TOGS at end.
15/07/2008 RM JD RT wapp.20080715.a2048.0000 Scan: J223354+243117, 7332 follow-up
wapp.20080715.a2048.0001 Scan: J223404+240213, 7332 follow-up
wapp.20080715.a2048.0002 Scan: AGES7448_p1_097, Warnings of too little power, counts don't match but difference is small
wapp.20080715.a2048.0003 Scan: AGES7448_p1_099, As above.
wapp.20080715.a2048.0004 Scan: AGES7448_p2_060, As above
wapp.20080715.a2048.0005 Scan: AGES7448_p2_064, Counts don't match but difference is small
wapp.20080715.a2048.0006 Scan: AGES7448_p2_066, Counts don't match but difference is small
wapp.20080715.a2048.0007 Scan: TOGS calibration, 
Beam 0B is down. No sign of rippling in 6B any more.
16/07/2008 JID wapp.20080716.a2048.0000 Scan: j223226+231111, 7332 follow up. Warning - Counts don't match on chip
wapp.20080716.a2048.0001 Scan: j223502+235235, 7332 follow up. Warning - Counts don't match on chip
wapp.20080716.a2048.0002 Scan: AGES7448_p2_068, AGES 7448. Warning - Counts don't match on chip
wapp.20080716.a2048.0003 Scan: AGES7448_p2_070, AGES 7448. Warning - Counts don't match on chip
wapp.20080716.a2048.0004 Scan: AGES7448_p2_072, AGES 7448. Warning - Counts don't match on chip
wapp.20080716.a2048.0005 Scan: AGES7448_p2_074, AGES 7448. Warning - Counts don't match on chip
wapp.20080716.a2048.0006 Scan: AGES7448_p2_076, AGES 7448. Warning - Counts don't match on chip
wapp.20080716.a2048.0007 Scan: AGES7448_p2_078, AGES 7448. Warning - Counts don't match on chip
wapp.20080716.a2048.0008 Scan: Cur_pos, TOGS cal.
17/07/2008 JID wapp..a2048.0000 Scan: ages7448_p2_80, No problems
wapp..a2048.0001 Scan: ages7448_p2_82, No problems
wapp..a2048.0002 Scan: ages7448_p2_84, No problems
wapp..a2048.0003 Scan: ages7448_p2_86, No problems
wapp..a2048.0004 Scan: ages7448_p2_88, No problems
wapp..a2048.0005 Scan: ages7448_p2_90, No problems
wapp..a2048.0006 Scan: TOGS calibration, No problems
18/07/2008 RA wapp.20080718.a2048.0000 Scan: 223516+244315, 
wapp.20080718.a2048.0001 Scan: AGES7448_p2_092, 
wapp.20080718.a2048.0002 Scan: AGES7448_p2_094, 
wapp.20080718.a2048.0003 Scan: AGES7448_p2_096, 
wapp.20080718.a2048.0004 Scan: AGES7448_p2_098, 
wapp.20080718.a2048.0005 Scan: AGES7448_p2_100, Beam 0B power at below 0.1
wapp.20080718.a2048.0006 Scan: AGES7448_p2_061, Beam 0B power back up to 0.4
wapp.20080718.a2048.0007 Scan: TOGS cal, Beam 0B power fluctuating below 0.4 and above 4
Beam 0B amplifier really needs attention.
19/07/2008 RA wapp.20080719.a2048.0000 Scan: J223544+235401, 
wapp.20080719.a2048.0001 Scan: J223604+242406, 
wapp.20080719.a2048.0002 Scan: AGES7448_p2_063, ALFA rotation command failed. TO fixed. Restarted
wapp.20080719.a2048.0003 Scan: AGES7448_p2_065, Observing not on source for first few seconds - still waiting for ALFA to rotate.
wapp.20080719.a2048.0004 Scan: AGES7448_p2_067, "RA has already passed" warnings. Not onsource for first 12s
wapp.20080719.a2048.0005 Scan: AGES7448_p2_069, 
wapp.20080719.a2048.0006 Scan: AGES7448_p2_071, 
wapp.20080719.a2048.0007 Scan: TOGS cal, 
Final observing command AGES7448_p2_073 was skipped. Presumably the slew time was too great so the IF statement failed, but I can't verify that.
20/07/2008 RA wapp.20080720.a2048.0000 Scan: J223210+234223, 
wapp.20080720.a2048.0001 Scan: TOGS cal, 
wapp.20080720.a2048.0002 Scan: AGES7448_p2_073, Beam 0B power < 0.3
wapp.20080720.a2048.0003 Scan: AGES7448_p2_075, Beam 0B power < 0.3. All WAPPs failed 03:06 AST. Only missing 1 minute
wapp.20080720.a2048.0004 Scan: AGES7448_p2_081, 
wapp.20080720.a2048.0005 Scan: AGES7448_p2_083, 
All WAPPs failed at 03:06. TO reports no power failure but Internet connection was lost. Reconnected after half an hour and restarted the WAPPs. 2 scans lost. Problems with Beam 0B again.
21/07/2008 RT wapp.20080721.a2048.0000 Scan: J223226+231111, N7332 follow-up
wapp.20080721.a2048.0001 Scan: J223502+242142, N7332 follow-up. A few warnings of channels with too little power during off scan.
wapp.20080721.a2048.0002 Scan: AGES7448_p2_085, Intermittant warnings of too little power. Beam 0B at half power for first drift scan and showed (most of the time) hideous striping in waterfall plot.
wapp.20080721.a2048.0003 Scan: AGES7448_p2_087, First 5 seconds off-source. Same warnings.
wapp.20080721.a2048.0004 Scan: AGES7448_p2_089, Same warnings.
wapp.20080721.a2048.0005 Scan: AGES7448_p2_091, Beam 0B power above 4. Warnings of channels with too little and then too much power, probably beam 0B issues.
wapp.20080721.a2048.0006 Scan: AGES7448_p2_093, Beam 0B back to normal. Eerie lack of power warnings...
wapp.20080721.a2048.0007 Scan: AGES7448_p2_095, First 2 seconds off-source. Beam 0B normal until last 6 minutes when suddenly power dropped below 0.1.
wapp.20080721.a2048.0008 Scan: TOGS calibration, The haphazard beam 0B jumps back to 0.5.
All beams OK at start. TO reports TOGS not working initially but running by start of second follow-up. Brief loss of internet connection at ~2:30, observations unaffected.
22/07/2008 RT wapp.20080722.a2048.0000 Scan: AGES7448_p2_097, 
wapp.20080722.a2048.0001 Scan: AGES7448_p2_099, First 3 seconds off-source.
wapp.20080722.a2048.0002 Scan: AGES7448_p3_060, First 9 seconds off-source.
wapp.20080722.a2048.0003 Scan: AGES7448_p3_062, 
wapp.20080722.a2048.0004 Scan: AGES7448_p3_064, 
wapp.20080722.a2048.0005 Scan: AGES7448_p3_066, First 7 seconds off-source.
wapp.20080722.a2048.0006 Scan: TOGS calibration, 
No time for follow-up due to ALFA uncovering time. Everything seems to be working, even beam 0B.
23/07/2008 RT wapp.20080723.a2048.0000 Scan: J223957+233942, 7332 follow-up. Warnings about being close to the zenith angle limit of 19.69 degrees.
wapp.20080723.a2048.0001 Scan: J224025+243927, 7332 follow-up.
wapp.20080723.a2048.0002 Scan: AGES7448_p2_077, A few warnings of wapp channels with too much power.
wapp.20080723.a2048.0003 Scan: AGES7448_p2_079, First 5 seconds off-source.
wapp.20080723.a2048.0004 Scan: AGES7448_p3_068, Warnings of channels with too little power; beam 0B is around 0.1
wapp.20080723.a2048.0005 Scan: AGES7448_p3_070, Beam 0B back to normal.
wapp.20080723.a2048.0006 Scan: AGES7448_p3_072, Beam 0B at half power. Warnings of channels with too much and too little power.
wapp.20080723.a2048.0007 Scan: AGES7448_p3_074, Warnings of channels with too little power, beam 0B back to 0.1.
No time for TOGS, probably should do at the start instead of 2 follow-ups.
24/07/2008 JID wapp.20080724.a2048.0000 Scan: J223237+231205, Follow up observation. WAPPS with too little power
wapp.20080724.a2048.0001 Scan: TOGS, Togs calibration
wapp.20080724.a2048.0002 Scan: AGES7448_p3_076, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
wapp.20080724.a2048.0003 Scan: AGES7448_p3_078, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
wapp.20080724.a2048.0004 Scan: AGES7448_p3_080, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
wapp.20080724.a2048.0005 Scan: AGES7448_p3_082, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
wapp.20080724.a2048.0006 Scan: AGES7448_p3_084, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
wapp.20080724.a2048.0007 Scan: AGES7448_p3_086, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
Worried that the spectra in some beams did not look right. I did not see a spectra displayed in beam 0 all run.
25/07/2008 JID wapp.20080725.a2048.0000 Scan: J223237+231205, Follow up observation. WAPPS with too little power. Just realised that I did this one yesterday, it was not marked off on the list
wapp.20080725.a2048.0001 Scan: AGES7448_p3_090, WAPPS with too little power
wapp.20080725.a2048.0002 Scan: AGES7448_p3_092, WAPPS with too little power
wapp.20080725.a2048.0003 Scan: AGES7448_p3_096, Skipped the 094 scan
wapp.20080725.a2048.0004 Scan: AGES7448_p3_098, WAPPS with too little power - I do not see the spectrum in some beams particularly beam 0
wapp.20080725.a2048.0005 Scan: , 
wapp.20080725.a2048.0006 Scan: , 
wapp.20080725.a2048.0007 Scan: , 
wapp.20080725.a2048.0008 Scan: , 
Only beams 1 and 6 are showing spectra in the data view window! I had a problem with TOGS, said failed. Thought I would go to AGES waited ages and then this failed (ALFA rotation timed out). My window also hung so phoned operator and he said the ALFA rotation motor was switched off from the previous obs - he switched it back on again!! Started AGES late and so missed the first scan. Hope I am OK for the second. Try and do TOGS at the end. Beam 2 sort of came back half-way through the run. For some reason it skipped the p3_094 scan - it said 'skipping line 'FIXEDDRIFT.....' Did it get there too late? Then waited 19min for next drift.
26/07/2008 LC wapp.20080726.a2048.0000 Scan: J223317+244538, Standing Waves and strong absorption @1373 MHz. Might be there
wapp.20080726.a2048.0001 Scan: J224025+243927, Radar Blanker ON.
wapp.20080726.a2048.0002 Scan: J224025+243927, Radar Blanker ON. Very close to the FAA radar, but probably there
wapp.20080726.a2048.0003 Scan: J223237+231205, Radar Blanker ON. Detected!
wapp.20080726.a2048.0004 Scan: J223415+233059, Radar Blanker ON.
wapp.20080726.a2048.0005 Scan: J223415+233059, Radar Blanker ON. Detected. More clear in this pair than in the previous one.
wapp.20080726.a2048.0006 Scan: J223111+234146, Radar Blanker ON. Standing Waves and strong absorptions. Probably better not to use it.
wapp.20080726.a2048.0007 Scan: J223111+234146, Radar Blanker ON. Detected
wapp.20080726.a2048.0008 Scan: J224125+232226, Radar Blanker ON. Very Bad baseline but strong source where expected! Did we really need follow-up for this? N.B. By mistake in this file is also present a calibration scan.
wapp.20080726.a2048.0009 Scan: B0026+346, Calibrator. Radar Blanker OFF
ALFA down, so time used for follow-up with L-wide.
First time I use WAPPs with L-wide, so I had to figure out how to look at the data on-line since 'cormonall' seems not to work with WAPPs.
Almost all sources near the FAA radar, so for great part of the run I decided to use the Radar Blanker, which seems to have worked properly.
Baseline changed quite a lot during the run (showing sometimes very weird features), but overall the vast majority of the data are usable.
27/07/2008 LC wapp.20080727.a2048.0000 Scan: AGES7448_p3_100, GPS @1381MHz between UT ~06:12-06:14. Warning: AGC duplicate datablock
wapp.20080727.a2048.0001 Scan: AGES7448_p3_061, First 11 seconds NOT on source. Warning: extrapolating/interpolating AGC data beween 9611-9613
wapp.20080727.a2048.0002 Scan: AGES7448_p3_063, First 6 seconds NOT on source. Warning: extrapolating/interpolating AGC data beween 10510-10512
wapp.20080727.a2048.0003 Scan: AGES7448_p3_065, Warning: extrapolating/interpolating AGC data beween 11409-11410
wapp.20080727.a2048.0004 Scan: AGES7448_p3_067, Warning: extrapolating/interpolating AGC data beween 13207-13209
wapp.20080727.a2048.0005 Scan: AGES7448_p3_069, First 9 seconds NOT on source.
wapp.20080727.a2048.0006 Scan: TOGS calibration, 
ALFA is back and all the seven beams appear to work fine
. Smooth run. Hundreds of warning "counts do not match" (almost 1 every sec) always associated with WAPP=4. Difference always 2.
. FAA Radar @1350Mhz weak or totally absent.
28/07/2008 LC wapp.20080728.a2048.0000 Scan: AGES7448_p3_071, GPS @1381MHz between UT~5:58-5:59.
wapp.20080728.a2048.0001 Scan: AGES7448_p3_073, First 9 seconds NOT on source.
wapp.20080728.a2048.0002 Scan: AGES7448_p3_075, Warning extrapolating/interpolating AGC-data between 10414-10416
wapp.20080728.a2048.0003 Scan: AGES7448_p3_077, Warning extrapolating/interpolating AGC-data between 11313-11315 and between 12212-12214
wapp.20080728.a2048.0004 Scan: AGES7448_p3_079, Warning extrapolating/interpolating AGC-data between 11311-13113
wapp.20080728.a2048.0005 Scan: AGES7448_p3_081, First 8 seconds NOT on source.
Warning extrapolating/interpolating AGC-data between 14010-14012
wapp.20080728.a2048.0006 Scan: TOGS calibration, 
Smooth run. All beams ok.
For all scans: "Warning: WAPP with too much power". This is always associated with a VERY strong continuum source, likely 3C454.3 (QSO with F~10 Jy).
29/07/2008 RA wapp.20080729.a2048.0000 Scan: unusable, 
wapp.20080729.a2048.0001 Scan: AGES7448_p3_83, 
wapp.20080729.a2048.0002 Scan: AGES7448_p3_85, 
wapp.20080729.a2048.0003 Scan: AGES7448_p3_87, 
wapp.20080729.a2048.0004 Scan: AGES7448_p3_89, 
wapp.20080729.a2048.0005 Scan: TOGS calibration, 
Problems making script this morning. First scan lost due to unprepared script. Second attempt resulted in one scan from NGC 3193. This is not part of the 3193 field and isn't usable. Third time lucky!
30/07/2008 RA wapp.20080730.a2048.0000 Scan: AGES7448_p3_088, 
wapp.20080730.a2048.0001 Scan: AGES7448_p3_091, 
wapp.20080730.a2048.0002 Scan: AGES7448_p3_093, First 12s not on source
wapp.20080730.a2048.0003 Scan: AGES7448_p3_097, 
wapp.20080730.a2048.0004 Scan: TOGS calibration, 
AGES7448_p3_095 skipped automatically by script. Otherwise a quiet night. ZA > 15 after last scan was performed due to scheduling.
09/08/2008 RM wapp.20080809.a2048.0000 Scan: J223226+231111, LBW: RFI@1340 - very close to centre!
wapp.20080809.a2048.0001 Scan: TOGS calibration, 
wapp.20080809.a2048.0002 Scan: TOGS calibration, 
wapp.20080809.a2048.0003 Scan: AGES7448_p2_062, 
wapp.20080809.a2048.0004 Scan: AGES7448_p3_076, 
wapp.20080809.a2048.0005 Scan: AGES7448_p3_078, 
wapp.20080809.a2048.0006 Scan: AGES7448_p3_080, 
wapp.20080809.a2048.0007 Scan: AGES7448_p3_082, 
wapp.20080809.a2048.0008 Scan: AGES7448_p3_084, 
10/08/2008 RM wapp.20080810.a2048.0000 Scan: J223502+224142, LBW.
wapp.20080810.a2048.0001 Scan: TOGS calibration, Aborted - forgot to start GALSPECT!
wapp.20080810.a2048.0002 Scan: TOGS calibration, 
wapp.20080810.a2048.0003 Scan: AGES7448_p3_086, Large (>2000) chip-count errors. Data possibly corrupt for first 1m20s. More (same size) later in the scan for 50s. Data looks okay on quick-look.
wapp.20080810.a2048.0004 Scan: AGES7448_p3_090, 
wapp.20080810.a2048.0005 Scan: AGES7448_p3_092, 
wapp.20080810.a2048.0006 Scan: AGES7448_p3_094, 
wapp.20080810.a2048.0007 Scan: AGES7448_p3_095, 
wapp.20080810.a2048.0008 Scan: AGES7448_p3_096, 
wapp.20080810.a2048.0009 Scan: AGES33PP_p1_080, Chip count errors again. No data shown for a period on quicklook.
wapp.20080810.a2048.0010 Scan: AGES33PP_p1_082, More chip count errors
wapp.20080810.a2048.0011 Scan: AGES33PP_p1_084, More chip count errors
wapp.20080810.a2048.0012 Scan: AGES33PP_p1_086, More chip count errors
wapp.20080810.a2048.0013 Scan: AGES33PP_p1_088, More chiop count errors
Need to check if chip count errors of ~2000 are acceptable or not. 33PP_p1_080 is probably corrupt (data disappeared for a bit!)
11/08/2008 RM wapp.20080811.a2048.0000 Scan: J223314+241428, LBW.
wapp.20080811.a2048.0001 Scan: TOGS calibration, 
wapp.20080811.a2048.0002 Scan: AGES7448_p3_098, 
wapp.20080811.a2048.0003 Scan: AGES7448_p3_099, 
wapp.20080811.a2048.0004 Scan: AGES7448_p3_100, 
wapp.20080811.a2048.0005 Scan: AGES7448_p1_101, Chip count errors (~2000) from 11 minutes in.
wapp.20080811.a2048.0006 Scan: AGES7558_p1_103, Continuing chip count errors
wapp.20080811.a2048.0007 Scan: AGES33PP_p1_090, Chip count errors for the first four seconds. M33 visible on quicklook.
wapp.20080811.a2048.0008 Scan: AGES33PP_p1_092, 
wapp.20080811.a2048.0009 Scan: AGES33PP_p1_094, 
wapp.20080811.a2048.0010 Scan: AGES33PP_p1_096, 
wapp.20080811.a2048.0011 Scan: AGES33PP_p1_098, 
12/08/2008 wapp.20080812.a2048.0013 Scan: J223823+245208, LBW. File data 080811
wapp.20080812.a2048.0000 Scan: TOGS calibration, Bad
wapp.20080812.a2048.0001 Scan: TOGS calibration, 
wapp.20080812.a2048.0002 Scan: AGES7448_p1_105, 
wapp.20080812.a2048.0003 Scan: AGES7448_p1_107, 
wapp.20080812.a2048.0004 Scan: AGES7448_p1_107, Duplicate! Problems with azimuth drive.
wapp.20080812.a2048.0005 Scan: AGES7448_p1_109, 
wapp.20080812.a2048.0006 Scan: AGES7448_p1_111, 
wapp.20080812.a2048.0007 Scan: AGES7448_p1_113, 
wapp.20080812.a2048.0008 Scan: AGES33PP_p1_110, Chip count errors (~2000) for first 8 seconds.
wapp.20080812.a2048.0009 Scan: AGES33PP_p1_112, 
wapp.20080812.a2048.0010 Scan: AGES33PP_p1_114, 
wapp.20080812.a2048.0011 Scan: AGES33PP_p1_116, 
wapp.20080812.a2048.0012 Scan: AGES33PP_p1_118, 
13/08/2008 wapp.20080813.a2048.0013 Scan: J2223142+244511, LBW. File dated 080812
wapp.20080813.a2048.0000 Scan: J223231+231611, LBW
wapp.20080813.a2048.0001 Scan: J223502+242142, LBW
wapp.20080813.a2048.0002 Scan: J223604+242406, LBW. CIMA reads velocity as 12929 instead of 16067. Source still visible in wide-band spectrum.
wapp.20080813.a2048.0003 Scan: J223714+233004, LBW
wapp.20080813.a2048.0004 Scan: J223745+225304, LBW
wapp.20080813.a2048.0005 Scan: J223714+233004, LBW. Second opinion.
wapp.20080813.a2048.0006 Scan: TOGS calibration, 
wapp.20080813.a2048.0007 Scan: AGES7448_p1_115, 
wapp.20080813.a2048.0008 Scan: AGES7448_p1_117, 
wapp.20080813.a2048.0009 Scan: AGES7448_p1_119, 
wapp.20080813.a2048.0010 Scan: AGES33PP_p1_120, Chip count errors (~2000) for the first 32s and last 11s.
wapp.20080813.a2048.0011 Scan: AGES33PP_p1_081, 
wapp.20080813.a2048.0012 Scan: AGES33PP_p1_083, 
wapp.20080813.a2048.0013 Scan: AGES33PP_p1_085, Chip count errors for the last 2 minutes.
Last chance to finish the f/u taken. Now just to write the paper...
23/09/2008 EM wapp.20080923.a2048.0000 Scan: J223502+235233, single pixel (with LBW); lots of "counts don't match" warnings. ERROR: failed calibration!!!
wapp.20080923.a2048.0001 Scan: J223628+245307, single pixel (with LBW); lots of "counts don't match" warnings.
wapp.20080923.a2048.0002 Scan: AGES4778_p1_121, WAPP failure. Scan failed!!
wapp.20080923.a2048.0002 Scan: AGES4778_p1_123, 
wapp.20080923.a2048.0003 Scan: AGES4778_p1_125, 
wapp.20080923.a2048.0004 Scan: AGES4778_p1_127, 
wapp.20080924.a2048.0000 Scan: TOGS calibration, 
At the start of FITS 0002 CIMA reported "failed to get response from the CIMA frontend when checking for 'fixed azimuth drift map'.
Scan AGES4778_p1_121 failed.
31/10/2008 EM wapp.20081031.a2048.0000 Scan: TOGS calibration, 
wapp.20081031.a2048.0001 Scan: AGES74478_p1_129, 
wapp.20081031.a2048.0002 Scan: AGES74478_p1_131, 
wapp.20081031.a2048.0003 Scan: AGES74478_p1_133, 
wapp.20081031.a2048.0004 Scan: AGES74478_p1_135, 
First scan: AGES74478_p1_121 was missed. The .cmd file didn't have the entry to call the correct source catalog. Mikael edited the file and we are back on track with the 2nd scan (AGES74478_p1_129).
Beam 6B is not well
05/11/2008 MS RT wapp.20081105.a2048.0000 Scan: TOGS calibration, 
wapp.20081105.a2048.0001 Scan: AGES7448_p1_139, 
wapp.20081105.a2048.0002 Scan: AGES7448_p1_141, 
wapp.20081105.a2048.0003 Scan: AGES7448_p1_143, 
Not enough time for first scan. Beam 6B is down. Lots of warnings of WAPP channels with too little power.
06/11/2008 MS wapp.20081106.a2048.0000 Scan: AGES7448_p1_137, 
wapp.20081106.a2048.0001 Scan: AGES7448_p1_102, 
wapp.20081106.a2048.0002 Scan: AGES7448_p1_104, 
wapp.20081106.a2048.0003 Scan: AGES7448_p1_106, 
wapp.20081106.a2048.0004 Scan: TOGS calibration, 
Missed initial TOGS due to connecting problems but fitted one in at end. Beam 6B is down. Lots of warnings of WAPP channels with too little power.
07/11/2008 RT wapp.20081107.a2048.0000 Scan: TOGS calibration, 
wapp.20081107.a2048.0001 Scan: AGES7448_p1_110, 
wapp.20081107.a2048.0002 Scan: AGES7448_p1_112, 
wapp.20081107.a2048.0003 Scan: AGES7448_p1_112, First 13 seconds off-source
Missed the first scan due to TOGS. Beam 6B is back up.
08/11/2008 MS wapp.20081108.a2048.0000 Scan: AGES7448_p1_108, 
wapp.20081108.a2048.0001 Scan: AGES7448_p1_116, 
wapp.20081108.a2048.0002 Scan: AGES7448_p1_118, First 14 seconds NOT on source
wapp.20081108.a2048.0003 Scan: TOGS callibration, 
Operator said TOGS run was already in progress when I logged in. The first scan had to wait 27 minutes before initialising, however think everything got done.
09/11/2008 SS wapp.20081109.a2048.0000 Scan: AGES7448_p1_122, Not quite enough to slew to first source in file
wapp.20081109.a2048.0001 Scan: AGES7448_p1_124, 
wapp.20081109.a2048.0002 Scan: AGES7448_p1_126, 
wapp.20081109.a2048.0003 Scan: TOGS, 
11/11/2008 RT wapp.20081111.a2048.0000 Scan: TOGS calibration, 
wapp.20081111.a2048.0001 Scan: AGES7448_p1_120, 
wapp.20081111.a2048.0002 Scan: AGES7448_p1_128, 
wapp.20081111.a2048.0003 Scan: AGES7448_p1_130, Warnings of wapp channels with too little power. Power on beams 5B and 6B momentarily dropped to about 0.5, then went back to normal.
wapp.20081111.a2048.0004 Scan: AGES7448_p1_132, First 12 seconds off-source.
wapp.20081111.a2048.0005 Scan: TOGS calibration, 
13/11/2008 KLO wapp.20081113.a2048.0000 Scan: TOGS Callibration, 
wapp.20081113.a2048.0001 Scan: AGES7448_p1_138, Counts don't match but difference is small.
wapp.20081113.a2048.0002 Scan: AGES7448_p2_101, Counts don't match but difference is small.
wapp.20081113.a2048.0003 Scan: AGES7448_p2_103, 
wapp.20081113.a2048.0004 Scan: AGES7448_p2_105, 
wapp.20081113.a2048.0005 Scan: AGES33PP_p102, Counts don't match but difference is small.
14/11/2008 JID wapp.20081114.a2048.0000 Scan: AGES7448_p1_136, 
wapp.20081114.a2048.0001 Scan: AGES7448_p1_140, 
wapp.20081114.a2048.0002 Scan: AGES7448_p2_107, First 14 seconds not on source.
wapp.20081114.a2048.0003 Scan: AGES7448_p2_109, 
wapp.20081114.a2048.0004 Scan: 7448_p2_111, 
wapp.20081114.a2048.0005 Scan: 7448_p2_113, First 8 seconds NOT on source.
wapp.20081114.a2048.0006 Scan: AGES33pp_p1_100, 
15/11/2008 JID wapp.20081115.a2048.0000 Scan: 7448_p2_115, 
wapp.20081115.a2048.0001 Scan: 7448_p2_117, 
wapp.20081115.a2048.0002 Scan: 7448_p2_119, 
wapp.20081115.a2048.0003 Scan: 7448_p2_121, 
wapp.20081115.a2048.0004 Scan: 7448_p2_123, 
wapp.20081115.a2048.0005 Scan: 7448_p2_125, 
wapp.20081115.a2048.0006 Scan: ages33pp_p1_102, 
All seemed to go OK.
16/11/2008 SS wapp.20081116.a2048.0000 Scan: TOGS, 
wapp.20081116.a2048.0001 Scan: AGES7448_p1_134, 
wapp.20081116.a2048.0002 Scan: AGES7448_p2_127, 
wapp.20081116.a2048.0003 Scan: AGES7448_p2_129, 
wapp.20081116.a2048.0004 Scan: AGES7448_p2_131, 
wapp.20081116.a2048.0005 Scan: AGES7448_p2_133, 
wapp.20081116.a2048.0006 Scan: AGES7448_p2_135, 
wapp.20081116.a2048.0007 Scan: AGES33PP_p1_104, 
very smoooooth
17/11/2008 KLO wapp.20081117.a2048.0 Scan: TOGS Calibration, 
wapp.20081117.a2048.0001 Scan: AGES7448_p2_139, may be garbage
wapp.20081117.a2048.0002 Scan: AGES7448_p2_108, 
wapp.20081117.a2048.0003 Scan: AGES7448_p2_110, 
wapp.20081117.a2048.0004 Scan: AGES7448_p2_106, 
skipped p2_137;
Observing started but the vncserver froze - i have no idea what is going on. The telescope operator phone was busy, the guard did not know the other number to the control room. After awhile I tracked down the correct number and finally reached the operator. Dataview computer is frozen.... Phil put in a new ethernet card and it all works again. Got restarted around 7pm. I have no idea if the TOGS stuff worked after all the problems.
18/11/2008 LC wapp.20081118.a2048.0000 Scan: TOGS calibration, 
wapp.20081118.a2048.0001 Scan: AGES7448_p2_137, 
wapp.20081118.a2048.0002 Scan: AGES7448_p2_139, 
First 3 seconds NOT on source.
GPS @1381MHz from UT~22:46:50 to 22:47:30
wapp.20081118.a2048.0003 Scan: AGES7448_p2_102, 
First 2 seconds NOT on source.
Warning extrapolating pnt-data over 3 seconds time gap.
wapp.20081118.a2048.0004 Scan: AGES7448_p2_104, 
First 19 seconds NOT on source.
Warning extrapolating pnt-data over 2 seconds time gap.
wapp.20081118.a2048.0005 Scan: AGES7448_p2_106, 
First 12 seconds NOT on source.
Warning extrapolating pnt-data over 2 seconds time gap.
wapp.20081118.a2048.0006 Scan: AGES7448_p2_112, 
First 12 seconds NOT on source.
wapp.20081118.a2048.0007 Scan: AGES7448_p2_114, 
First 12 seconds NOT on source.
Warning extrapolating pnt-data over 2 seconds time gap.
wapp.20081118.a2048.0008 Scan: AGES33PP_p1_108, 
GPS @1381MHz from UT~01:18:00 to 01:19:30
Smooth run.

Got new type of warning for most of the scans:"Warning extrapolating pnt-data over 2 seconds time gap."

Noticed that the beam's intensity sometimes goes down to zero for just 1 sec and then turns back to normal. Contacted TO+Mikeal who said that if CIMA does not give warnings it is probably only a network problem.
19/11/2008 LC wapp.20081119.a2048.0000 Scan: AGES7448_p2_116, 
wapp.20081119.a2048.0001 Scan: AGES7448_p2_118, First 9 seconds NOT on source.
wapp.20081119.a2048.0002 Scan: AGES7448_p2_120, 
wapp.20081119.a2048.0003 Scan: AGES7448_p2_122, First 17 seconds NOT on source.
wapp.20081119.a2048.0004 Scan: AGES7448_p2_124, First 12 seconds NOT on source.
wapp.20081119.a2048.0005 Scan: AGES7448_p2_126, First 12 seconds NOT on source.
wapp.20081119.a2048.0006 Scan: AGES7448_p2_128, First 12 seconds NOT on source.
wapp.20081119.a2048.0007 Scan: AGES33PP_p1_087, 
wapp.20081119.a2048.0008 Scan: TOGS calibration, 
Smooth run. Everything ok!
20/11/2008 RA wapp.20081120.a2048.0000 Scan: AGES7448_p2_132, 
wapp.20081120.a2048.0001 Scan: AGES7448_p2_134, 
wapp.20081120.a2048.0002 Scan: AGES7448_p2_136, 
wapp.20081120.a2048.0003 Scan: AGES7448_p2_138, 
wapp.20081120.a2048.0004 Scan: AGES7448_p2_140, 
wapp.20081120.a2048.0005 Scan: TOGS calibration, 
Missed first scan due to being logged into observer not observer2 and command file was incomplete. TOGS was missed I'll see if I can do it at the end of the run... ...there was time for TOGS.
21/11/2008 JID wapp.20081121.a2048.e.g. (0001) Scan: scan name, Any Comments?
wapp.20081121.a2048.0001 Scan: 7448_p3_101, 
wapp.20081121.a2048.0002 Scan: 7448_p3_103, 
wapp.20081121.a2048.0003 Scan: 7448_p3_105, 
wapp.20081121.a2048.0004 Scan: 7448_p3_107, 
wapp.20081121.a2048.0005 Scan: 7448_p3_109, 
wapp.20081121.a2048.0006 Scan: 7448_p3_111, 
No problems
22/11/2008 RA wapp.20081122.a2048.0000 Scan: TOGS calibration, 
wapp.20081122.a2048.0001 Scan: AGES7448_p3_115, 
wapp.20081122.a2048.0002 Scan: AGES7448_p3_117, 
wapp.20081122.a2048.0003 Scan: AGES7448_p3_119, 
wapp.20081122.a2048.0004 Scan: AGES7448_p3_121, 
wapp.20081122.a2048.0005 Scan: AGES7448_p3_123, 
wapp.20081122.a2048.0006 Scan: AGES33PP_p1_089, 
wapp.20081122.a2048.0007 Scan: TOGS calibration, 
First scan missed by 3 minutes - not enough time to accommodate slew time and TOGS cal. We're getting 'observing when not on source' messages every scan. It's only a beam's width of sky, but I it bet scares the willies out of new observers. Any chance we can sort them out?
23/11/2008 RA wapp.20081123.a2048.0000 Scan: TOGS calibration, 
wapp.20081123.a2048.0001 Scan: AGES7448_p3_113, 
wapp.20081123.a2048.0002 Scan: AGES7448_p3_125, 
wapp.20081123.a2048.0003 Scan: AGES7448_p3_127, 
wapp.20081123.a2048.0004 Scan: AGES7448_p3_129, 
wapp.20081123.a2048.0005 Scan: AGES7448_p3_131, 
wapp.20081123.a2048.0006 Scan: AGES7448_p3_133, 
wapp.20081123.a2048.0007 Scan: AGES33PP_p1_091, 
wapp.20081123.a2048.0008 Scan: TOGS calibration, 
Power on Beam 6B low again.
01/12/2008 MS wapp.20081201.a2048.0000 Scan: TOGS callibration, 
wapp.20081201.a2048.0001 Scan: AGES7448_p3_135, 
wapp.20081201.a2048.0002 Scan: AGES7448_p3_137, 4 seconds NOT on source
wapp.20081201.a2048.0003 Scan: AGES7448_p3_139, 
wapp.20081201.a2048.0004 Scan: AGES7448_p3_102, 
wapp.20081201.a2048.0005 Scan: AGES7448_p3_104, 
wapp.20081201.a2048.0006 Scan: AGES7448_p3_106, 5 seconds NOT on source
wapp.20081201.a2048.0007 Scan: AGES33PP_p3_106, 
Good run, no problems.
MS wapp.20081202.a2048.0000 Scan: AGES3193_p1_009, 
wapp.20081202.a2048.0001 Scan: AGES3193_p2_043, 
Good run, starting two runs in one day (for a couple weeks). Observation files are labelled a and b, wapp data files should continue in order but CIMA log files will be renamed (with a and b) and the website adjusted manually.
MS wapp.20081202.a2048.0002 Scan: TOGS Callibration, 
wapp.20081202.a2048.0003 Scan: AGES7448_p3_108, 
wapp.20081202.a2048.0004 Scan: AGES7448_p3_110, 4 seconds NOT on source
wapp.20081202.a2048.0005 Scan: AGES7448_p3_112, 
wapp.20081202.a2048.0006 Scan: AGES7448_p3_116, Strong spike at 1380 MHz appeared for a few seconds
wapp.20081202.a2048.0007 Scan: AGES33PP_p1_093, 
Missed one scan due to abnormally long slew time. Radar spike at 1340 MHz.
MS wapp.20081203.a2048.0000 Scan: AGES3193_p2_045, 
wapp.20081203.a2048.0001 Scan: AGES3193_p2_047, 
wapp.20081203.a2048.0002 Scan: AGES3193_p2_049, 
wapp.20081203.a2048.0003 Scan: AGES3193_p2_051, 
wapp.20081203.a2048.0004 Scan: AGES3193_p2_053, 
wapp.20081203.a2048.0005 Scan: Togs Callibration, 
Radar spike at 1340 MHz in most scans.
MS wapp.20081203.a2048.0006 Scan: TOGS calibration, 
wapp.20081203.a2048.0007 Scan: AGES7448_p3_118, 
wapp.20081203.a2048.0008 Scan: AGES7448_p3_120, 
wapp.20081203.a2048.0009 Scan: AGES7448_p3_122, 
wapp.20081203.a2048.0010 Scan: AGES7448_p3_124, 1 second NOT on source
wapp.20081203.a2048.0011 Scan: TOGS calibration, 
wapp.20081203.a2048.0012 Scan: AGES33PP_p1_095, Only way to fit scan in schedule was to use ZA 16.5
1340 MHz Radar Present on a few scans, realised half way through session that finish at 20:15 instead of 20:30. Created an extra command file ('c' but same Cima log 'b'). However only way to fit 33PP scan due to schedule is to use ZA 16.53.
MS wapp.20081204.a2048.0000 Scan: TOGS Calibration, 
wapp.20081204.a2048.0001 Scan: AGES3193_p2_057, 
wapp.20081204.a2048.0002 Scan: AGES3193_p2_059, 
wapp.20081204.a2048.0003 Scan: AGES3193_p2_061, 
wapp.20081204.a2048.0004 Scan: AGES3193_p2_063, 
wapp.20081204.a2048.0005 Scan: TOGS Calibration, 
Radar at 1340 MHz present on some scans.
MS wapp.20081204.a2048.0006 Scan: TOGS callibration, 
wapp.20081204.a2048.0007 Scan: AGES7448_p3_114, 
wapp.20081204.a2048.0008 Scan: AGES7448_p3_126, 
wapp.20081204.a2048.0009 Scan: AGES7448_p3_128, 3 seconds NOT on source
wapp.20081204.a2048.0010 Scan: AGES7448_p3_130, 
Good run. Strong 1350 MHz and a small 1340 MHz Radar Spike
MS wapp.20081205.a2048.0000 Scan: AGES3193_p2_073, Warning RA had passed, 3 Seconds NOT on source.
wapp.20081205.a2048.0001 Scan: AGES3193_p2_065, 
wapp.20081205.a2048.0002 Scan: AGES3193_p2_067, 
wapp.20081205.a2048.0003 Scan: AGES3193_p2_069, 
wapp.20081205.a2048.0004 Scan: AGES3193_p2_071, 
wapp.20081205.a2048.0005 Scan: TOGS Calibration, 
wapp.20081205.a2048.0006 Scan: TOGS Calibration, 
4B low on Galspect, however has been calibrated by wapps so looks fine on ALFA data window. 1340, 1350 Radar Spikes are present.
MS wapp.20081205.a2048.0007 Scan: TOGS Calibration, 
wapp.20081205.a2048.0008 Scan: AGES7448_p3_132, 
wapp.20081205.a2048.0009 Scan: AGES7448_p3_134, 
wapp.20081205.a2048.0010 Scan: AGES7448_p3_136, 
wapp.20081205.a2048.0011 Scan: AGES7448_p3_138, 3 Seconds NOT on source, spike at 1380 MHz for 1 minute. Last couple minutes of scan operator reported azimuth movement not running, no errors reported on Cima and data looked fine.
Couldn't do 33PP scan as telescope lost ability to change Azimuth (occured at end of 7448_p3_138). Strong 1350 Radar and small 1340 MHz spike present on most scans, 4B still showing low on GALSPECT but fine on ALFA Data window. Due to poor scheduling am having trouble fitting one 33PP scan in 1 hour slot.
MS wapp.20081206.a2048.0000 Scan: AGES3193_p2_075, 
wapp.20081206.a2048.0001 Scan: AGES3193_p2_077, 
wapp.20081206.a2048.0002 Scan: AGES3193_p2_079, 
wapp.20081206.a2048.0003 Scan: AGES3193_p2_081, 
wapp.20081206.a2048.0004 Scan: AGES3193_p2_083, 
wapp.20081206.a2048.0005 Scan: TOGS Calibration, 
wapp.20081206.a2048.0006 Scan: TOGS Calibration, 
1340 and 1350 MHz Radar Spike, same issue with 4B as above.
MS wapp.20081206.a2048.0007 Scan: TOGS calibration, 
wapp.20081206.a2048.0008 Scan: AGES7448_p3_140, Warning that RA passed and 10 seconds NOT on source
wapp.20081206.a2048.0009 Scan: AGES7448_p1_141, 
wapp.20081206.a2048.0010 Scan: AGES7448_p1_143, Small spike briefley at 1380MHz
wapp.20081206.a2048.0011 Scan: AGES7448_p1_145, 1 second NOT on source, new small spike at 1390MHz
wapp.20081206.a2048.0012 Scan: TOGS calibration, 
wapp.20081206.a2048.0013 Scan: AGES33PP_p1_097, 
Good run. Ditto about 4B. Radar present.
MS wapp.20081207.a2048.0000 Scan: AGES3193_p2_085, 
wapp.20081207.a2048.0001 Scan: AGES3193_p2_087, 
wapp.20081207.a2048.0002 Scan: AGES3193_p2_089, 
wapp.20081207.a2048.0003 Scan: AGES3193_p2_091, 
wapp.20081207.a2048.0004 Scan: AGES3193_p2_093, 
wapp.20081207.a2048.0005 Scan: TOGS calibration, 
wapp.20081207.a2048.0006 Scan: TOGS calibration, 
Good run, Radar present, same with 4B.
MS wapp.20081207.a2048.0007 Scan: TOGS Calibration, 
wapp.20081207.a2048.0008 Scan: AGES7448_p1_147, 
wapp.20081207.a2048.0009 Scan: AGES7448_p1_149, 
wapp.20081207.a2048.0010 Scan: AGES7448_p1_151, Small spikes at 1380MHz and 1388MHz for ~3.5min (other than radar ones)
wapp.20081207.a2048.0011 Scan: AGES7448_p1_153, 2 seconds NOT on source. Very small spike at 1388MHz for all scan on some of the channels (other than radar)
wapp.20081207.a2048.0012 Scan: TOGS calibration, 
wapp.20081207.a2048.0013 Scan: TOGS calibration, 
wapp.20081207.a2048.0014 Scan: AGES33PP_p1_119, 
Had to change order of 33PP scans just to fit one scan in a hour session and still has 15.88 ZA. Radar Present. 4B still low on GALSPECT but fine in Alfa-data display.
08/12/2008 MS wapp.20081208.a2048.0000 Scan: AGES3193_p2_095, 
wapp.20081208.a2048.0001 Scan: AGES3193_p2_097, 
wapp.20081208.a2048.0002 Scan: AGES3193_p2_099, 
wapp.20081208.a2048.0003 Scan: AGES3193_p2_101, 
wapp.20081208.a2048.0004 Scan: AGES3193_p2_103, 
wapp.20081208.a2048.0005 Scan: TOGS calibration, 
wapp.20081208.a2048.0006 Scan: TOGS calibration, 
Good run, Same with 4B, usual radar spikes.
MS wapp.20081208.a2048.0007 Scan: TOGS calibration, Warning extrapolating pnt-data forround 0.00002s then Warning Interpolating pnt-data for 2 seconds.
wapp.20081208.a2048.0008 Scan: AGES7448_p1_157, 
wapp.20081208.a2048.0009 Scan: AGES7448_p1_159, Spike at 1380MHz for three minutes
wapp.20081208.a2048.0010 Scan: AGES7448_p1_142, 
wapp.20081208.a2048.0011 Scan: TOGS calibration, 
wapp.20081208.a2048.0012 Scan: AGES33PP_p1_117, 
Usual Radar, and 4B on Galspect (but fine on Wapps)
MS wapp.20081209.a2048.0000 Scan: AGES3193_p2_105, 
wapp.20081209.a2048.0001 Scan: AGES3193_p2_107, 
wapp.20081209.a2048.0002 Scan: AGES3193_p2_109, 
wapp.20081209.a2048.0003 Scan: AGES3193_p2_111, 
wapp.20081209.a2048.0004 Scan: AGES3193_p2_113, 
wapp.20081209.a2048.0005 Scan: TOGS calibration, 
wapp.20081209.a2048.0006 Scan: TOGS calibration, 
Good run, ditto 4B, usual Radar.
MS wapp.20081209.a2048.0007 Scan: TOGS calibration, 
wapp.20081209.a2048.0008 Scan: AGES7448_p1_144, 
wapp.20081209.a2048.0009 Scan: AGES7448_p1_146, Small spike at 1380 MHz appeared for ~3.5 min (other than radar)
wapp.20081209.a2048.0010 Scan: AGES7448_p1_148, 1 Second NOT on Source
wapp.20081209.a2048.0011 Scan: TOGS calibration, 
wapp.20081209.a2048.0012 Scan: AGES33PP_p1_115, 
Missed intended first scan due to maintenance over-running. Usual radar and 4B
MS wapp.20081210.a2048.0000 Scan: AGES3193_p2_115, 
wapp.20081210.a2048.0001 Scan: AGES3193_p2_117, 2 seconds NOT on source
wapp.20081210.a2048.0002 Scan: AGES3193_p2_119, 
wapp.20081210.a2048.0003 Scan: AGES3193_p2_121, 
wapp.20081210.a2048.0004 Scan: AGES3193_p2_123, 1 second NOT on source
wapp.20081210.a2048.0005 Scan: TOGS calibration, 
Good run, usual radar and ditto 4B.
MS wapp.20081210.a2048.0006 Scan: TOGS calibration, 
wapp.20081210.a2048.0007 Scan: AGES7448_p1_155, 
wapp.20081210.a2048.0008 Scan: AGES7448_p1_150, 
wapp.20081210.a2048.0009 Scan: AGES7448_p1_152, Big spike at 1380MHz and small at 1390MHz (other than usual radar)
wapp.20081210.a2048.0010 Scan: TOGS calibration, Big spike 1380Mhz
wapp.20081210.a2048.0011 Scan: AGES33PP_p1_113, Big spike 1380Mhz for first part of scan
Operator reported TOGS was stopped and restarted during a run (computer got logged off). Usual Radar and 4B is same.
MS wapp.20081211.a2048.0000 Scan: AGES3193_p2_125, Warning extrapolating PNT data for 0.000012s and then interpolating pnt-data over 2 second time gap
wapp.20081211.a2048.0001 Scan: AGES3193_p2_127, 
wapp.20081211.a2048.0002 Scan: AGES3193_p2_129, 
wapp.20081211.a2048.0003 Scan: AGES3193_p2_131, 
wapp.20081211.a2048.0004 Scan: AGES3193_p2_133, 
wapp.20081211.a2048.0005 Scan: AGES3193_p2_135, 3 seconds NOT on source, Warning extrapolating PNT data for 0.000011s and then interpolating pnt-data over 2 second time gap
wapp.20081211.a2048.0006 Scan: TOGS calibration, 
Good run, Usual radar and 4B problem on GALSPECT but not on Wapps
MS wapp.20081211.a2048.0007 Scan: AGES7448_p1_161, 
wapp.20081211.a2048.0008 Scan: AGES7448_p1_154, 
wapp.20081211.a2048.0009 Scan: AGES7448_p1_156, Usual GPS at 1381 for 3.5 mins
wapp.20081211.a2048.0010 Scan: TOGS calibration, 
wapp.20081211.a2048.0011 Scan: TOGS calibration, 
wapp.20081211.a2048.0012 Scan: AGES33PP_p1_111, 
Good run. Usual radar and interesting 4B on GALSPECT.
MS wapp.20081212.a2048.0000 Scan: AGES3193_p2_137, 7 seconds NOT on source
wapp.20081212.a2048.0001 Scan: AGES3193_p2_139, 1 second NOT on source
wapp.20081212.a2048.0002 Scan: TOGS calibration, 
wapp.20081212.a2048.0003 Scan: TOGS calibration, 
Good run, usual radar and 4B
MS wapp.20081212.a2048.0004 Scan: AGES7448_p1_158, 
wapp.20081212.a2048.0005 Scan: AGES7448_p1_160, Usual GPS at 1381 for 3 minutes.
wapp.20081212.a2048.0006 Scan: AGES7448_p2_141, 
wapp.20081212.a2048.0007 Scan: TOGS calibration, 
wapp.20081212.a2048.0008 Scan: AGES33PP_p1_109, 
Good run, usual radar and low 4B on GALSPECT (fine on ALFADATAWIN
13/12/2008 MS wapp.20081213.a2048.0000 Scan: AGES7448_p2_143, 
wapp.20081213.a2048.0001 Scan: AGES7448_p2_145, 
wapp.20081213.a2048.0002 Scan: AGES7448_p2_147, 
wapp.20081213.a2048.0003 Scan: TOGS calibration, 
wapp.20081213.a2048.0004 Scan: AGES33PP_p1_099, 
wapp.20081213.a2048.0005 Scan: AGES33PP_p2_080, 
6B down so a lot of WAPP channels with two little power warnings. 4B still not quite write on GALSPECT. 1350MHz radar is present.
14/12/2008 RA Complications due to scheduling. Running TOGS too early meant that it was chasing the NGC7448 sources, not the 33PP sources. So it was waiting for NGC7448 to rise again. Got the TO to send the telescope to the start position for TOGS and ran the galfacurpos script, but unfortunately the script waited to get on source and wouldn't continue. By the time I noticed and skipped the tracking command, it ended up overrunning the start time for our obs. I think we need to revise the script for these two fields (7448 and 33PP). Matt apparently had similar problems.
16/12/2008 RA wapp.20081216.a2048.0000 Scan: TOGS Cal, Aborted after run 2 A7 due to time constraints
wapp.20081216.a2048.0001 Scan: AGES33PP_p1_103, 
17/12/2008 RA wapp.20081217.a2048.0000 Scan: TOGS calibration, 
wapp.20081217.a2048.0001 Scan: AGES33PP_p1_101, Appears to be truncated - do not use
Robbie didn't write log - ask him for comments.
19/12/2008 KLO wapp.20081219.a2048.0000 Scan: AGES3193_p2_141, 
wapp.20081219.a2048.0001 Scan: AGES3193_p2_143, 
wapp.20081219.a2048.0002 Scan: AGES3193_p2_145, 
wapp.20081219.a2048.0003 Scan: AGES3193_p2_147, 
Did not run the galafa scripts due to lack of time.
Script ended 15 minutes early.
20/12/2008 KLO wapp.20081220.a2048.0000 Scan: AGES3193_p2_149, 
wapp.20081220.a2048.0001 Scan: AGES3193_p2_151, 
wapp.20081220.a2048.0002 Scan: AGES3193_p2_153, 
wapp.20081220.a2048.0003 Scan: AGES3193_p2_155, 
wapp.20081220.a2048.0004 Scan: AGES3193_p2_157, 
Could not ssh into dataview. At operators suggestion, ran /home/cimca/bin/clear_cima to clear things out and then there was no problem. Due to delay, I did not run the galfa script.
21/12/2008 SS wapp.20081221.a2048.0000 Scan: AGES3193_p2_157, 
wapp.20081221.a2048.0001 Scan: AGES3193_p2_159, 
wapp.20081221.a2048.0002 Scan: AGES3193_p2_161, 
wapp.20081221.a2048.0003 Scan: AGES3193_p2_002, 
wapp.20081221.a2048.0004 Scan: AGES3193_p2_004, 
No log form written ask Steve for comments. Looks like many power warnings (maybe one of the polarisations was down?). Looking at data, there appears to have been problems with 1b but otherwise ok.
01/01/2006 wapp.20060101.a2048.e.g. (0001) Scan: scan name, Any Comments?