Changes between Version 9 and Version 10 of PublicPages/MayallZbandLegacy/NotesforObservers/Problems


Ignore:
Timestamp:
Feb 5, 2016 5:02:36 AM (8 years ago)
Author:
Arjun Dey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PublicPages/MayallZbandLegacy/NotesforObservers/Problems

    v9 v10  
    88
    99Can be usually fixed by typing the following in a NOCS xterm window:
     10{{{
    1011        - nocs reset ccp
    1112        - nocs init ccp
     13}}}
    1214Then 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).
    1315
    … …  
    3032Every 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
    3133
     34{{{
    3235grep pixCnt mos3*dat | grep 1783
     36}}}
    3337
    3438This 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
    35 
     39Images with pixel shifts are now marked on the obsbot/copilot display
    3640
    3741=== 4. Repeat images ===
    … …  
    4852        - Stop MOSAIC (from the startup gui)
    4953        - In a NOCS xterm window, type:
     54{{{
    5055                nocs nuke pana
    5156                nocs nuke dhs
     57}}}
    5258        - Start MOSAIC (from the startup gui)
    5359Once 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.