Startup:

• Ask the telescope operator to move to the azimuth and approximate zenith angle of the drift you're doing. This 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). But... 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 Az=360, not 0 if observing the southern part of the sky (to avoid wrap problems). Usually the best way 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.)

• Open up the catalog file /share/obs4/usr/a2010/a2010.cat (use the alias: a2010obs to get to that directory) and estimate (including slew time) when the telescope will be on the meridian. Edit the TOGS entry called galfasrc to the new right ascension and declination for that night. Adjust the RA entry by estimating as the previous observer is finishing, and again during setup if there are delays, when the telescope will be in position on the meridian.

• 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 (Ver 3.1.02 2008-12-29 17:19)".
  • Project Number: a2010
  • Observer: your name
  • select Line and Accept.
  • Choose Receiver: ALFA and "Accept". Note: "Quick Tsys" should be "no", "rotate receiver" and "retrack source" should be "yes".

• Utilities Menu
  • Restart the WAPPs
  • Close when output to log window complete.

• Command File Observing (TOGS) Menu
  • Click Load - to open a menu listing available command files.
  • Select the file 'command_galfasrc09.cmd' (scroll down) and then click Accept.
  • When the operator has given the OK that TOGS is running, check and, if necesary, adjust starting RA on galfasrc entry in a2010.cat.
  • 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)
    
  • If the requested RA is past meridian, the command file may hang and need to be restarted. If so, 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. But, even if you don't run it at the beginning, run the TOGS calibration at the end, if there is time and GALSPECT is running.

• Utilities Menu
  • Restart the WAPPs again, just to be sure!
  • Close when output to log window complete.

• Load the standard A2010 configuration file
  • Select Load configuration
  • Select the appropriate file. In January 2009, we are using a2010_az360_2009.conf because we are observing south of zenith. Check that the parameters look correct and 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. Everything will be done for you.

• Pointing Control Menu   Note: If you have already positioned the telescope, e.g. for TOGS, this step should not be necessary. The configuration file should take care of it; use this widget to move the telescope in advance of starting A2010 if you need to.
  • If not already loaded, Load the catalog a2010.cat and
  • Click on the entry for the night's block from the list in lower half of menu.
  • Update the RA (adding enough time to account for slew time to reposition after galspect)
  • Click Apply and continue while telescope points.
  • Check that velocity is set to 0, reference frame to topocentric and type to optical.
  • Click ALFA rotation control window button. Set Rotation angle: 19.0 deg (for AZ=360 or 180). Click Send and then click Close.
  • Click 0 to choose beam 0 as ALFA center.
  • Note:WAIT until ALFA revolves into place. Otherwise the IFLO control and wapp configuration will not respond, and some ALFA beams may not "turn on". (We think this is not longer a problem)
  • Note: if there are problems with ALFA not responding (e.g., it doesn't rotate), click Restart ALFA under the Utilities menu.
  • Dismiss this window if you don't use it; you can call it from within "CIMA observing menu".
• 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.

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 button to the right of the start position marked drift#p# and select proper drift from the a2010.cat, check the RA is set ahead enough for the starting RA, check declination, and click use now and then click accept.
  • The rest of the values in red should be quickly checked. 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.
    • Azimuth position should be either 180 degs or 360 degs. (Note 180 is equivalent to 540 and telescope will know to go to the closer angle, so you do not need to change to 540.)
    • ALFA rot angle is 19 degrees (at least for now).
    • Start position is the drift you want; if not, click on it to load another from the catalog "a2010.cat" or to update the R.A.
    • 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
  • Click Adjust power Wait until output in log window confirms power adjustment. Once observations have started, check power numbers 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.
  • Check that the telescope is actually at the correct declination - look at 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.

When Observing:

• 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 in the directory /share/a2010/idl/eggidl. Run @wasinit2 first, then
  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.
  Or 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. 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:

• Procedure:
  • Abort Observation in, e.g., the observing menu
  • Restart the WAPPS under Utilities
  • Repeat start up process, beginning from Load Configuration
  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.
• If running TOGS: (if not, skip to next step)
  • 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_galfacurpos09.cmd', click open , 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.
• Exit CIMA normally
• 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...