Changes between Version 186 and Version 187 of PublicPages/MayallZbandLegacy/NotesforObservers

Timestamp:

Feb 4, 2017 6:24:53 PM (8 years ago)

Author:

Benjamin Alan Weaver

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers

@@ -340 +340 @@
 === 10 Observe - all night long! ===
 
-1. From the mzls@mayall-idl window, generate the top-level observing script (tonight.sh) assuming that we have three plan files named pass1.json, etc.
-{{{
-   cd ~/obsbot
-   python mosbot.py pass1.json pass2.json pass3.json
-}}}
-This will start the [wiki:MayallZbandLegacy/NotesforObservers/MosBot mosbot] script, which will watch the $MOS3_DATA directory for new images, analyze them, and update FUTURE exposure scripts, choosing the pass number and setting the exposure time.
-
-'''The exposure script behavior can be modified by creating or removing various files in the 
-exec/mosbot/ directory on mosaic3 (nocs xterm).'''
-
-If the conditions look marginal, and you only want to run with pass3, say, just create an empty "forcepass3" file in the `~/exec/mosbot/` directory:
-{{{
-   cd ~/exec/mosbot
-   touch forcepass3
-}}}
-
-If you want to allow only pass 2, then use: 
-{{{
-   cd ~/exec/mosbot
-   touch forcepass2
-}}}
-
-If you want to allow only pass 1, then use: 
-{{{
-   cd ~/exec/mosbot
-   touch forcepass1
-}}}
-(though pass1 should not have to be forced if conditions are good!)
-
-If you want to allow only pass 2 and pass 3, then use: 
-{{{
-   cd ~/exec/mosbot
-   touch nopass1
-}}}
-
-Mosbot checks for these files in the order: `forcepass 1,2,3` then `nopass1`.
-
-**Force files are not removed by `tonight.sh` or `mosbot.py`, so remove them manually to revert or change mosbot's behavior. **
-
-For more options with mosbot, 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.
-
-2. From the observer@mosaic3 xterm window, start taking exposures using the top-level observing script (tonight.sh):
-{{{
-   cd ~/exec/mosbot
-   ./tonight.sh
-}}}
-
-3. [wiki:MayallZbandLegacy/NotesforObservers/Copilot "copilot"] should already be running. If not, start running "copilot" in the mayall-idl VNC window. Copilot keeps a beautiful running plot of observing conditions.  From any mzls@mayall-idl window:
-{{{
-   cd ~/obsbot
-   python copilot.py
-}}}
-
-Whenever a new image is detected in the data directory (as defined by $MOS3_DATA), a new image is generated as `~/obsbot/recent.png`.
-
-See [wiki:MayallZbandLegacy/NotesforObservers/Copilot]
-
-4. Monitor focus by checking the image quality on each frame or keeping an eye on the mosstat PSF display. 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 tonight.sh to quit. On mosaic3:
-{{{
-   touch ~/exec/mosbot/quit
-}}}
-- Wait for the current exposure to complete (at which point the above file is automatically removed). 
-- CTRL-C the mosbot.py session on mayall-idl.
-- Run a focus sequence (see link below for instructions).
-  - [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!
-
-5. If one wants to know where on the footprint the images being taken are, in real time:
-{{{
-     mayall-idl> cd ~/obsbot
-     mayall-idl> eog radec.png &
-}}}
-which auto-update the display when the radec.png is overwritten.
-
-Keep an eye on the CCD and dewar temps (should be around 173K and 90K respectively)
-
-OK - you are off and running! Congratulations!!!
+==== Routine Observations ====
+
+ 1. From the mzls@mayall-idl window, generate the top-level observing script (tonight.sh) assuming that we have three plan files named pass1.json, etc.
+    {{{
+cd ~/obsbot
+python mosbot.py pass1.json pass2.json pass3.json
+    }}}
+    This will start the [wiki:MayallZbandLegacy/NotesforObservers/MosBot mosbot] script, which will watch the $MOS3_DATA directory for new images, analyze them, and update FUTURE exposure scripts, choosing the pass number and setting the exposure time. '''The exposure script behavior can be modified by creating or removing various files in the  exec/mosbot/ directory on mosaic3 (nocs xterm).'''
+    * If the conditions look marginal, and you only want to run with pass3, say, just create an empty "forcepass3" file in the `~/exec/mosbot/` directory:
+      {{{
+cd ~/exec/mosbot
+touch forcepass3
+      }}}
+    * If you want to allow only pass 2, then use: 
+      {{{
+cd ~/exec/mosbot
+touch forcepass2
+      }}}
+    * If you want to allow only pass 1, then use: 
+      {{{
+cd ~/exec/mosbot
+touch forcepass1
+      }}}
+      (though pass1 should not have to be forced if conditions are good!)
+    * If you want to allow only pass 2 and pass 3, then use: 
+      {{{
+cd ~/exec/mosbot
+touch nopass1
+      }}}
+      Mosbot checks for these files in the order: `forcepass 1,2,3` then `nopass1`.
+    * Force files are not removed by `tonight.sh` or `mosbot.py`, so remove them manually to revert or change mosbot's behavior.
+    * For more options with mosbot, 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.
+ 1. From the observer@mosaic3 xterm window, start taking exposures using the top-level observing script (tonight.sh):
+    {{{
+cd ~/exec/mosbot
+./tonight.sh
+    }}}
+ 1. [wiki:MayallZbandLegacy/NotesforObservers/Copilot "copilot"] should already be running. If not, start running "copilot" in the mayall-idl VNC window. Copilot keeps a beautiful running plot of observing conditions.  From any mzls@mayall-idl window:
+    {{{
+cd ~/obsbot
+python copilot.py
+    }}}
+    Whenever a new image is detected in the data directory (as defined by $MOS3_DATA), a new image is generated as `~/obsbot/recent.png`. See [wiki:MayallZbandLegacy/NotesforObservers/Copilot]
+ 1. Monitor focus by checking the image quality on each frame or keeping an eye on the mosstat PSF display. 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 tonight.sh to quit. On mosaic3:
+      {{{
+touch ~/exec/mosbot/quit
+      }}}
+    - Wait for the current exposure to complete (at which point the above file is automatically removed). 
+    - CTRL-C the mosbot.py session on mayall-idl.
+    - Run a focus sequence (see link below for instructions).
+      - [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!
+ 1. If one wants to know where on the footprint the images being taken are, in real time:
+    {{{
+mayall-idl> cd ~/obsbot
+mayall-idl> eog radec.png &
+    }}}
+    which auto-update the display when the radec.png is overwritten.
+ 1. Keep an eye on the CCD and dewar temps (should be around 173K and 90K respectively)
+ 1. OK - you are off and running! Congratulations!!!
 
 ==== If you have problems ... ====
@@ -433 +416 @@
 From an IDL prompt, use the MOSSTAT routine to analyze the latest image on disk:
 {{{
-   IDL> mosstat
+IDL> mosstat
 }}}
 There are keyword options that allow you to choose different exposure numbers or CCDs
 within that exposure.  For example, to analyze chip 'im16' of the exposure number 12345, type:
 {{{
-   IDL> mosstat, 12345, ext='im16'
+IDL> mosstat, 12345, ext='im16'
 }}}
 The full documentation can be seen with:
 {{{
-   IDL> doc_library,'mosstat'
+IDL> doc_library,'mosstat'
 }}}
 To just have mosstat run continuously whenever each image appears, use
 {{{
-   IDL> mosstat_continuous
+IDL> mosstat_continuous
 }}}
 
@@ -452 +435 @@
 ==== Please write useful human logs ====
 
-Keep a log about weather conditions, which pass you observed,
-and telescope problems.  Follow the example on the pages at [wiki:MayallZbandLegacy/ObservingLogs] .
+Keep a log about weather conditions, which pass you observed, and telescope problems.  Follow the example on the pages at [wiki:MayallZbandLegacy/ObservingLogs] .
 
 Catastrophically bad frames (such as saturated frames, or where the telescope moved) are recorded and svn-checked-in to