Changes between Version 134 and Version 135 of PublicPages/MayallZbandLegacy/NotesforObservers


Ignore:
Timestamp:
Mar 10, 2016 8:58:38 PM (9 years ago)
Author:
Robert Blum
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PublicPages/MayallZbandLegacy/NotesforObservers

    v134 v135  
    121121----
    122122
    123 
    124123= [1] Update everything =
    125124
    … …  
    191190
    192191On mayall-2, double click on the MOSAIC3 icon, which brings up the MOSAIC3 Menu on the left edge of the screen.
    193 1. Start the camera control program by pressing the yellow "Start Cameras" button. Wait for this to finish, then dismiss the screen by typing any key as instructed
    194 2. Start the MOSAIC3 NOCS software by pressing the blue "Start MOSAIC" button. This launches a blue xterm. Move it out of the way and watch all the windows come up
     1921. **Start the camera control program** by pressing the yellow "Start Cameras" button. Wait for this to finish, then dismiss the screen by typing any key as instructed
     1932. **Start the MOSAIC3 NOCS** software by pressing the blue "Start MOSAIC" button. This launches a blue xterm. Move it out of the way and watch all the windows come up
    1951943. Rearrange the desktop as needed.
    196195
    197 If, for some reason, the buttons do not work, you can start up the software on a command line as follows:
    198 On mayall-2 open a terminal window and:
    199 {{{
    200 ssh -XY observer@mosaic3
    201 nocs start ccp (this is equivalent to the "Start Cameras" button on the MOSAIC3 Menu)
    202 nocs start all (this is equivalent to the "Start MOSAIC" button on the MOSAIC3 Menu)
    203 }}}
    204 Once nocs is up and running, rearrange windows as desired, and check the status of the system by typing
    205 the following in a nocs terminal window:
     196 If, for some reason, the buttons do not work, you can start up the software on a command line as follows.
     197 On mayall-2 open a terminal window and:
     198{{{
     199 ssh -XY observer@mosaic3
     200 nocs start ccp (this is equivalent to the "Start Cameras" button on the MOSAIC3 Menu)
     201 nocs start all (this is equivalent to the "Start MOSAIC" button on the MOSAIC3 Menu)
     202}}}
     203
     204 Once nocs is up and running, rearrange windows as desired, and check the status of the   system by typing the following in a nocs terminal window:
    206205{{{
    207206nocs status all
    … …  
    209208}}}
    210209
    211 If you want to know what these commands actually do, see here: [wiki:MayallZbandLegacy/NotesforObservers/MOSAICGUI_Notes]
     210 If you want to know what these commands actually do, see here: [wiki:MayallZbandLegacy/NotesforObservers/MOSAICGUI_Notes]
    212211
    2132124. Launch CCD temperature monitor from "MOSAIC Temps" icon (CCD and Dewar temps should be around 173C and 90C respectively)
    … …  
    2162157. Launch Truss temperature monitor from "Truss C" icon
    217216
    218 All these icons are on the right side of the left hand screen of the mayall-2 computer display. Rearrange the busy desktop as needed ...
     217All these icons are on the right side of the left hand screen of the mayall-2 computer display. Many or all of these may be running already. They can stay up. Rearrange the busy desktop as needed ...
    219218
    220219= [5] Set the PROP-ID and Project Info =
    … …  
    258257= [8] Just before observing =
    259258
    260 0. It is best to start things up after sunset and to be ready to start observing before the 10 deg twilight mark.
    261 10 deg twilight times for KPNO are listed here:
     259It is best to start things up after sunset and to be ready to start observing before the 10 deg twilight mark.
     26010 deg twilight times for KPNO are listed here:
     261
    262262Before 10 deg twilight, you can do all the steps in [8] (i.e., this one)
    263263
    … …  
    271271}}}
    272272
    273 The VNC session should automatically start MUPTILES, MOSSTAT and COPILOT. Rearrange as desired.
    274 
    275 If it doesn't, open terminals in the VNC session and manually run the scripts for monitoring the observations and updating the tile file:
    276 
    277 1a) The FITS file listing which tiles have been completed should be updated throughout the night.
    278 This file is '''$MOS3_OBS/obstatus/mosaic-tiles_obstatus.fits'''.  The following IDL command
    279 will monitor exposures as they are taken throughout the night, automatically updating this file.
    280 From a terminal on the mayall-idl VNC, in the mzls account, start this running:
     273 The VNC session should automatically start MUPTILES, MOSSTAT and COPILOT.  Rearrange as desired.
     274
     275 If it doesn't, open terminals in the VNC session and manually run the scripts for monitoring the observations and updating the tile file:
     276
     277 1a) The FITS file listing which tiles have been completed should be updated throughout the night.
     278 
     279 This file is '''$MOS3_OBS/obstatus/mosaic-tiles_obstatus.fits'''.  The following IDL command will monitor exposures as they are taken throughout the night, automatically updating this file.
     280
     281 From a terminal on the mayall-idl VNC, in the mzls account, start this running:
    281282{{{
    282283idl
    283284   muptiles
    284285}}}
    285 At the end of the night, you should check the updated tile file into the svn repository.
    286 
    287 1b). In a second terminal on the VNC tart the automated script for monitoring the data quality
     286 At the end of the night, you should check the updated tile file into the svn repository.
     287
     288 1b). In a second terminal on the VNC tart the automated script for monitoring the data quality
    288289{{{
    289290idl
    290291   mosstat_continuous
    291292}}}
    292 This will run mosstat on each frame as it shows up and display the results on the screen.
    293 
    294 1c). In a third terminal on the VNC start running [wiki:MayallZbandLegacy/NotesforObservers/Copilot copilot]:
     293 This will run mosstat on each frame as it shows up and display the results on the screen.
     294
     295 1c). In a third terminal on the VNC start running [wiki:MayallZbandLegacy/NotesforObservers/Copilot copilot]:
    295296{{{
    296297cd ~/obsbot
    … …  
    298299}}}
    299300
    300 2. Take a zero image to ensure everything is working. Once the image has been written, use the
    301 IRAF window and run mscstat <filename> to make sure the system came up OK. See step [6] above.
     3012. Take a zero image to ensure everything is working. Once the image has been written, use the IRAF window and run mscstat <filename> to make sure the system came up OK. See step [6] above.
    302302
    3033033. Set the focus to some approximate value based on the Truss temperature and the formula:
    304 - Focus(zd) = -8400+(1.4-Ttruss)x110
    305 where Ttruss is in deg C
    306 
    307 4. Ask the telescope operator to point the telescope to a 5th mag star and to center it on the MOSAIC3 focal plane.
     304 
     305 Focus(zd) = -8400+(1.4-Ttruss)x110
     306 
     307 where Ttruss is in deg C.
     308
     3094. Ask the telescope operator to point to the first tile in the json file in pass 2 (for normal case, or json of forced pass if starting up non standard). Then ask the telescope to go to a  nearby 5th mag star and to center it on the MOSAIC3 focal plane. The coordinates of the first tile can be found by:
     310 
     311{{{
     312 cd ~/exec/mosbot on mosaic3
     313 cat exposure-1.sh | grep RA
     314}}}
     315
     316 give the coordinates to the OA.
    308317
    3093185. Wait patiently for 10 deg twilight.
    … …  
    3163251. 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.
    317326
    318 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 the 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.
     3272. Move back to the first MzLS tile position from item [8].4. 
    319328
    3203293. Focus the telescope