Changes between Version 12 and Version 13 of PublicPages/MayallZbandLegacy/NotesforObservers/Problems
- Timestamp:
- Feb 5, 2016 1:55:35 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PublicPages/MayallZbandLegacy/NotesforObservers/Problems
v12 v13 5 5 === 1. Count-down timer counting negative and no new images read === 6 6 7 ''' Problem:''': Count-down timer keeps counting down negative numbers, and no new images are read.7 '''Sympton''': Count-down timer keeps counting down negative numbers, and no new images are read. 8 8 9 9 '''Frequency''': Several times per night in the early Feb 2016 run. 10 10 11 '''Fix:''' 11 '''Fix:''' Arjun types magic things. 12 12 13 13 === 2. Images show bad amp === 14 14 15 This is usually diagnosed by an amp appearing “dead”, having very large noise (mscstat results in rms > ~ 1000 adu/pix). 15 '''Symptom: One amp has extremely large noise, looks awful the display of the image with "mcsdisplay" with a noise > 1000 ADU/pix from the "mscstat" command. 16 16 17 Can be usually fixed by typing the following in a NOCS xterm window: 17 '''Frequency:''' Several times in Dec 2015 run, never in early Feb 2016 run. 18 19 '''Fix:''' Reset the NOCS controller by typing the following in a NOCS xterm window: 18 20 {{{ 19 -nocs reset ccp20 -nocs init ccp21 nocs reset ccp 22 nocs init ccp 21 23 }}} 22 Then take two zero images. The first image is always bad. The second should be ok. Check it using mscstat <filename> once it has read out. All rms values should be between 4-7 adu (except for amps 6 and 14, which may be ~8-10). 24 Then take two zero images. The first image is always bad. The second should be OK. 25 Check it using "mscstat <filename>" once it has read out. All rms values should be between 4-7 ADU except for amp 6 with will be 8-10 ADU. 23 26 24 === 3. 4MAPS system goes “OFF AIR” during observing === 27 === 3. 4MAPS primary mirror support goes “OFF AIR” during observing === 28 29 '''Symptom:''' The OA should notice when this happens, but you can also see if the mirror support is listed as "OFF AIR" on the 4MAPS GUI. 30 The images will also appear to have very large and strangely-shaped PSFs. 25 31 26 32 [[Image(4MAPS_gui.tiff, 400px)]] 27 33 34 '''Frequency:''' This happened several times per night in the Dec 2015 run, but never in the early Feb 2016 run. 28 35 29 OA should notice this, but you can keep track of the mirror support system on the 4MAPS gui. If it says “OFF AIR”, the mirror is off air! 30 31 32 33 34 - Check the last image taken when 4MAPS failure occurred - the image quality is probably bad. Log the image file / exposure number 35 - Edit the mzls*sh script. This is a bit complicated, since you need to keep the first 8 lines of the script, and then delete everything up to the point where you stopped. The image number at which you stopped is probably displayed in the NMSL gui. Let’s say the last image was No. 14. You may want to repeat this image, if the image quality was bad due to the 4MAPS failure. So delete all lines for image exposures No. 1 to No. 13, but be careful that you retain the telescope positioning command in the script that occurs just before the line ==== No. 14 ==== . 36 - Once the OA has reset 4MAPS, you can restart the script. The telescope will slew to your position and start the exposure.36 '''Fix:''' 37 - Type Control-C to exit out of the observing script 38 - wait for it to finish and for “DONE” to appear on the NMSL gui 39 - 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 40 - Tell the OA they can move the telescope to zenith and reset 4MAPS 41 - 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 42 - Create a new observing script. 43 - Once the OA has reset 4MAPS, start the new script. 37 44 38 45 === 4. Shifted images ===