Changes between Version 40 and Version 41 of PublicPages/MayallZbandLegacy/NotesforObservers

Timestamp:

Jan 7, 2016 7:49:19 PM (9 years ago)

Author:

Arjun Dey

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers

@@ -212 +212 @@
 Keep an eye on the CCD and dewar temps (should be around 173C and 90C respectively)
 
-=== Please write human logs ===
+=== Checking the Sky Brightness, Seeing and Transparency  ===
+
+The observing strategy files take as input these environmental conditions for
+setting the exposure times to achieve the required MzLS survey depth.
+
+From an IDL prompt, use the MOSSTAT routine to analyze the latest image on disk:
+{{{
+   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'
+}}}
+The full documentation can be seen with:
+{{{
+   IDL> doc_library,'mosstat'
+}}}
+
+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 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 ===
 
 '''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3'''
@@ -251 +278 @@
      nocs fullstatus ccp
 and make sure everything is shut down. Only when this is done, is it safe for the OAs to put on the lights in the dome. 
+
 
 === Check in the updated tile file ===