A2143 Remote Observing Instructions

log on to observer2 as dtusr (get password from TO if necessary).
Run the scripts monpnt and /home/aoui/bin/aostatus if you want to
get a sense of what the telescope is doing during the run.
Start CIMA: type 'cima --V' and choose the normal version, or if
you know how to do it through VNC then by all means do it that way.
Enter the relevant information so that the TO will approve your 
remote session.  The project is a2143, and it is a LINE project.
Once cima is running, select L-Band Wide from the 'Choose Receiver'
GUI.  Click on 'disable quick tsys', then click 'Select Receiver Now'.
The CIMA log display window should tell you when the receiver is in
place.
Next, on the CIMA Observer's Interface GUI, click on 'Receiver IF/LO
Control' and set the L-wide Filterbank to 1360-1470,1550-1870, then
click on 'Send L-Wide Setup' and Dismiss the window
Now click on Pointing Control and on the Telescope Pointing Control
GUI set the Velocity Frame to LSR.  I have left the Velocity Type 
as 'velocity(optical)' even though for A2154 we set it to z(radio).
I don't think this makes a big difference since we leave 'Velocity/z'
as 0.0.  Select the source B0300+162 from the list of calibration
sources and click 'Point'  This is the source on which we do the spider
scan.  It should be up at the start of the run.  
While the telescope is slewing to B0300+162, click on Backend Control
on the Interface GUI.  On the 'Backend Control...' GUI, click on 
'Load/Save Setup' and then 'Load a Saved State' on the next window that
pops up.  When the window 'Load Configuration File' pops up, click on
'brdset.gui' and cima will load that config file in.  Click 'Continue'
on the window that informs you that brdset.gui was loaded.  Make sure
the backend control looks good (interim correlator, 4 boards at 9-level
A&B pol sampling, bandwidth is 0.78125 MHz, 1024 lags, double nyquist
set, and the frequencies are 1665, 1667, 1720 and 1420).  Click on
'Apply Current Setup' and dismiss all windows related to backend control.
While the telescope is still moving, click on Calibrate on the Interface.
Select B0300+162 there too, and click 'Start Spider Scan' when the telescope
has started tracking that source.  This might also be a good time to set
up the Spectral Line Observing GUI, so click that one on the Interface and
set Cal to hcal, Scan duration to 5 minutes, and Loops to 4.
While the Spider Scan is running, use the Telescope Pointing Control GUI
to load in the a2143 source list.  Click on 'Catalog: calib.cat' and in 
the new window click on 'Find Any Catalog File' - this will appear to make
CIMA freeze for a while, so that's why it's good to do this at the start
of the spider scan.  Eventually a window will come up called 'Select Catalog
File' - select a2143masterlist.txt and click 'Open' - the font may be hard
to see; it is on my screen.  The sources will appear in the Telescope Pointing
Control GUI - keep the Pointing GUI up since you'll need it every 22 minutes
or so.
Once the spider scan is done, the IDL0 window will show the beam parameters
for the calibration run.  Check that the beam looks OK, and that parameters
like Tsys and efficiency (eta) are good, say around 35-40 K and 0.7-0.8
respectively.  Once the spider scan is completely done, it's OK to select
a point from the a2143masterlist and tell the telescope to point there.
If you haven't already done so, set up the Spectral Line Observing GUI now
(see above for specifics).
The Sources
-----------
There are 15 sources, groups as follows:
Group 1: cloud1a, cloud1f, cloud1n, mbm18hi, mbm18lo
Group 2: cloud1b, cloud1d, onvaxis, offvaxs, mbm18md
Group 3: cloud2a, cloud2b, cloud2c, cloud2d, cloud2e
It's not the best naming convention but whatever.  The observing strategy
is to start by doing all of either Group 1 or Group 2 on alternate days, 
(in the order specified above!!!)
20 minutes per point, and then ending on Group 3, taking up the observations
wherever they left off the previous day.  For example, suppose on day 5 I
did Group 1, then got 4 scans done on cloud2c but only 2 loops on cloud2d.
Then on day 6 I would do the Group 2 sources, then do 2 loops on cloud2d 
before moving on the 4 loops on cloud2e, then on to cloud2a if I still had
some time left.
To start the scans, simply click 'Observe' on the 'AO Spectral Line Observer's
Widget'  The telescope will do the 4 loops and when the CIMA observations
status window says the telescope is IDLE, that's your cue to select a new
point on the Pointing Control GUI, and tell the telescope to move there.
You can hit 'Observe' again right away, so the telescope will start the next
set of loops as soon as it starts tracking the next point.
Keep an eye on 'wrap' on your monpnt window!  It'll probably go to a value of 
-1 when it starts tracking B0300+162.  You'll want to ask the TO to set the
'pnt wrap' to zero, so that when the telescope crosses the meridian it doesn't
decide it wants to add 15 minutes to all the slew times to reach other points.
If the wrap is 1 or 2 instead of -1, make sure to keep in touch with the TO
to avoid similar wrap issues.
When you're done, click 'Exit CIMA' on the Interface, and that's it.
Real-Time Monitoring
--------------------
It's pretty simple to monitor the spectra as they're being recorded.  I've 
written some simple scripts and if you go to 
/home/kdouglas/OH/worklog.txt on the AO network you can probably figure it
out from there.