Changes between Version 12 and Version 13 of PublicPages/MayallZbandLegacy/NotesforObservers/Copilot


Ignore:
Timestamp:
Feb 25, 2016 4:28:14 PM (9 years ago)
Author:
Dustin Lang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PublicPages/MayallZbandLegacy/NotesforObservers/Copilot

    v12 v13  
    99cd ~/obsbot
    1010python copilot.py &
    11 eog recent.png &
    1211}}}
    1312
    1413It will monitor the $MOS3_DATA directory, and whenever a new image
    1514comes it, it will measure it, update a little database, and create a
    16 "strip plot" showing the conditions.
     15"strip plot" showing the conditions.  The plot should be shown in a python plot window.
     16The plot is also saved to the file "recent.png"; you could for example view it using
     17{{{
     18eog recent.png &
     19}}}
    1720
    18 The database is in `~/obsbot/obsdb/obsdb.sqlite3`.
     21When a focus sequence is taken, it will run an analysis on the image and show another plot (also saved as focus.png).
     22
     23The database is in `~/obsbot/obsdb/mosaic3.sqlite3` for MzLS.
    1924
    2025
     
    2631*  --extnum=EXTNUM       Integer extension to read
    2732*  --rawdata=RAWDATA     Directory to monitor for new images: default $MOS3_DATA if set, else "rawdata"
    28 *  --portion=PORTION     Portion of the night: default 1.0
    2933*  --n-fwhm=N_FWHM       Number of stars on which to measure FWHM
    3034*  --no-db               Do not append results to database
     
    5963the exposure number of the bad frame both in the observing logs and in the bad_expid.txt file.
    6064
    61 * Vertical red line in top panel accompanied by "readtime" error message
    62 
    63 This is harmless in general and can be ignored. However, many sequential appearances
    64 of the readtime error mean that the camera may not be writing new images (as in the first
    65 case above). In this event, one has to stop observing and restart NOCS.
    66 
    6765* Variations in transparency / seeing
    6866
     
    7674The top panel shows the seeing.  Any problems with the data we know
    7775how to detect are marked with red vertical bands.  These include:
    78 * readtime -- MAY indicate a duplicated image ("md5sum" is a better
    79   indicator). ALSO, typing "hselect mos3*fits[0] $I,readtime yes" in the IRAF window can show you the
    80   readtime header jkeyword values for the images. If the last several are ''identical'', then this requires
    81   action.
    8276* md5sum -- this image contains identical pixels as a previous image.
    8377  This requires action!  Please see the problem description [[https://desi.lbl.gov/trac/wiki/PublicPages/MayallZbandLegacy/NotesforObservers/Problems#a5.Repeatimages HERE]].
     
    117111
    118112
    119 Note that zeros and focus frames will not show up on the plot.
     113Note that zeros will not show up on the plot.  The times of focus frames will be marked with a black dot labelled "F".
    120114
    121115
     
    131125{{{
    132126python obsdb/manage.py flush
     127python obsdb/manage.py migrate
    133128}}}
    134129