Changes between Version 189 and Version 190 of PublicPages/MayallZbandLegacy/NotesforObservers


Ignore:
Timestamp:
Feb 7, 2017 1:20:56 PM (8 years ago)
Author:
Dustin Lang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PublicPages/MayallZbandLegacy/NotesforObservers

    v189 v190  
    1010Additional Notes:
    1111
    12  * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/Copilot copilot]
     12 * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/Copilot Copilot]
     13 * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/MosBot Mosbot]
    1314 * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/Domeflats Dome flats]
    1415 * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/MOSAICGUI_Notes MOSAIC GUI Notes]
    15  * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/MosBot mosbot]
    1616 * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/Problems Problems]
    1717 * [wiki:PublicPages/MayallZbandLegacy/NotesforObservers/Safety Safety]
    … …  
    7575
    7676Other directories in the home directory are:
    77    '''astrometry/, legacypipe, obsbot, tractor, wcslib''' -- Python code for running copilot [[BR]]
     77   '''astrometry, legacypipe, obsbot, tractor, wcslib''' -- Python code for running copilot & mosbot [[BR]]
    7878   '''data/''' -- Link to the top-level data directory, where each night is stored in subdirectories like "20151213" [[BR]]
    7979   '''exec/''' -- Cross-mount to mosaic.kpno.noao.edu:/home/observer/exec [[BR]]
    … …  
    108108The tiles are broken into three passes. Each pass, pass1, pass2, and pass3, covers the basic footprint and each is offset optimally from the others. The tile are thus now fixed or defined on the sky for the duration of the survey. By definition:
    109109
    110 **pass1** is the high quality, photometric coverage. To the greatest extent possible, we want to ensure pass one tiles are the best. As such, pass1 should be executed on photometric nights with good seeing (< 1.3"). The observer should not start pass1 if its a not a true photometric night or if 3-4 hour contiguous blocks are not stable and clear. The robot observing program will choose pass1 for seeing < 1.25", transparency > 90% and sky brightness not worse than 0.25 mag brighter than the fiducial. But the observer should really be setting pass1 based on whether its a very stable photometric night from beginning to end. Forcing the pass is described here: [wiki:MayallZbandLegacy/NotesforObservers/MosBot#ToRestricttoPass2andor3 ForcePass]
     110**pass1** is the high quality, photometric coverage. To the greatest extent possible, we want to ensure pass one tiles are the best. As such, pass1 should be executed on photometric nights with good seeing (< 1.3"). The observer should not start pass1 if it is not a true photometric night or if 3-4 hour contiguous blocks are not stable and clear. The robot observing program will choose pass1 for seeing < 1.25", transparency > 90% and sky brightness not worse than 0.25 mag brighter than the fiducial. But the observer should really be setting forcepass1 based on whether its a very stable photometric night from beginning to end. Forcing the pass is described here: [wiki:MayallZbandLegacy/NotesforObservers/MosBot#UseTheForce Use The Force]
    111111
    112112**pass2** is the next best pass. Seeing should be < 1.3" or the weather is photometric (but seeing worse than 1.3"). Pass2 and 3 may alternate throughout a given night and the mosbot observing robot will do this automatically based on seeing, transparency, and sky brightness. Pass2 could also be done if no pass1 tiles are available. The robot will stick with pass2 when conditions are a little worse than this. Specifically seeing < 2" and trans > 70%. Observers can force pass3 if they think the conditions are poor, even though the robot might say pass2. This is especially encouraged if conditions are variable on short timescales and the robot is moving frequently between pass2 and pass3.
    … …  
    120120}}}
    121121
    122 If you want to use only pass2 or pass3 on a given night (because, say, there is high cirrus and you are sure the night will not be photometric), then create a file called "nopass1" (by typing "touch nopass1") in the ~/exec/mosbot directory. This will restrict mosbot to choose only between passes 2 and 3.
    123 
    124122
    125123== READ THIS IN PREP FOR OBSERVING ==
    126124
    127  * [wiki:MayallZbandLegacy/NotesforObservers/MosBot  mosbot notes]
    128  * [wiki:MayallZbandLegacy/NotesforObservers/Copilot  copilot notes]
     125 * [wiki:MayallZbandLegacy/NotesforObservers/MosBot  Mosbot notes]
     126 * [wiki:MayallZbandLegacy/NotesforObservers/Copilot Copilot notes]
    129127
    130128== AFTERNOON DOMEFLATS ==
    … …  
    288286       }}}
    289287       At the end of the night, you should check the updated tile file into the svn repository.
    290     a. In a second terminal on the VNC tart the automated script for monitoring the data quality
     288    a. In a second terminal on the VNC start the automated script for monitoring the data quality
    291289       {{{
    292290> idl
    … …  
    347345python mosbot.py pass1.json pass2.json pass3.json
    348346    }}}
    349     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).'''
    350     * 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:
     347    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).'''
     348    * If the conditions look marginal, and you only want to run with pass3, say, create an empty `forcepass3` file in the `~/exec/mosbot/` directory:
    351349      {{{
    352 cd ~/exec/mosbot
    353 touch forcepass3
     350rm ~/exec/mosbot/forcepass?
     351touch ~/exec/mosbot/forcepass3
    354352      }}}
    355353    * If you want to allow only pass 2, then use:
    356354      {{{
    357 cd ~/exec/mosbot
    358 touch forcepass2
     355rm ~/exec/mosbot/forcepass?
     356touch ~/exec/mosbot/forcepass2
    359357      }}}
    360358    * If you want to allow only pass 1, then use:
    361359      {{{
    362 cd ~/exec/mosbot
    363 touch forcepass1
     360rm ~/exec/mosbot/forcepass?
     361touch ~/exec/mosbot/forcepass1
    364362      }}}
    365       (though pass1 should not have to be forced if conditions are good!)
    366363    * If you want to allow only pass 2 and pass 3, then use:
    367364      {{{
    368 cd ~/exec/mosbot
    369 touch nopass1
     365rm ~/exec/mosbot/forcepass?
     366touch ~/exec/mosbot/nopass1
    370367      }}}
    371368      Mosbot checks for these files in the order: `forcepass 1,2,3` then `nopass1`.
    372     * Force files are not removed by `tonight.sh` or `mosbot.py`, so remove them manually to revert or change mosbot's behavior.
     369    * Force files are removed by `mosbot.py` on startup, so you will need to re-create those files if you restart the Mosbot.
    373370    * For more options with mosbot, see [wiki:MayallZbandLegacy/NotesforObservers/MosBot]
    374     * 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.
     371    * Note that if you need to stop 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.
    375372 1. From the observer@mosaic3 xterm window, start taking exposures using the top-level observing script (tonight.sh):
    376373    {{{
    … …  
    378375./tonight.sh
    379376    }}}
    380  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:
     377 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:
    381378    {{{
    382379cd ~/obsbot
    383380python copilot.py
    384381    }}}
    385     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]
     382    Whenever a new image is detected in the data directory (as defined by `$MOS3_DATA`), a new image is generated as `~/obsbot/recent.png`.
    386383 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:
    387384    - Create a file to tell tonight.sh to quit. On mosaic3:
    … …  
    393390    - Run a focus sequence (see link below for instructions).
    394391      - [wiki:MayallZbandLegacy/NotesforObservers/FocusInfo Example of a focus sequence]
    395     - 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!
     392    - 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!
    396393 1. If one wants to know where on the footprint the images being taken are, in real time:
    397394    {{{
    … …  
    409406==== Checking the Sky Brightness, Seeing and Transparency  ====
    410407
    411 The "copilot" python script and mosstat should already be running in a VNC.
     408The Copilot and mosstat programs should already be running in a VNC.
    412409If they are not, you can launch xterms, login to the mayall-idl computer as mzls,
    413410and run these individually.