The Arecibo Legacy Fast ALFA (ALFALFA) Survey

A2010 Observing Checklist

WARNING: Version date: November 2011

Cookbook date:	21 Nov 2011
CIMA version :	"A `smart' version of CIMA (3.1.08 2010-02-01 17:44 "Smart")"
WAPPdata :	/share/pserverf.sda3/wappdata/ (a2010 alias is "wdata1")

Find the 2007 version here, the Spring 2008 version here, the Fall 2008 version here, the Spring 2009 version here, and the Jan 2010 version with the normal meridian (transit) setup here. The special Spring 2010 instructions are here as is the corresponding checklist. The normal instructions for Fall 2010 are here as is the corresponding checklist. Find the Aug-Sep2011 (including zenith strip observing) checklist here.

IMPORTANT CHANGES FOR NOVEMBER 2011

Beam 6.1 is dead. This means you are going to see oodles of warning messages and the CIMA logs will be big.
As of Nov 20 (via Dana), Beam 4.0 also appears to be noisy (Tsys ~ 40K); so it is "live" but may be erratic.

If you notice instabilities in other beams or unusual behavior, please be sure to make detailed notes in the log files about what you observe. Also ask the operator to report the problems to Dana and Ganesh. Our immediate feedback is really important... and much appreciated!

Warning Warnings about WAPP chip count errors appear in the cimalog file (but not in the CIMA log window). This warnings are not fatal, but the size of the cimalog file therefore exceeds the limit of the web service. Include it in the loglinks.htm file, but you won't be able to view it. And, of course, keep an eye on the WAPPS: this is not a positive sign.

Warning from Sept 2010: (This does not seem to be an issue now) The TOGS calibration script appears to hang at the stage of rotating ALFA into position and times out (after 2 min). Run it again, and it should work. The problem was reported last year.

