Changes between Version 64 and Version 65 of PublicPages/MayallZbandLegacy/NotesforObservers/Problems
- Timestamp:
- Jan 30, 2017 1:57:47 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PublicPages/MayallZbandLegacy/NotesforObservers/Problems
v64 v65 3 3 [[PageOutline]] 4 4 5 == = 0. No images being written ===5 == 0. No images being written == 6 6 7 7 '''Symptom''': No new images are showing up on disk or in the obsbot display, and the real time display does not update. The control system and readout timer, … … 33 33 - restart the observing script by following the instructions here 34 34 35 == = 1. Images appear on the real time display, but are not written immediately to the data directory ===35 == 1. Images appear on the real time display, but are not written immediately to the data directory == 36 36 37 37 '''Symptom''': The real time display shows updated images, but files are very slow to appear in the data directory. The MOSSTAT and copilot displays are slow to update; copilot may eventually flag the image with a "readtime" failure. … … 50 50 51 51 52 == = 2. Detector timeouts ===52 == 2. Detector timeouts == 53 53 54 54 '''Symptom''': Count-down timer in NMSL GUI turns red keeps counting down negative numbers (to -105 or so), or hangs during exposure, and no new images are read. … … 111 111 Take a zero image, make sure it reads out, and check image by running "mscstat" If the zero image looks ok, you can restart the observing script. 112 112 113 == = 3. Images show bad amp ===113 == 3. Images show bad amp == 114 114 115 115 '''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. … … 128 128 - Re-start the observing script 129 129 130 == = 4. 4MAPS primary mirror support goes “OFF AIR” during observing ===130 == 4. 4MAPS primary mirror support goes “OFF AIR” during observing == 131 131 132 132 '''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. … … 146 146 - Once the OA has reset 4MAPS, re-start the observing script 147 147 148 == = 5. Shifted images ===148 == 5. Shifted images == 149 149 150 150 '''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. … … 166 166 - And add a note to the logs 167 167 168 == = 6. Repeat images ===168 == 6. Repeat images == 169 169 170 170 '''Symptom:''' The image data is an exact duplicate of a previous image, usually the one from 6 images prior. … … 196 196 197 197 198 == = 7. Focus drifting ===198 == 7. Focus drifting == 199 199 200 200 If you lose track of the focus and don’t know whether you are below or above the focus value, wait for the readout countdown to start … … 212 212 - Restart observing 213 213 214 == = 8. Images of stars on the guider are bouncing around ===214 == 8. Images of stars on the guider are bouncing around == 215 215 216 216 '''Symptoms:''' Guider images are visibly bouncing around on the TV guider image, and the seeing is poor, with the image extension being … … 225 225 '''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. 226 226 227 == = 9. Bad telescope pointing ===227 == 9. Bad telescope pointing == 228 228 229 229 '''Symptoms:''' The reported telescope offsets from the python "obsbot" or the IDL "mosstat" show … … 248 248 will 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. 249 249 250 == = 10. tonight.sh script stops for no apparent reason ===250 == 10. tonight.sh script stops for no apparent reason == 251 251 252 252 '''Symptoms:''' Things go idle and quiet. No exposures are being taken or read out, the telescope is not moving, and the software does not indicate any activity. The shell window where you are running tonight.sh returns to a prompt, and has no error message of any kind. … … 256 256 '''Fix:''' Re-run the mosbot -py command with the appropriate pass?.json files. Check that the tonight.sh script has been rebuilt anew. Start the new tonight.sh script. 257 257 258 == = 11. MOSSTAT or MUPTILES don't see data ===258 == 11. MOSSTAT or MUPTILES don't see data == 259 259 260 260 '''Symptoms:''' mosstat or muptiles can’t see the data as its being taken. … … 270 270 Note "dataX" is usually data2 or data3 and DATE is the UT Date of the morning on which we are observing. 271 271 272 == = 12. Semaphore Failure ===272 == 12. Semaphore Failure == 273 273 274 274 '''Symptoms:''' … … 290 290 - restart tonight.sh. 291 291 292 == = 13. Elongated images due to 4MAPS valve problems ===292 == 13. Elongated images due to 4MAPS valve problems == 293 293 294 294 '''Symptoms:''' … … 308 308 This can be done without moving the telescope, but you probably want to stop the mosbot script, since you don’t want the script to command the telescope to move while you are repressurizing the bag. 309 309 310 If this test does not work with the telescope in its current position, then the next step is to take the telescope to zenith and repeat the procedure. 310 If this test does not work with the telescope in its current position, then the next step is to take the telescope to zenith and repeat the procedure. 311 312 [[BackLinks]]
