| 100 | | '''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. |
| 101 | | The images will also appear to have very large and strangely-shaped PSFs. |
| 102 | | |
| 103 | | [[Image(4MAPS_gui.tiff, 400px)]] |
| 104 | | [[Image(4MAPS_OFF_AIR.tiff, 400px)]] |
| 105 | | |
| 106 | | '''Frequency:''' This happened several times per night in the Dec 2015 run, but with reduced frequency in the early Feb 2016 run. |
| 107 | | |
| 108 | | '''Fix:''' |
| 109 | | - Stop the observing script with cntrl-C |
| 110 | | - Wait for it to finish and for “DONE” to appear on the NMSL GUI |
| 111 | | - 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 |
| 112 | | - Tell the OA they can move the telescope to zenith and reset 4MAPS |
| 113 | | - 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/obstatus/bad_expid.txt |
| 114 | | - Once the OA has reset 4MAPS, re-start the observing script |
| | 100 | 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. The images will also appear to have very large and strangely-shaped PSFs.[[BR]] |
| | 101 | [[Image(4MAPS_gui.tiff, 400px)]] [[Image(4MAPS_OFF_AIR.tiff, 400px)]] |
| | 102 | Frequency:: This happened several times per night in the Dec 2015 run, but with reduced frequency in the early Feb 2016 run. |
| | 103 | Fix:: |
| | 104 | - Stop the observing script with cntrl-C |
| | 105 | - Wait for it to finish and for “DONE” to appear on the NMSL GUI |
| | 106 | - 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 |
| | 107 | - Tell the OA they can move the telescope to zenith and reset 4MAPS |
| | 108 | - 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/obstatus/bad_expid.txt |
| | 109 | - Once the OA has reset 4MAPS, re-start the observing script |
| 118 | | '''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. |
| 119 | | The readout system detects when this happens, adds a set of PIXCNT* cards in the image header, and a red line shows up on the obsbot/copilot strip chart. |
| 120 | | Every 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 watching |
| 121 | | the copilot plots (for points with vertical red lines in the seeing plot), looking for the ERROR messages on the mosstat output, or just doing |
| 122 | | {{{ |
| | 113 | 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. The readout system detects when this happens, adds a set of PIXCNT* cards in the image header, and a red line shows up on the obsbot/copilot strip chart. Every 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 watching the copilot plots (for points with vertical red lines in the seeing plot), looking for the ERROR messages on the mosstat output, or just doing |
| | 114 | {{{ |
| 124 | | }}} |
| 125 | | in the IRAF window. |
| 126 | | |
| 127 | | [[Image(imageshift.png,400)]] |
| 128 | | |
| 129 | | '''Frequency:''' A couple of times per night in the early Feb 2016 run. |
| 130 | | |
| 131 | | '''Fix:''' |
| 132 | | - Don't stop taking data. This one exposure will be bad, but it should recover on its own |
| 133 | | - Add this as a bad exposure in the file ~products/mosaic3/obstatus/bad_expid.txt |
| 134 | | - And add a note to the logs |
| | 116 | }}} |
| | 117 | in the IRAF window.[[BR]] |
| | 118 | [[Image(imageshift.png,400)]] |
| | 119 | Frequency:: A couple of times per night in the early Feb 2016 run. |
| | 120 | Fix:: |
| | 121 | - Don't stop taking data. This one exposure will be bad, but it should recover on its own |
| | 122 | - Add this as a bad exposure in the file ~products/mosaic3/obstatus/bad_expid.txt |
| | 123 | - And add a note to the logs |
| 138 | | '''Symptom:''' The image data is an exact duplicate of a previous image, usually the one from 6 images prior. |
| 139 | | The headers are not duplicated, only the data, although the READTIME card will be the same to all decimal places |
| 140 | | to the preceding image. |
| 141 | | |
| 142 | | You can see whether images are repeating by typing the following command into the IRAF cl window: |
| 143 | | {{{ |
| | 127 | Symptom:: The image data is an exact duplicate of a previous image, usually the one from 6 images prior. The headers are not duplicated, only the data, although the READTIME card will be the same to all decimal places to the preceding image. You can see whether images are repeating by typing the following command into the IRAF cl window: |
| | 128 | {{{ |
| 145 | | }}} |
| 146 | | and look at the "readtime" column. If the numbers are the same in all decimal places and repeating, then the images |
| 147 | | are repeats. You will have to stop taking data and restart the system. |
| 148 | | |
| 149 | | '''Frequency:''' Several times per night during the early Feb 2016 run, but should be less often now. |
| 150 | | |
| 151 | | '''Fix:''' |
| 152 | | - If you are running a mosbot script, stop it by going to the directory in which the script is running (~/exec/mosbot/) and |
| 153 | | type "touch quit" and then wait for the script to end. |
| 154 | | - use the MOSAIC startup GUI and Stop MOSAIC |
| 155 | | - In a NOCS xterm window, type: |
| 156 | | {{{ |
| 157 | | nocs nuke pana |
| 158 | | nocs nuke dhs |
| 159 | | }}} |
| 160 | | - Start MOSAIC (from the startup GUI) |
| 161 | | - Take a zero frame and make sure all the amps are OK and have reasonable noise levels using "mscstat" |
| 162 | | - Re-start the observing script |
| 163 | | - List as bad exposures in the file ~products/mosaic3/obstatus/bad_expid.txt |
| 164 | | |
| | 130 | }}} |
| | 131 | and look at the "readtime" column. If the numbers are the same in all decimal places and repeating, then the images are repeats. You will have to stop taking data and restart the system. |
| | 132 | Frequency:: Several times per night during the early Feb 2016 run, but should be less often now. |
| | 133 | Fix:: |
| | 134 | - If you are running a mosbot script, stop it by going to the directory in which the script is running (~/exec/mosbot/) and type "touch quit" and then wait for the script to end. |
| | 135 | - use the MOSAIC startup GUI and Stop MOSAIC |
| | 136 | - In a NOCS xterm window, type: |
| | 137 | {{{ |
| | 138 | nocs nuke pana |
| | 139 | nocs nuke dhs |
| | 140 | }}} |
| | 141 | - Start MOSAIC (from the startup GUI) |
| | 142 | - Take a zero frame and make sure all the amps are OK and have reasonable noise levels using "mscstat" |
| | 143 | - Re-start the observing script |
| | 144 | - List as bad exposures in the file ~products/mosaic3/obstatus/bad_expid.txt |