For a2010, you need to use the a2010_az180_2011.conf configuration file; the azimuth can be either 180 or 540; pick the one nearer to the current position.
In Nov 2011, TOGS runs at the END of A2010 ONLY. Time is not allocated to run TOGS at the beginning of the night, so don't run it at the beginning unless there is extra time (a gap before a2010 starts). Load the TOGS command file: command_galfacurpos_nov11.cmd.
If there are problems running TOGS, please call Snez (work: 608 890 1458 or home: 608 259 9449) to let her know (but don't delay the start of A2010; you can always call her later).
We position the telescope at a particular Az (on the meridian) and DecJ2000. Always double check that the DecJ2000 is correct by checking that the "Rslt" declination in the monpnt display is the correct DecJ2000. It will be updated every ten minutes (beginning of each drift), so it may stray a bit, and it may require a few seconds to move into position. Remember that that the beam is ~3.5 arcmin and it takes ~14 sec of time for a source to drift through the beam so if you are "off source" for a few seconds at the start of the next drift, it doesn't really matter....
The ALFA rotation angle for meridian observing is 19 degrees. This is set properly when you load the configuration file.
You need to start CIMA by typing "cima --X". (Notice the "--X".)
"Help" info is available by right clicking on any widget or parameter
The sources in your catalog which are "visible" are indicated along with their current location, slew time, etc.
It is possible to launch the system monitoring widgets from within CIMA.
"Accept" is the same as "Apply"+"Dismiss"
The scan number convention is "ydddNNNNN.fits" where "y" is the year number, "ddd" is the day number within the year and "NNNNN" is a sequential number which now has nothing to do with the time. Note also it has nothing to do with the FITS file number.

This is a short checklist of the things to do when observing... for more details see the observing cookbook.
Remote observers, see remote observing checklist .
In case of observational problems, see observational troubleshooting list.
And, it is always a good idea to check the recent log files or ask recent observers about their experiences.

Startup:

Ask the telescope operator to move to the azimuth and approximate zenith angle of the drift you're doing. For meridian observing in general, it can either be 360 degrees (NOT 0) or 180 degrees (540 equivalent) depending on whether the drift tracks north of zenith (Decl > +20d; use AZ => 180) or south of zenith (Decl < +16d; use AZ = 360). In 2011-12, we will always be observing north of zenith, so choose the 180 degrees (540 equivalent) option. And be sure the operator gives you back telescope control! Alternatively, go to the "Pointing Control" window and point the telescope to the first position; just be sure the telescope goes to the proper azimuth. Usually the best approach is to have the telescope operator send the telescope to the approx AZ, ZA before (tell him/her) he/she starts up GALSPECT. If so, don't start CIMA until the telescope is close to position (once you start CIMA, the telescope motion will halt until you start the TOGS command file.)
New: In Nov 2011, run TOGS only at the end of the night! So skip this part; start with A2010 right away!
If running TOGS: Check the TOGS setting:
When we are observing in meridian observing mode, then the source position is specified by the galfasrc position in the a2010.cat file and you execute the command file command_galfasrc_meridian.cmd. Be sure that the declination of galfasrc is the same as the one for the A2010 drift. The TOGS command file sends the telescope to the position specified by galfasrc, and then tracks that position for ~6 minutes. If you have problems running TOGS, please call Josh Peek (510/299-4427) to let him know (but don't delay the startup of the A2010 program; you can always call him later).
LET THE OPERATOR DO THIS STEP! On the dataview machine do the following to start GALSPECT:
- Login to dataview using the a2010 account. Switch to the guest account via ssh -l guest dataview. You must do this as guest.
- In the same xterm window ssh to the galfa1 machines. ssh -i galfa_key galfa@galfa1. You should see a '#' prompt.
- Check if ghost galspect processes are running by typing ps. If processes called gdiag are present, kill them by typing the command kill followed by the process number.
- Warm up GALSPECT via typing /var/diag
- Type the command: /var/levels_togs. If you get the message LO2: Set failed, got back: ERROR setting freq, then you need to start the gpib on the wapp server. To do this, start CIMA and click Restart GPIB under the Utilities menu. Go back to the xterm logged into galfa1 and again type /var/levels_togs. You should not receive an error.
- Enter the command /var/togs. This will run for the rest of the night, so minimize the windows.
  Note: if the operator is not able to get GALSPECT to run, he/she should call the TOGS contact for the night.
Log into OBSERVER2: dtusr (once the previous observer is out). Password is taped to computer.
Start CIMA on-line GUI when telescope is close to start position. At the moment, you need to type cima --X in an available window or right click on the screen background and choose CIMA Online GUI. Select the desired version of CIMA; this is currently "The 'smart' version of CIMA (3.1.08 2010-02-01 17:44 "Smart")".
- Project Number: a2010
- Observer: your name
- select Line and Accept.
Receiver selection menu
- Choose Receiver: ALFA and "Accept". Note: "Quick Tsys" should be "no"; "rotate receiver" and "retrack source" should be "yes".
- Hit Accept
- Close window
Main menu / Utilities / Utilities
- Restart the WAPPs
- Close when output to log window complete.
New: In Nov 2011, run TOGS only at the end of the night! So skip this part; start with A2010 right away!
Command File Observing (TOGS) Menu
- Click Load - to open a menu listing available command files.
- Select the file 'command_galfasrc_meridican.cmd' (scroll down) and then click Accept.
- When the operator has given the OK that GALSPECT is running, check and, if necesary, adjust the RA, Dec for galfasrc in the "a2010.cat" file. Note: In meridian observing, we update the "a2010.cat" file for the TOGS team; it should have the same declination as the A2010 drift.
- Click Run to run the command file. The telescope will slew to requested position and, when it reaches the meridian, TOGS calibration will run for ~7 minutes.
- As soon as "observing menu" appears it can be used to verify settings and then closed. The "command file" window cannot be closed until the run file is finished, at which point click Close . and then continue with Load Configuration menu (below)
- For for any reason the command file hangs, restart it; make sure that you restart from First line by clicking appropriate button at middle left on Command Log GUI.
- Note: if the GALSPECT spectrometer is not set up within ten minutes of their allotted time (so that the ~7 mins of calibration cannot be run before A2010 is scheduled to start), do not run the TOGS calibration if the A2010 prime map LST range is reached. In Fall 2011, we do not run TOGS at the end.
New: In Nov 2011 pick up here without running TOGS.
Main menu / Utilities / Utilities
- Restart the WAPPs again. A favorite A2010 saying is: "When in doubt, restart the WAPPs." Another one is, of course, "Boring is good."
- Close when output to log window complete.
Main menu / Utilities / Load configuration
- Scroll down to select the appropriate configuration file. In Fall 2011-2, this will be a2010_az180_2011.conf. Check the schedule to be sure you know what drift you are observing and which file to use. After selecting the proper configuration file, be sure to check that the parameters look correct.
- Click Load and Apply when ready.
  Note: If this works, you will not need to load the IF/LO configuration or adjust the Backend Control (next two steps below).
Receiver IF/LO selection menu Note: Not needed if you loaded the configuration!
- Check receiver ALFA
- Check ALFA filter choice: Full width
- Check IF/LO path: ALFA
- Check center frequency: 1385.0 MHz (when topocentric observing)
- Check backend: WAPP
- Check bandwidths: 100 MHz
- Click Accept Check that the correct ALFA center frequency (1385 MHz), range (1335-1435 MHZ) and 4 IF band setups (100 MHz) are ok on the upper display screen to right of observer2 computer or in CIMA log window.
- Watch CIMA log window to make sure IF/LO params are set before moving on, then Dismiss both IF/LO windows
Backend Control Menu Note: Not needed if you loaded the configuration, but always needed if you restart the WAPPs!
- This opens the Configure Wapp ALFA window. Check that all WAPPs are using 2 channels and 3 levels and at 100MHz.
- Accept this configuration.
CIMA observing menu (should pop open when configuration file loaded)
- Set the azimuth position to the exact value (DD.DD) for this observation. For Fall 2011/2 meridian observing, this is 180 deg. Notice the possible configuration of Az+360 according to wrap. We think that the telescope will chose the closer one, but double check if the telescope seems to be unwrapping itself. Be sure to record the one that is actually used.
- Set the ALFA rot angle to the exact value (DD.D) for this observation. For meridian observing, this is 19 deg.
- Quickly check the basic setup for fixed azimuth observing. Correct values:
  - The observing mode is Fixed azimuth drift map
  - Number of loops is set to cover length of run. Easiest to leave it at the default 99.
  - Strip time is 600 secs.
  - Drift type is Follow Dec J2000
  - Calibration type is Hcorcal
  - Calibration time is 1 sec
  - Calibrate when is On @ loopend
  - Add extra cal is No
  - Adjust power is First loop only
  - Loops per file is 1 loop
OK, now it is time to pick your drift, make final adjustments and begin observing.

Beginning Observations:

CIMA observing menu: The observing widget should still be open since you didn't close the resulting window after completing the Load Configuration. This is the window you'll be using most of the night. Note it also has buttons that allow you to "adjust power", but you should only do that if you stop/start data taking.
- Click on the start position button and select the proper drift from the a2010.cat for tonight's observation.
- Check the RA is set ahead enough for the starting RA (including the offset from LST). Enter the correct value (if it is not already ok). Review the "status" display to be sure the ZA is what you expect it to be. Adjust RA otherwise. Check that the declination is correct, and click use now and then click accept.
- Click Adjust power Wait until output in log window confirms power adjustment. Once observations have started, check that the power numbers in the Observer's Monitor (alfaobswin) to make sure OK (the numbers should be between 0.8 and 1.2)
- Click Observe to begin the observation. Hopefully only a small countdown will remain, and the photon collecting will begin.

When Observing:

As soon as you start observe, run some immediate quick checks. It is especially important that you do this in Fall 2011 to be sure that the Az, ZA and ALFA rotation angle are correct.
- Check that the telescope is actually at the correct declination
  1. Check the declination displayed in the CIMA observation status window Always check this!
  2: Check the "Rslt" line in the monpnt window (the upper right window on the screen below the frequency band monitor). Dec value should stay within a few arcseconds of the drift value. Always check this!
- Check that the ALFA rotation angle is properly set. Click on telescope in the CIMA observation status window and check the number to the right of "ALFA" in the bottom right hand corner of the display. Always check this!
- Check the power levels and waterfall plots as usual. Always check this! If there are unexpectedly bad beams, consult the telescope operator, and report issues in the nightly log.
Keep a log file - it is very important to keep an accurate log of what happens, even to note "an uneventful night". To do so:
- ssh to another machine as a2010
- open a new file logYYMMDD in /share/obs4/usr/a2010 using you favorite text editor (vi or pico work well when remote observing; emacs is too slow, unless you use the '-nw' flag to open in a terminal.) Use a posted log file as the template.
- record **anything** of note, especially
  (1) the CIMA version number and the saved state (a2010_az360.gui or a2010_az180.gui)
  (2) any bad files,
  (3) any power adjustments,
  (4) unusual rfi etc. (see observational troubleshooting list to check for notes about specific RFI frequencies.)
  To quote Brian: I cannot stress the importance of keeping accurate logs. While the file conversion software works automatically, it is good to have a backup to check against when comparing scan numbers. Sometimes CIMA squeezes in extra scans at the beginning or end of the run, or has some other unpredictable behavior. It is also important to note "empty" files, as IDL will hiccup on these. The folks who calibrate/process the drifts you take will thank you for your carefully note-taking (and will be entirely justified in saying unkind things about you otherwise).
Be vigilant for new sources of RFI; carefully check the waterfall plots and/or quicklook. Know the expected locations in the band of the "usual suspects". The FAA radar is usually at 1350 MHz (although they sometimes use 1330 MHz, out of our bandpass!). Strong RFI at 1367 and 1382 MHz is due to the Punta Salinas naval base radar, which should not be on during ALFALFA run (see this link.) . If you see this, ask the operator to call Punta Salinas immediately and tell them to turn off their equipment! See observational troubleshooting list for other observing issues.)

Between loops:
- Check power levels periodically. They should stay in the range (0.8,1.2) and be coded blue on the dataview observer's monitor. Note any odd power level variations in log. (Remote observers: be sure to note in log that you checked periodically.) Do not adjust the power levels during a run unless absolutely necessary; be sure to make a clear note in the log file if you do so; it is necessary to process separately drifts done before and after the adjustment, so make sure the processer can tell from the log file how to group the drift files.
- Keep track of the times, file numbers, scan numbers for drift and cal and any notes in the log file.
- Keep an eye on the declination on the monpnt window on the right hand console to make sure it is the same (within a few arcsec) of the desired J2000 declination.
File Integrity: Check the FITS files to make sure the coordinates are being written correctly. Use the IDL program quicklook.
- ssh to one of the fast linux machines, like "fusion01", "aolc1", "aolc2" etc.
- > cd /share/a2010/idl/eggidl.
- IDL> @wasinit2
- IDL> quicklook, 'filename'
  where 'filename' is the name of the fits file, with directory path. The directory path can be found in the log file, e.g., /share/wappdata/wapp.20061116.a2010.0011.fits
This is fast and is good to use while remote observing. If you want to look at an arbitrary record, see the file "checkfitsnotes.txt" in the /share/obs4/usr/a2010 directory.
Data Monitoring:
- Use the widgets provided on the dataview computer or within the CIMA widgets (there are lots of monitoring tools; learn to use them!). When you are in the control room, you can start them from the pull-down menu on the dataview machine; be sure that the "CIMA version" is set to what you want. Alternatively, you can open the widgets by typing the following commands on an xterm:
  - alfamonwin & - same display as to the right of the operator's station
  - alfamotorwin &- shows ALFA rotation angle - good to check at start
  - alfabeamwin &- shows approximate positions of each beam; can set to RA,Dec (note: currently, the positions aren't quite perfect but still helpful.)
  - alfaobswin &- smaller window showing the power in dB for each beam
  - alfadatawin &- waterfall plots in your color of choice (select ALFA pattern, then waterfalls from the pull-down menu under diagrams). Too cool. Enough said.
  The latter two (alfadatawin and alfaobswin) are particularly useful in monitoring the data and should be left up in plain sight.
- Notice that you will not be able to start alfadatawin if the process is already running on dataview (started by one of the previous observers). If this happens, ask the telescope operator to kill the previous process or, if he cannot, to contact Mikael, Arun, or Phil to do so.
If there is a power failure... There is a remote "reset" switch for ALFA - it is no longer necessary to go up to the dome and push the reset button.

If the WAPPs get confused...which WILL happen:

The only sign of this happening in CIMA is that messages appear in red in the CIMA log window. WAPP error messages include: WAPPs confused indicates a hardware problem (Note the messages WAPP (3) WARNING - Counts don't match for chip 1 and WAPPDATA-queue_agcdata: WARNING received duplicate AGC-datablock are not WAPP errors.) Occasionally there is no warning message from CIMA, but the countdown time on the aostatus window stops, meaning that the WAPPs are no longer taking data. Sometimes the problems go away, so try to restart the WAPPs and then the observing again.

Procedure:
- Abort Observation in, e.g., the observing menu
- Restart the WAPPS under Utilities
- Repeat start up process
  - Load Configuration as before. Load and Apply
  - Reconfigure the WAPPS: Click on B Backend Control Menu, which opens the Configure Wapp ALFA window. Check that all WAPPs are using 2 channels and 3 levels and at 100MHz. Accept this configuration.
  - In the CIMA observing menu, select drift again and adjust starting time.
  - Adjust power and observe.
If this does not work, try again, up to a few times. If this still does not help, exit CIMA and start again. If the error messages keep appearing, it will be necessary to have the operator call an engineer to look into the problem. Currently, the WAPP experts are Giacomo Comes and Arun.

Finishing Up:

After a few seconds of integration time, abort the last unfinished scan.
In Nov 2011, run TOGS at the end:
If running TOGS:
- Under Utilities, Restart the WAPPs (note any error messages when you do this; if you get any, try restarting the WAPPs again)
- Go to Command File Observing, and click on Load . Choose 'command_galfacurpos_nov11.cmd", click accept , and run the script. TOGS calibration will take about 6 minutes, so be sure to allow for this before the next program is set to start. Note: should the telescope run into the ZA limit during TOGS calibration, just let it finish (or abort and give up). .
Exit CIMA normally
Exit the observer2 machine
Exit data monitoring programs "nicely"
Exit IDL (if you were using it)
CTRL-C out of the GALSPECT control and logout of galfa1 (Let the operator do this!)
Exit out of the dataview machine

After observing...

See the list of tasks to do after each run.
Here is a shorter summary of commands that can be saved to the disk and edited for current date.

This page maintained by the members of the Cornell ExtraGalactic Group and their friends, the other members of the ALFALFA observing team
Last modified: Mon Nov 21 16:18:26 EST 2011 by martha