Changes between Version 221 and Version 222 of PublicPages/MayallZbandLegacy/NotesforObservers

Timestamp:

Jan 6, 2018 2:54:54 AM (6 years ago)

Author:

Jeffrey A. Newman

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers

@@ -217 +217 @@
 
 === 3b If you are Observing in the 2017B semester: === 
-The json files that are generated by the strategy code (mstrategy) will require a very large slew near the end of the night (~09:40ut = 02:40am) which will take you from the west end of the DESI North Galactic Cap footprint to its eastern end. The problem with this is that the system times out during the long slew, and this causes it to crash. 
+The json files that are generated by the strategy code (mstrategy) will require a very large slew near the end of the night (~09:40ut = 02:40am) which will take you from the west end of the DESI North Galactic Cap footprint to its eastern end. The problem with this is that the system times out during the long slew, and this causes it to crash.  **Note: This has also happened on occasion in 2018.**
 
 The procedure until further notice is to break each new json file that is created in the ~mzls/obsbot/ directory into two parts at the point of this large slew. (This will not be necessary if MzLS is scheduled for a first-half night, since you will be stopping observing at ~00:30am, but it will be an issue for all full nights.) 
@@ -275 +275 @@
 
 Check that all is well by taking a test zero exposure. 
-On the IRAF window, check the image statistics by cd-ing to the correct directory and typing "mscstat <filename>"
+
+To do this, in a nocs window (an xterm connected to observer@mosaic3) do:
+{{{
+cd ~/exec/MzLS
+./ZERO1_MzLS.sh
+}}}
+
+After the image is done, on the IRAF window, check the image statistics by cd-ing to the correct directory (e.g., /data/observer/20180105 for data from Jan. 5 2018) and typing "mscstat <filename>"
 All rms values should be about 4-6 adu/pix; the exceptions are amplifier [6] or [14] which can have an rms~8-10 adu/pix. 
 If any one amplifier shows very high noise, then execute the following commands in a nocs window: