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.
IMPORTANT CHANGES FOR SEPTEMBER 2011
Beam 4A is dead; the AO folks
are looking into this. This means you are going to see oodles of warning messages and
the CIMA logs will be big.
We are trying to complete the zenith strip drifts which means that we will be observe off-meridian
for much of September. Fortunately,
since the ZA is no longer restricted, this is easier than it was last year. But please read and understand the
A2010 instructions for
zenith strip observing to understand the limitations and our approach to them.
Warning from Sept 2010: (we do not know in 2011 if this is still an issue)
Warnings about WAPP chip count errors appear in the cimalog file (but not in the CIMA log window).
This warnings do not appear to be 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: (we do not know in 2011 if this is still an issue)
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.
- We are using several special configuration files "*.conf", both for a2010 and the
TOGS calibration. They all have "11" in their names.
- In Sept 2011, we will be observing north of zenith, and in most cases in September, in "zenith strip" mode. You need
to check the schedule to know what azimuth (and what configuration file) to choose.
NEW!!
- In Fall 2011, TOGS runs at the start of A2010 ONLY. Time is not allocated to run
TOGS at the end of the night, so don't run it at the end unless there is extra time (a gap before
the next program). Furthermore, for zenith strip observing,
TOGS points to a position specified in (Az,ZA) that is set by
the TOGS team. As long as they do their homework, you should not have to edit any files for them.
If we are doing meridian observing, you will need to modify the a2010.cat file. There are two
TOGS command files, (cleverly) named command_galfasrc_zenstrip.cmd and command_galfasrc_meridian.cmd.
Execute the one appropriate to the observing mode. NEW!!
If the TOGS files are not properly set up or there are problems running it,
please call Josh Peek (510/299-4427) to let him know (but don't delay the start of A2010; you can always
call him later).
- For zenith strip observing, we
use a new set of basic configuration files called a2010_az85_2011.conf
(for observations near but not at 90 degrees) and a2010_az265_2011.conf
(for observations near but not at 270 degrees). These only get you close to what you need;
you have to make further adjustments by hand
because the azimuth and ALFA rotation angle change each day. Note: When we return to meridian
observing, we use the standard files a2010_az180_2011.conf or a2010_az360_2011.conf;
in that case, the configuration file will set the ALFA rotation angle to the correct value (+19.0 degrees
on the meridian).
- For zenith strip observing, you may need to adopt Az+360 rather than the Az listed in the schedule; we
think that the telescope control system is smart enough to pick the nearest one, but we suggest that you
note where the previous observer has left the telescope, think about options,and then make the right
choice (Az or Az+360) yourself. Be sure to record the one actually used by the telescope control software.
- For the zenith strip, the hour angle is non-zero, i.e. the right ascension and
LST ranges do not coincide; they are offset by 20-30 minutes, earlier or later,
depending on whether we are observing south of, or north of, zenith. Check the schedule.
- For the zenith strip, the configuration file doesn't set everything for you and you need to make adjustments
by hand after it is loaded. After the telescope gets to the approximate position,
you need to (1) rotate ALFA using the pointing control widget,
(2) set the azimuth,
the ALFA rotation angle and the starting R.A. in the spectral line observing
widget.
- For the zenith strip observing, you may notice that the Z.A. changes systematically during
the night. Remember that we are tracking in J2000 coords
and it is now 2011.7. Close to 90,270 a small change in Decl translates to a larger change in Z.A.
Refer to the ALFALFA notes on precession.
- Check that the ALFA rotation angle looks ok using alfabeamwin but remember that the coordinates
displayed in this widget may not be exactly correct. In fact, close to 90 or 270, the optimal rotation angle will
vary by a lot; we have chosen a single "best value" (it is not clear we can determine it more accurately, anyway).
As long as the arrangement looks reasonable for our desired
mode, then we should be ok.
- We position the telescope at a particular Az and DecJ2000. The resultant Az and ZA won't
exactly match (because of the pointing, precession and the hour angle). The hour angle is determined
by when you actually start taking data; our
setup assumes a value which may not be exact. Just be sure 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....
- Please record extra information (az, ALFAang, start/stop RA) at the top of the log file; see a recent log file that
also used the off-meridian/zenith strip observing mode.
- 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.
|