Changes between Version 22 and Version 23 of PublicPages/MayallZbandLegacy/NotesforObservers/Copilot


Ignore:
Timestamp:
Feb 7, 2017 12:35:10 PM (8 years ago)
Author:
Dustin Lang
Comment:

--

Legend:

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

    v22 v23  
    8989* MISSING IMAGE -- it has been a while since the last image has been seen.  Have images stopped being written?  See problem description [[https://desi.lbl.gov/trac/wiki/PublicPages/MayallZbandLegacy/NotesforObservers/Problems#a0.Noimagesbeingwritten here]] 
    9090
    91 The second panel shows the Sky brightness.  The "nominal" brightness
    92 is shown by the magenta horizontal line.  In this panel, the pass
    93 number of previous exposures is shown.  (This corresponds to the pass
    94 we thought the image was going to be, not what the actual conditions
    95 delivered.)
     91The second panel shows the Sky brightness relative to a nominal value.
     92Larger values means the sky is darker than nominal.
     93This panel also shows the pass number of previous exposures.
     94This is the pass number of the tiles that were observed.
     95
     96(Note, this does *not* come from an assessment of how good the conditions were,
     97it comes from looking at what tile we chose to observe.  Note also that the "pass2.json" file
     98may contain tiles from pass 3, so even if you have set *forcepass2*, you may see pass 3 labels
     99in the copilot plot.)
    96100
    97101The "transparency" panel shows what fraction of the light from stars
    98 is getting through the atmosphere to us.  Around 90% usually indicates
     102is getting through the atmosphere to us.  Values above 90% usually indicate
    99103clear photometric conditions.
    100104
     
    107111is shown with a triangle, and a circle will also be plotted at the
    108112lower or upper bound line.  Triangles above the upper bound indicate
    109 images that might not be as deep as desired. **Sometimes a line is visible in this plot (e.g. see 10hr - 11hr above 250 sec). This is the predicted max exposure time to saturate (really to get to a "do not cross" number of counts) the background. This relates to safety of the detectors. If you notice real exposure times are getting close to this line, its time to stop tonight.sh and take stock. This most easily would happen with moon and clouds which make the background high.**
     113images that might not be as deep as desired. **Sometimes a line is visible in this plot (e.g. see 10hr - 11hr above 250 sec). This is the predicted exposure time to get 20,000 ADU from the sky background.
     114Mosbot will try to limit the exposure times to avoid exposing for too long, but if conditions are changing rapidly, it may not realize soon enough that the sky has become too bright.  The detectors can be damaged by too much light, so if you see this line, you should monitor the conditions very carefully!  You may need to stop tonight.sh and take stock.  This most easily happens with moon and clouds which make the background high.**
     115
     116The numbers on the exposure time panel are the "depth factor" of the images.  A value of "1.50" indicates that we exposed for 1.5 times as long as was necessary to achieve our target depth.  Note that the Mosbot does try to adapt its exposure times based on the depth achieved in other passes, so sometimes it may be shooting for depth values greater than 1.0.  And when exposure times are clipped up to 80 seconds, we expect the depth factor to be greater than 1.  Similarly, when exposure times are clipped down to 250 seconds, or to limit the sky background counts, then we expect the depth factor to be smaller than 1.
     117
    110118
    111119**[depth factor has been removed from the plot. This description is useful when looking at plots created before about February 2016]** The "depth factor" plot just shows our actual exposure time divided by
     
    122130== Notes ==
    123131
    124 At the moment, `copilot.py` just waits for new images to appear, but you can also tell it to process a set of images (eg, if it crashed and you want it to run the backlog) by specifying the files on the command line.  You can also tell it to skip files that already exist in the database via `--skip`, eg,
     132Normally, `copilot.py` just waits for new images to appear, but you can also tell it to process a set of images (eg, if it crashed and you want it to run the backlog) by specifying the files on the command line.  You can also tell it to skip files that already exist in the database via `--skip`, eg,
    125133{{{
    126134python copilot.py --skip $MOS3_DATA/mos3.*.fits