Arecibo L-band Feed ArrayNGC 2903 Drift Observations

Results

Last Update:

Date Observer(s) Target CIMA log file Comments
28 Nov 2004 MP, MPH, RG, BC az252d2151 - az104d2059 Power on Beam0b is low (< 0.7) and staying low. Power on Beam6a is low (0.75 --- noticed on 0007.fits), Beam0b is still low. 2nd Map aborted by observer (0001.fits Az 250.63884, rotangle -53). The partial map of the 2nd and full map of the 3rd are both contained in the 0001.fits file. 4th map is in 0002.fits, 5th in 0003.fits etc. After NGC2903, doing beam maps on r1020d2159 (0011-0017.fits). Dummy file at end.
FITS files: wapp.20041128.a1963.0000-0017.fits
29 Nov 2004 MP, BC, RA az252d2142 - az104d2151 Power on Beam0b is low (< 0.7) and staying low. The source names on this date are not correct for the first 4 files (the name is 1 dec step higher than the actual pointings, which are correct). For file 0001 (scan #2) the data taking began before the telescope reached the beginning of the scan. Approximately 1 minute of this scan was lost and the scan has a strip off of the cube which will affect the data reduction if not removed. File 0002 (scan #3) has a similar problem, but only a few seconds were lost. It just did the same thing on scan #6, started taking data 1 minute early. Fits 0011: cannot be done (wait time ~30 min!), aborted. Fits 0012: AZ and rot. angle calculated using AGES software (alfa_ang); aborted at the end b/c no time.
FITS files: wapp.20041129.a1963.0000-0012.fits
30 Nov 2004 MP, BC, RG, MPH RA=9:28:10, Dec=21:51:26 FixedAZ2.tcl script modified: scan does not start until ALFA rotation has been completed. Running on generator power. System temperature is about 30 instead of 28-29. Using new file. 0006.fits started 8 secs late, otherwise all files started on time.
FITS files: wapp.20041130.a1963.0000-0011.fits
01 Dec 2004 MP, RG RA=9:28:10, Dec=21:03:56 Power low on Beam0B (~0.69) All scans had time to start (see ngc2903_results.tbl)
FITS files: wapp.20041201.a1963.0000-0011.fits
02 Dec 2004 MP RA=9:28:10, Dec=21:32:56 Power good All scans had time to start (see ngc2903_results.tbl) Went to 1021+219 at end, it started taking data ~15s before at right place Kicked off on time, most likely nothing useful in these files (0012-0015.fits)
FITS files: wapp.20041202.a1963.0000-0011.fits
03 Dec 2004 MP RA=9:28:10, Dec=21:13:26 Power good at start Option to do a cal at start and end has not been implemented yet SWITCHING TO LOOP START to make using livedata better Power on Beam 3b slightly low (~0.79), improves at end of night Wandering birdy about
FITS files: wapp.20041203.a1963.0000-0011.fits
04 Dec 2004 mph,rg RA=9:28:10, Dec=+21:22:56 All runs smoothly except that Beam 5, both pols is dead. This started at 19:50AST during a1956 run. Data recorded as "NULL" in FITS. Beam 4 is fine (other beam on same WAPP). Willie will call Bill Sisk at 7am. We note that ALFA rotates before slew starts. Near transit, we time this at 36sec for a 41deg rotation. More overhead...
FITS files: wapp.20041204.a1963.0000 to 0011
05 Dec 2004 mph, rg RA=09:28:10, Dec= +21:41:56, plus continuum sources Beam 5b shows poor bandpass slope. Otherwise, spectral line observing ok. N2903 clearly seen in Beams 1 and 6. Use some X111 time to make drifts across 3 continuum sources, in transit fixed az. First centered on Beams 2-0-5. 2nd centered 1' south; 3rd 1' north; to check rotation angle zero point. See detailed logfile.
FITS files: wapp.20041205.a1963.0000-0014
06 Dec 2004 mph,rg Beam maps 0805+21 and 1021+21 Testing the beam map scheme works very well. Using 50 MHz BW centered at 1405 MHz. 240 sec drifts with CAL = LOOPEND Wandering birdy noticeable, esp. at beginning.
FITS files: wapp.20041206.a1963.0000 to 0023
14 Dec 2004 SL, BC, EM RA:09:28:10, DEC:+21:46:41 Beam 5 pol. B has a bad bandpass slope. Power levels for beams 2B, 3B, 4B, and 5A tend to be slightly low (~0.78).
FITS files: wapp.20041214.a1963.0000-0011
15 Dec 2004 EM, SL RA: 092810, DEC:+213711 Beam 5 pol B: bad bandpass. FITS 0002 is aborted. Scan 435015049: beam4, pol B power level is at 77.7%. Sacn 435015673: beam4, pol B, power level is at 78.4%, and beam 5, pol A, power level is at ~79.6%. For every fits file there seemed to be more than one scan number. Deal with caution with the scan numbers reported in the table.
FITS files: wapp.20041215.a1963.0000 to 0010.fits
16 Dec 2004 SL, EM, LH RA 092810, Dec 212741 Beam 5B still has badly sloped baseline Beam 3B power slightly low (0.795) in .0003.fits Power adjusted after .0003.fits; OK for .0004.fits Several power levels high during cal, .0007.fits
FITS files: wapp.20041216.a1963.0000 -- 0011
17 Dec 2004 SL, EM, LH RA 080338, Dec 210844, then RA 101955, Dec 220124 Slew > 6 min to start; missed first two drifts. First 3 scans (0000.fits - 0002.fits) have source misnamed as beam2159; should be beam2108. Coordinates are correct. First scan on beam2201 ran during long slew, aborted. Second scan on beam 2201 skipped, too late. Third scan in 0007.fits after aborted scan. File 0010.fits has aborted scan (during slew) at start, then 435215515 has 1-2 secs data before on source. Rest of scan OK.
FITS files: wapp.20041217.a1963.0000.fits -- 0006.fits, 0007.fits -- 0021.fits
18 Dec 2004 LH, SL, EM beamd2106, beamd2159 Error messages about the chip counts not matching in WAPP(1) at the beginning.
FITS files: wapp.20041218.a1963.0000 to 0021.fits
19 Dec 2004 LH, SL beamd2106,beamd2159 Went smoothly tonight.
FITS files: 0000-0023
20 Dec 2004 LH, SL beamd2106,2159 Power level high on beam 3b each time the continuum source passed through. Also high power level once for beam 3a (fits file 0017).
FITS files: 0000-0023
21 Dec 2004 SL, LH beamd2106, beamd2159 First scan (000.fits) has source center dec, not offset. Corrected for second and later scans. Appears to be second continuum source in southernmost beam while target (beamd2106) is in northernmost two beams. Aborted first scan in 0007.fits since slew was longer than time available. Second "source" appears in southermost two beams when beamd2159 is in northernmost -- strong second sidelobe at ca. 12'? Beam 1A and 1B have high power levels as beamd2159 drifts through.
FITS files: wapp.20041221.a1963.0000 - 0020.fits
22 Dec 2004 LH, SL beamd2106, beamd2159 Power levels wouldn't adjust in the beginning, so we exited CIMA and restarted it. Power levels go out of range during the calibration. Also high power levels in beam 4 when the continuum source passed through (fits file 0009).
FITS files: wapp.20041222.a1963.0001-0022.fits
23 Dec 2004 LH, EM RA:080538.5, DEC:+210651. RA:10102154.6,DEC:+215931 Got 12 min extra observing time (gap in the schedule). Smooth run!
FITS files: wapp.20041223.a1963.0000.fits -- 0026.fits
26 Dec 2004 LH, EM RA:080338,DEC: 205921. RA:101955, DEC:215200 FITS 0004 is aborted, has bad data.
FITS files: wapp.20041226.a1963.0000 -- 0003.fits, 0005--0029.fits. Smooth run!
10 Feb 2005 EM, BC RA=10:19:55, DEC=22:08:55 (2nd source only) FITS header format changed on Feb 3rd!!!
1st source: went to wrong coords. 2nd source: ok. Notice that difference b/w actual starting LST [AST] and LST [AST] in MPH's table can be up to 3 minutes. Beams 4A, 4B, 5A: strong bsln gradient.
FITS files: wapp.20050211.a1963.0001 -- 0021
11 Feb 2005 EM, BC RA:080338,DEC: 205727; RA:102154 DEC: 215931 Beams 4A, 4B, 5A: strong bsln gradient.
FITS files: wapp.20050211.a1963.0023 -- 0029
wapp.20050212.a1963.0000 -- 0021
12 Feb 2005 BC beamd2106, beamd2159 Beams 4A, 4B, 5A: strong bsln gradient. Got 10 extra minutes at the end. Smooth run.
FITS files:  wapp.20050212.a1963.0023-0027,
wapp.20050213.a1963.0000-0023
13 Feb 2005 BC beamd2106, beamd2159 Beams 4A, 4B, 5A: usual bsln gradient. Smooth run.
FITS files:  wapp.20050213.a1963.0025-0030,
wapp.20050214.a1963.0000-0015
28 Feb 2005 JI, BC lined2118
beamd2212
Beam 5B has strong gradient (1.5 to 0.6). FITS 0000: waterfall plot for beam 0A shows regular pattern of horizontal lines (every 12s?), not seen in pol B or in other beams. Problem disappeared after first or second scan. Problem returned later. During scan 6 noticed that the same problem is now in beam 2A but not in Beam 0A any more. Must have to do with direction of pointing? Then back in beam 0 again. For continuum observations, some RFI seen at 1400 MHz in beam 1A
FITS files:  wapp.20050228.a1963.0000-0007
wapp.20050301.a1963.0000-0006
01 Mar 2005 ji beamd2112, lined2151 Same interference in beam 0a as seen yesterday bandpass 5b a little wavy but not as steep a gradient as yesterday. Interference seen in 3a and 2a also -- this is low level across all channels -- also see interference in channel 1a at 1400 MHz only, like yesterday. noticed bandpass 5b is bad again. scan 0024 had wrong rotation angle.
FITS files: wapp.20050301.a1963.0009-0028
wapp.20050302.a1963.0000-0002
02 Mar 2005 ji beamd2108, lined2156 conditions similar to yesterday Beam maps: missed one scan at az=132.5 (not enough time to get into position) 5b bad baseline again. otherwise good run.
FITS files: wapp.20050302.a1963.0004-0025
wapp.20050303.a1963.0000-0001
03 Mar 2005 ji beamd2106, lined2108, beamd2157 some baseline ripple evident about about 20% level in 5B on continuum. 5B is still very slopy on the galaxy, goes from about 1.5 to .7 across the band. 4a shows a ripple in frequency space
FITS files: wapp.20050303.a1963.0003-0023
wapp.20050304.a1963.0000-0002
04 Mar 2005 ji beamd2118, lined2200 On Continuum maps, beam 6a power level has dropped to 0.772 -noticed during fits 0012. Beam 2b has also dropped to 0.800. power adjusted for galaxy obs. On galaxy, 5B baseline is still poor ranging from 1.6 to 0.7. power levels good.
FITS files: wapp.20050304.a1963.0004-0029, wapp.20050305.a1963.0000-0001
05 Mar 2005 ji lined2137,beamd2153 started a big early so got in an extra scan. position now near (north of) galaxy center and emission is showing up nicely. 5B baseline still screwy. During second scan, beam 2 power is getting low (0.799, 0.8). Adjusted power after second scan. Now okay. There is enough time at these azimuths to make the adjustment and still catch the next scan. Interference in beam 0 and beam 2. Have had no other problems with power levels. Managed to catch the calibrator for one scan at az=129 at the end.
FITS files: wapp.20050305.a1963.0002-0014,wapp.20050306.a1963.0000
06 Mar 2005 ji lined2127 observing the galaxy. Again baseline 5b is poor. galaxy clearly visible. There was a power dip during fits 0007 scan. Everything kept running. Beam 6A has low power during scan 8 (.781). adjusted power after scan 8, looks good.
FITS files: wapp.20050306.a1963.0002-0013,wapp.20050307.a1963.0000
21 Mar 2005 SML lined2141 Galaxy observations. One scan was missed, but everything went well otherwise.
FITS files: wapp.20050321.a1963.0000-0010
22 Mar 2005 SML lined2122, 1021+21(beamd2153) Galaxy observations, plus one continuum scan at the end.
FITS files: wapp.20050322.a1963.0000-0011, 0013
23 Mar 2005 SML lined2146, beamd2153 Galaxy scans (13) plus 3 calibration scans.
FITS files: wapp.20050323.a1963.0000-0015
24 Mar 2005 SML lined2118,beamd2153 Problem with power in Beam 0, pol A, low levels around 0.7 which couldn't be adjusted. Scan 3 (fits 0003) had a warning about observing when not on source, also slight mistype in az (248.8383). Lost scans 7-8 due to attempted repairs.
FITS files: wapp.20050324.a1963.0000-0013
25 Mar 2005 SML lined2151,beamd2153 First four scans were missed due to removal of ALFA cover, then lack of power in WAPP 1. Beam 0, pol A still has somewhat low power like yesterday. Eight galaxy scans plus one callibrator scan.
FITS files: wapp.2005325.a1963.0001-0009.fits
26 Mar 2004 SML lined2113, beamd2153 Slight delay in starting due to radar again. Power in beam 0,pol A still low. 11 galaxy scans plus callibrator.
FITS files: wapp.2005.326.a1963.0000-0012.fits