Changes between Version 104 and Version 105 of PublicPages/MayallZbandLegacy/NotesforObservers
- Timestamp:
- Feb 22, 2016 12:41:20 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PublicPages/MayallZbandLegacy/NotesforObservers
v104 v105 18 18 Prolonged exposure can damage and even destroy the devices. The following rules are in effect: 19 19 20 1. Operation on sky is restricted to between 1 2deg twilights.20 1. Operation on sky is restricted to between 10 deg twilights. 21 21 2. Operation is restricted to when OAs or other NOAO technical/scientific staff are present 22 22 3. The cameras and MOSAIC software should be shut down when observing / NOAO personnel are not present … … 196 196 Then, in one of the NOCS xterm windows, type: "nocs set project" 197 197 198 = [6] Take a test image to ensure system is working =198 = [6] Take a test Zero image to ensure system is working = 199 199 200 200 Check that all is well by taking a test zero exposure. … … 218 218 219 219 = [8] Just before observing = 220 221 0. It is best to start things up after sunset and to be ready to start observing before the 10 deg twilight mark. 222 10 deg twilight times for KPNO are listed here: 223 Before 10 deg twilight, you can do all the steps in [8] (i.e., this one) 220 224 221 225 1. Start the mayall-idl:1 VNC session. … … 255 259 }}} 256 260 257 = [9] Observe - start of night = 258 259 ''No on-sky observations are permitted before 12 deg twilight.'' 260 261 1. Take a zero image to ensure everything is working 262 263 2. Set the focus to some approximate value based on the Truss temperature and the formula: 261 2. Take a zero image to ensure everything is working. Once the image has been written, use the 262 IRAF window and run mscstat <filename> to make sure the system came up OK. See step [6] above. 263 264 3. Set the focus to some approximate value based on the Truss temperature and the formula: 264 265 - Focus(zd) = -8400+(1.4-Ttruss)x110 265 266 where Ttruss is in deg C 266 267 267 3. At start of night, check telescope pointing and zero the telescope coordinates using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane). 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. Watch for MOSSTAT to process the image and report the RA, Dec offsets. If mosstat 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). Once you are able to determine offsets, give these offsets to the OA with **opposite** sign. That is, if mosstat reads "RA,Dec offsets = -15.34, 18.32", then you need to provide the OA with the offsets of +15,-18 to zero the telescope coordinates. You can take another OBJECT frame if you want to check to make sure the offset went in the right direction. 268 269 4. Move to the beginning of the first MzLS tile position. What position is that, you ask? One way to find out is to run mosbot.py (see step 5 below), and look for RA, DEC in expose-1.sh in the exec/mosbot/ directory. Tell these coordinates to the OA to move the telescope. Another way is to look at teh first entry in the ~/obsbot/pass1.json file on the mayall-idl computer - remember, it is in degrees, so you will have to divide the RA by 15. Getting within a degree is close enough, so no need to be super precise. 270 271 5. Focus the telescope 268 4. Ask the telescope operator to point the telescope to a 5th mag star and to center it on the MOSAIC3 focal plane. 269 270 5. Wait patiently for 10 deg twilight. 271 272 = [9] Get Ready to Observe - start of night = 273 274 ''No on-sky observations are permitted before 10 deg twilight.'' 275 276 1. At start of night, check telescope pointing and zero the telescope coordinates using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane). 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. Watch for MOSSTAT to process the image and report the RA, Dec offsets. If mosstat 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). Once you are able to determine offsets, give these offsets to the OA with **opposite** sign. That is, if mosstat reads "RA,Dec offsets = -15.34, 18.32", then you need to provide the OA with the offsets of +15,-18 to zero the telescope coordinates. You can take another OBJECT frame if you want to check to make sure the offset went in the right direction. 277 278 2. Move to the beginning of the first MzLS tile position. What position is that, you ask? One way to find out is to run mosbot.py (see step 5 below), and look for RA, DEC in expose-1.sh in the exec/mosbot/ directory. Tell these coordinates to the OA to move the telescope. Another way is to look at teh first entry in the ~/obsbot/pass1.json file on the mayall-idl computer - remember, it is in degrees, so you will have to divide the RA by 15. Getting within a degree is close enough, so no need to be super precise. 279 280 3. Focus the telescope 272 281 - create a focus script using the NGUI: exposure time 5 or 10 seconds, zd filter, -100 micron focus steps, click Midpoint to *on*, 9 exposures. 273 282 - run the focus script from the /home/observer/exec directory … … 282 291 **[wiki:MayallZbandLegacy/NotesforObservers/FocusInfo Example of a focus sequence] 283 292 284 === Observe - all night long! ===285 286 6. From the mzls@mayall-idl window, generate the top-level observing script (tonight.sh) assuming that we have three plan files named pass1.json, etc.293 === [10] Observe - all night long! === 294 295 1. From the mzls@mayall-idl window, generate the top-level observing script (tonight.sh) assuming that we have three plan files named pass1.json, etc. 287 296 {{{ 288 297 cd ~/obsbot … … 296 305 Note that if you need to escape the script at some point during the night (see below), you will need to CTRL-C to stop mosbot.py and **restart** it when you are ready to start up again. If you forget this, you will be observing tiles that you already observed earlier in the night. 297 306 298 7. From the observer@mayall-3 xterm window, start taking exposures using the top-level observing script (tonight.sh):307 2. From the observer@mayall-3 xterm window, start taking exposures using the top-level observing script (tonight.sh): 299 308 {{{ 300 309 cd ~/exec/mosbot … … 302 311 }}} 303 312 304 8. "copilot" should already be running. If not, start running "copilot" in the mayall-idl VNC window. Copilot keeps a beautiful running plot of observing conditions. From any mzls@mayall-idl window:313 3. "copilot" should already be running. If not, start running "copilot" in the mayall-idl VNC window. Copilot keeps a beautiful running plot of observing conditions. From any mzls@mayall-idl window: 305 314 {{{ 306 315 cd ~/obsbot … … 316 325 See [wiki:MayallZbandLegacy/NotesforObservers/Copilot] 317 326 318 8. Monitor focus by checking the image quality on each frame. Keep track of the truss temperature variation and use the information to modify the focus as needed. Note that the focus may not respond quickly to changes in temperature, so monitor the images carefully before adjusting focus. The Mayall has astigmatism, so one can sometimes tell from the shape of the images which way to move the focus. To stop and do a focus sequence:327 4. Monitor focus by checking the image quality on each frame. Keep track of the truss temperature variation and use the information to modify the focus as needed. Note that the focus may not respond quickly to changes in temperature, so monitor the images carefully before adjusting focus. The Mayall has astigmatism, so one can sometimes tell from the shape of the images which way to move the focus. To stop and do a focus sequence: 319 328 - Create a file to tell obsbot to quit 320 329 {{{