Changes between Version 87 and Version 88 of PublicPages/MayallZbandLegacy/NotesforObservers

Timestamp:

Feb 10, 2016 8:13:04 PM (8 years ago)

Author:

Knut Olsen

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers

@@ -105 +105 @@
 Log into the mzls account on the mayall-idl machine.
 
-Update the code, log files and most importantly the tile file:
+Update the code, log files and most importantly the tile file: (if people have been working on the code and tile file during the day, this step may not be necessary)
 {{{
 cd ~/products/mosaic3
@@ -197 +197 @@
 2. Take 10 zero exposures [[BR]]
 3. Turn on low dome flat field lamps at 100% intensity (~50V) [[BR]]
-4. Create a dome flat script using the NGUI interface. Exposure times as follows: [[BR]]
+4.  Create a test script using the NGUI interface to take a 5 second exposure through the zd filter.  Run this with TEST.sh in the exec/ directory, and check that the counts you receive are ~9000 ADU in the real-time display.  If they are much higher, you will want to adjust the lamp intensity or flat field exposure time to compensate. [[BR]]
+5. Look for the script DFLATS_MZLS_zd.sh in the exec/ directory and run it if it exists.  You can also create your own dome flat script using the NGUI interface. Exposure times as follows: [[BR]]
        z-band : 20 sec [[BR]]
        r-band : 25 sec [[BR]]
@@ -207 +208 @@
 = [8] Just before observing = 
 
-1. Start the automated script for updating the tile file
+1. Start the may all-idl:1 VNC session.  This session should automatically start MUPTILES and MOSSTAT.  If it doesn't, open a terminal in the VNC session and start the automated script for updating the tile file:
 
 The FITS file listing which tiles have been completed should be updated throughout the night.
@@ -233 +234 @@
 
 1. Take a zero image to ensure everything is working
-2. At start of night, check telescope pointing and zero the telescope coordinates using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane).
-3. Move to the beginning of the first MzLS tile position
+2. At start of night, check telescope pointing and zero the telescope coordinates using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane).  When taking the image of the bright star, make sure to create an OBJECT script with NGUI (not a TEST, because MOSSTAT will ignore it), zd filter, 1 - 5 sec exposure.  Watch for MOSSTAT to process the image and report the RA, Dec offsets.  Give these offsets to the OA with **opposite** sign.  You can take another OBJECT frame if you want to check to make sure the offset went in the right direction.
+3. Move to the beginning of the first MzLS tile position.  What position is that, you ask?  One way to find out is to run mosbot.py (see step 5 below), and look for RA, DEC in expose-1.sh in the exec/mosbot/ directory.  Tell these coordinates to the OA to move the telescope.
 4. Focus the telescope
- - create a focus script using the NGUI
+ - create a focus script using the NGUI: exposure time 5 or 10 seconds, zd filter, -100 micron focus steps, click Midpoint to *on*, 9 exposures.
  - run the focus script from the /home/observer/exec directory 
  - analyze the focus image using mscstarfocus 
     - edit the mscfoc.cl script to correct the name of the image that needs to be analyzed 
-    - mark about 10 stars around the image; mark the top star in each sequence using "m"; "q" to quit 
+    - mark about 10 stars around the image; to get a quick idea if you have covered the right focus range mark "g" on the top star in a sequence which will pop up a graph that you will need to type "q" to get out of; mark the top star in each remaining sequence using "m"; "q" to quit 
  - log the Truss temperature 
- - set the telescope focus  
+ - set the telescope focus in the Configuration Monitor: Enter the value in Pedestal focus, **hit return**, and then hit Apply.  If you forget the return, it will do nothing. 
  - focus the guiders; this way you can use the guider images to monitor focus drifts
 
@@ -259 +260 @@
 See [wiki:MayallZbandLegacy/NotesforObservers/MosBot]
 
+Note that if you need to escape the script at some point during the night (see below), you will need to CTRL-C to stop mosbot.py and **restart** it when you are ready to start up again.  If you forget this, you will be observing tiles that you already observed earlier in the night.
+
 6. From the observer@mayall-3 xterm window, start taking exposures using the top-level observing script (tonight.sh):
 {{{
@@ -277 +280 @@
 See [wiki:MayallZbandLegacy/NotesforObservers/Copilot]
 
-8. Monitor focus by checking the image quality on each frame. Keep track of the truss temperature variation and modify  the focus as needed. The Mayall has astigmatism, so one can tell from the shape of the images which way to move the focus.  To stop and do a focus sequence:
+8. Monitor focus by checking the image quality on each frame. Keep track of the truss temperature variation and use the information to modify  the focus as needed. Note that the focus may not respond quickly to changes in temperature, so monitor the images carefully before adjusting focus.  The Mayall has astigmatism, so one can sometimes tell from the shape of the images which way to move the focus.  To stop and do a focus sequence:
 - Create a file to tell obsbot to quit
 {{{
@@ -285 +288 @@
 - Run a focus sequence (DESCRIBE THIS)
   - [wiki:MayallZbandLegacy/NotesforObservers/FocusInfo Example of a focus sequence]
-- Re-start the observing as described above.  *IMPORTANT* make sure to re-run `mosbot.py` so that you don’t repeat exposures from the beginning of the night!
+- Re-start the observing as described above.  **IMPORTANT** make sure to re-run `mosbot.py` so that you don’t repeat exposures from the beginning of the night!
 
 Keep an eye on the CCD and dewar temps (should be around 173C and 90C respectively)