Changes between Version 17 and Version 18 of PublicPages/MayallZbandLegacy/NotesforObservers/Problems


Ignore:
Timestamp:
Feb 5, 2016 7:36:39 PM (9 years ago)
Author:
David Schlegel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PublicPages/MayallZbandLegacy/NotesforObservers/Problems

    v17 v18  
    1010
    1111'''Fix:'''
     12- Stop the observing script with cntrl-C
    1213- Restart the controllers
    1314{{{
    … …  
    1516       nocs nmsl reset
    1617}}}
    17 - Take a zero image, make sure it rads out, and check the image by running "mscstat"
    18 - Create and start a new observing script
     18- Take a zero image, make sure it reads out, and check the image by running "mscstat"
     19- Re-start the observing script
    1920
    2021
    … …  
    2526'''Frequency:''' Several times in Dec 2015 run, never in early Feb 2016 run.
    2627
    27 '''Fix:''' Reset the NOCS controller by typing the following in a NOCS xterm window:
     28'''Fix:'''
     29- Stop the observing script with cntrl-C
     30- Reset the NOCS controller by typing the following in a NOCS xterm window:
    2831{{{
    2932        nocs reset ccp
    3033        nocs init ccp
    3134}}}
    32 Then take two zero images. The first image is always bad. The second should be OK.
    33 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.
     35- Take two zero images. The first image is always bad. The second should be OK.
     36   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.
     37- Re-start the observing script
    3438
    3539=== 3. 4MAPS primary mirror support  goes “OFF AIR” during observing ===
    … …  
    4347
    4448'''Fix:'''
    45 - Type Control-C to exit out of the observing script
     49- Stop the observing script with cntrl-C
    4650- Wait for it to finish and for “DONE” to appear on the NMSL GUI
    4751- 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
    4852- Tell the OA they can move the telescope to zenith and reset 4MAPS
    4953- 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
    50 - Create a new observing script
    51 - Once the OA has reset 4MAPS, start the new script
     54- Once the OA has reset 4MAPS, re-start the observing script
    5255
    5356=== 4. Shifted images ===
    … …  
    5962'''Frequency:''' A couple of times per night in the early Feb 2016 run.
    6063
    61 '''Fix:'''
     64'''Fix:'''
     65- Don't stop taking data.  This one exposure will be bad, but it should recover on its own
    6266- Add this as a bad exposure in the file ~products/mosaic3/logs/bad_expid.txt
    6367
    6468=== 5. Repeat images ===
    6569
    66 This is very hard to diagnose, and requires you to pay attention to the obsbot/copilot output, the individual images, and occasionally running the command:
     70'''Symptom:''' The image data is an exact duplicate of a previous image, usually the one from 6 images prior.
     71The headers are not duplicated, only the data, although the READTIME card will be the same to all decimal places
     72to the preceding image.
    6773
    68 hselect mos3*fits[0] $I,READTIME yes
     74'''Frequency:''' Several times per night during the early Feb 2016 run, but should be less often now.
    6975
    70 in the IRAF window.
    71 
    72 If the READTIME values begin to repeat, this is a sign that new images are not being written out. Another clue is that the read out counter on the NMSL gui goes straight from 44 to 0. A third clue is that the MOSSTAT command is failing to find any stars in the image, even though the offsets were small when the sequence was started.
    73 
    74 If any of these are true, then it means that the images are just duplicates of previous images. You need to stop the sequence using CTRL-C in the window where the script is being exectuted, and restart everything:
    75         - Stop MOSAIC (from the startup gui)
    76         - In a NOCS xterm window, type:
     76'''Fix:'''
     77- In a NOCS xterm window, type:
    7778{{{
    7879                nocs nuke pana
    7980                nocs nuke dhs
    8081}}}
    81         - Start MOSAIC (from the startup gui)
    82 Once everything comes up and you have rearranged windows how you like, take a ZERO frame to make sure that the amps are all OK. Check the noise on the zero image using mscstat.
    83 If this is not OK, then see instructions for Problem 1.
    84 
    85 From here, it is best to make a new plan (strategy file) and start it up.
    86 
    87 Log all the images that had identical READTIME values.
     82- Start MOSAIC (from the startup GUI)
     83- Take a zero frame and make sure all the amps are OK and have reasonable noise levels using "mscstat"
     84- Re-start the observing script
     85- List as bad exposures in the file ~products/mosaic3/logs/bad_expid.txt
    8886
    8987
    … …  
    117115
    118116=== 7. Images of stars on the guider are bouncing around ===
    119         - If the wind is high, ask the OA to close the louvers
     117
     118'''Symptoms:''' Guider images are visibly bouncing around on the TV guider image, and the seeing is poor.
     119
     120'''Fix:''' If the wind is high, ask the OA to close the louvers that allow additional outside air to circulate into the dome.
     121If observing near zenith, the lower part of the dome slit can also be closed.  That lower part of the slit only starts
     122vignetting the telescope if observing to airmasses larger than 2.
     123