Changes between Version 63 and Version 64 of PublicPages/MayallZbandLegacy/NotesforObservers

Timestamp:

Feb 6, 2016 12:01:32 AM (8 years ago)

Author:

David Schlegel

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers

@@ -2 +2 @@
 
 '''Still need to incorporate the following instructions:'''
-  - '''Pointing the telescope, and re-zeroing the pointing using the numbers reported by MOSSTAT or obsbot'''
   - '''Running the guiding loop -- although we typically do not guide on the Mayall for these 1-2 min exposures'''
   - '''Coverage plots, which we've not yet ported from the DECam version'''
@@ -261 +260 @@
 }}}
 
-=== Correcting the pointing ===
-
-Keep an eye on the mosstat output. If the telescope pointing has gone off by more than about 30 arcsec (which happens!), then
-this routine will likely fail to match stars.  If this happens, the operator will need to recenter the telescope. One can do this by
-telling the OA to offset the telescope in the *OPPOSITE* direction of the computed mosstat positional offsets, i.e., if you see: 
-   RA, Dec offsets: -15.230 14.756
-ask the OA to offset the telescope +15" in RA (i.e., east) and -15" in DEC (i.e., south) and zero the coordinates there. Only 
-apply these offsets when the exposure is done (i.e., during readout) and when the telescope is not moving!
-
-One can also check the observing progress using the almanac command: 
-  IDL> almanac, 10001, /noprint
-will print out a summary of all the frames from 10001 to the present in a nice tabular form (widen the window).  This is useful for checking how the seeing and sky brightness have varied since frame 10001, and whether  one should create and upload a new JSON observing script. The /noprint just prevents the decstat output for every frame; if you want to see that, then don't use the /noprint keyword. 
-
 
 === Please write useful human logs ===