Changes between Version 40 and Version 41 of PublicPages/MayallZbandLegacy/NotesforObservers/Problems


Ignore:
Timestamp:
Feb 10, 2016 11:25:52 PM (9 years ago)
Author:
Knut Olsen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PublicPages/MayallZbandLegacy/NotesforObservers/Problems

    v40 v41  
    176176vignetting the telescope if observing to airmasses larger than 2.
    177177
    178 '''Fix 2:''' If accounting for the wind does not fix the problem, it may be related to an issue of telescope tracking, as was the case in February 8-9 2016.  You can try a test of moving to a different part of the sky and taking a 60-second exposure.  If the stars are round, but are elongated when you move back to the field, there may not be much you can do other than report the problem and continuing to observe.
     178'''Fix 2:''' If accounting for the wind does not fix the problem, it may be related to an issue of telescope tracking, as was the case in February 8-9 2016.  You can try a test of moving to a different part of the sky and taking a 60-second exposure.  If the stars are round, but are elongated when you move back to the field, there may not be much you can do other than report the problem and continuing to observe.  The problem seen in February 8-9 2016 was traced to the RA axis encoder tape.  Shelby Gott cleaned the tape, which fixed the problem.
    179179
    180180=== 8. Bad telescope pointing ===
     
    201201will print out a summary of all the frames from 10001 to the present in a nice tabular form (widen the window).  This is useful for checking how the seeing and sky brightness have varied since frame 10001, and whether  one should create and upload a new JSON observing script. The /noprint just prevents the decstat output for every frame; if you want to see that, then don't use the /noprint keyword.
    202202
    203