| 336 | | (a) create an OBJECT script with NGUI for 5 sec with the zd filter (do not create a TEST script, because MOSSTAT will ignore it) |
| 337 | | |
| 338 | | (b) Execute it, wait for it to readout completely, and make sure that it appears in your data directory; if it does not, use the "Update Status" button on the DHS GUI |
| 339 | | |
| 340 | | (c) Once the image is processed by copilot, the bottom panel on the copilot plot will print the pointing offsets. Give these offsets to the OA with '''opposite''' sign. That is, if copilot shows numbers (-15.3,+18.3), or if mosstat reads "RA,Dec offsets = -15.34, 18.32", then you need to provide the OA with the pointing offsets of +15,-18 to zero the telescope coordinates.[[BR]][[BR]] |
| 341 | | |
| 342 | | If this process does not work for some reason, then you can also zero the telescope coordinates by using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane; ''i.e.'' in the chip gaps). As before, when taking the image of the bright star, make sure to create an OBJECT script with NGUI (not a TEST, because MOSSTAT will ignore it), zd filter, 1 - 5 sec exposure. After centering the bright star, return to the first target field and use the above procedure to determine the pointing offsets - do not use the copilot or mosstat results based on the bright star image! Make sure you move back to the first MzLS tile position after you complete this test. [[BR]][[BR]] |
| 343 | | |
| 344 | | If mosstat or copilot fails, it could be because (a) the telescope is mis-pointed, (b) the telescope is out of focus (set the focus approx using the formula above and try again). [[BR]][[BR]] |
| 345 | | You can take another OBJECT frame if you want to check to make sure the offset went in the right direction. |
| 346 | | |
| 347 | | 2. Focus the Telescope:: |
| 348 | | - Create a focus script using the NGUI: exposure time 5 or 10 seconds, zd filter, -75 micron focus steps, click Midpoint to *on*, 9 exposures. NOTE: If observing in the 2017B semester, please make sure you are focusing at the sky location 270,+60. |
| 349 | | - run the focus script from the /home/observer/exec directory (./FOCUS.sh) |
| 350 | | - copilot will automatically analyze and report the best focus in the mayall-idl window. |
| 351 | | - or alternately, analyze the focus image using the IRAF script mscstarfocus |
| | 335 | a. create an OBJECT script with NGUI for 5 sec with the zd filter (do not create a TEST script, because MOSSTAT will ignore it) |
| | 336 | a. Execute it, wait for it to readout completely, and make sure that it appears in your data directory; if it does not, use the "Update Status" button on the DHS GUI |
| | 337 | a. Once the image is processed by copilot, the bottom panel on the copilot plot will print the pointing offsets. Give these offsets to the OA with '''opposite''' sign. That is, if copilot shows numbers (-15.3,+18.3), or if mosstat reads "RA,Dec offsets = -15.34, 18.32", then you need to provide the OA with the pointing offsets of +15,-18 to zero the telescope coordinates. |
| | 338 | a. If this process does not work for some reason, then you can also zero the telescope coordinates by using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane; ''i.e.'' in the chip gaps). As before, when taking the image of the bright star, make sure to create an OBJECT script with NGUI (not a TEST, because MOSSTAT will ignore it), zd filter, 1 - 5 sec exposure. After centering the bright star, return to the first target field and use the above procedure to determine the pointing offsets - do not use the copilot or mosstat results based on the bright star image! Make sure you move back to the first MzLS tile position after you complete this test. |
| | 339 | a. If mosstat or copilot fails, it could be because (a) the telescope is mis-pointed, (b) the telescope is out of focus (set the focus approx using the formula above and try again). |
| | 340 | a. You can take another OBJECT frame if you want to check to make sure the offset went in the right direction. |
| | 341 | 1. Focus the Telescope |
| | 342 | a. Create a focus script using the NGUI: exposure time 5 or 10 seconds, zd filter, -75 micron focus steps, click Midpoint to *on*, 9 exposures. NOTE: If observing in the 2017B semester, please make sure you are focusing at the sky location 270,+60. |
| | 343 | a. run the focus script from the /home/observer/exec directory (./FOCUS.sh) |
| | 344 | a. copilot will automatically analyze and report the best focus in the mayall-idl window. |
| | 345 | a. or alternately, analyze the focus image using the IRAF script mscstarfocus |
| 355 | | - log the Truss temperature |
| 356 | | - set the telescope focus in the Configuration Monitor: Enter the value in Pedestal focus, '''hit return''', and then hit Apply. If you forget the return, it will do nothing. |
| 357 | | - focus the guiders; this way you can use the guider images to monitor focus drifts |
| 358 | | - [wiki:MayallZbandLegacy/NotesforObservers/FocusInfo Example of a focus sequence] |
| | 349 | a. log the Truss temperature |
| | 350 | a. set the telescope focus in the Configuration Monitor: Enter the value in Pedestal focus, '''hit return''', and then hit Apply. If you forget the return, it will do nothing. |
| | 351 | a. focus the guiders; this way you can use the guider images to monitor focus drifts |
| | 352 | a. [wiki:MayallZbandLegacy/NotesforObservers/FocusInfo Example of a focus sequence] |
