Changes between Version 212 and Version 213 of PublicPages/MayallZbandLegacy/NotesforObservers

Timestamp:

Sep 26, 2017 1:24:46 PM (7 years ago)

Author:

Arjun Dey

Comment:

--

PublicPages/MayallZbandLegacy/NotesforObservers

@@ -336 +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
     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.
-    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.
+    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.
     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).
     a. You can take another OBJECT frame if you want to check to make sure the offset went in the right direction.
@@ -461 +461 @@
 ==== Please write useful human logs ====
 
-Keep a log about weather conditions, which pass you observed, and telescope problems.  Follow the example on the pages at [wiki:MayallZbandLegacy/ObservingLogs] . Please make a note of when you make any changes to the focus (note the time and the image exposure number before/after the focus change), any changes to weather conditions (increase in wind speed, change in direction, changes in humidity, sky brightness, cloud cover, etc.). Please stay aware of the observing conditions. Go out an look at the sky yourself every few hours - do not rely solely on the computer monitors and telemetry. Don't worry - you will not be eaten; just carry a flashlight. Sing loudly, if that helps :)
+Keep a log about weather conditions, which pass you observed, and telescope problems.  Follow the example on the pages at [wiki:MayallZbandLegacy/ObservingLogs] . Please make a note of when you make any changes to the focus (note the time and the image exposure number before/after the focus change), any changes to weather conditions (increase in wind speed, change in direction, changes in humidity, sky brightness, cloud cover, etc.), and any pointing corrections (please note the time and magnitude, and if possible the frame number). Please stay aware of the observing conditions. Go out an look at the sky yourself every few hours - do not rely solely on the computer monitors and telemetry. Don't worry - you will not be eaten; just carry a flashlight. Sing loudly, if that helps :)
 
 Please record any catastrophically bad frames (such as saturated frames, or where the telescope moved) in the bad_expid.txt file. This file is svn-checked-in at the end of the night.