Changes between Version 13 and Version 14 of PublicPages/MayallZbandLegacy/NotesforObservers/Problems

Timestamp:

Feb 5, 2016 2:03:36 PM (9 years ago)

Author:

David Schlegel

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers/Problems

@@ -5 +5 @@
 === 1. Count-down timer counting negative and no new images read ===
 
-'''Sympton''': Count-down timer keeps counting down negative numbers, and no new images are read.
+'''Symptom''': Count-down timer keeps counting down negative numbers, and no new images are read.
 
 '''Frequency''': Several times per night in the early Feb 2016 run.
@@ -36 +36 @@
 '''Fix:'''
 - Type Control-C to exit out of the observing script
-- wait for it to finish and for “DONE” to appear on the NMSL gui
-- type “ditscmd nohs nohs_endobs” in the xterm window in which the script was stopped. This should readout the last image and display it on the real-time display ximtool window
+- Wait for it to finish and for “DONE” to appear on the NMSL GUI
+- Type “ditscmd nohs nohs_endobs” in the xterm window in which the script was stopped. This should readout the last image and display it on the real-time display ximtool window
 - Tell the OA they can move the telescope to zenith and reset 4MAPS
 - Check the last image taken when 4MAPS failure occurred - the image quality is probably bad.  Add this as a bad exposure in the file ~products/mosaic3/logs/bad_expid.txt
-- Create a new observing script.
-- Once the OA has reset 4MAPS, start the new script.
+- Create a new observing script
+- Once the OA has reset 4MAPS, start the new script
 
 === 4. Shifted images ===
 
+'''Symptom:''' Sub-blocks of an image have been shifted in the readout, and is obvious on the display as the overscan region being in a different place.
+The readout system detects when this happens, adds a set of PIXCNT* cards in the image header, and a red line shows up on the obsbot/copilot strip chart.
 Every now and then, an image appears which shows a shifted region in one or more CCDs. Please log this. You can identify images with shifts by running 
 
-{{{
-grep pixCnt mos3*dat | grep 1783
-}}}
+'''Frequency:''' A couple of times per night in the early Feb 2016 run.
 
-This results in all the files that may have shifts. Please examine them by displaying them using mscdisplay, examining the full image, identifying the CCDs which have shifts and logging the file numbers / exposure numbers
-Images with pixel shifts are now marked on the obsbot/copilot display
+'''Fix:''' 
+- Add this as a bad exposure in the file ~products/mosaic3/logs/bad_expid.txt
 
 === 5. Repeat images ===