Changes between Version 6 and Version 7 of PublicPages/MayallZbandLegacy/NotesforObservers


Ignore:
Timestamp:
Dec 13, 2015 3:20:06 PM (8 years ago)
Author:
David Schlegel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PublicPages/MayallZbandLegacy/NotesforObservers

    v6 v7  
    2727any data taken during the night of August 17/18, 2014 will be written as 2014-08-17.
    2828This is consistent with how the NOAO Science Archive timestamps and saves the raw data files.
    29 (This convention has changed from what we did at the start of the survey, but Greg has made
    30 everything consistent.)
    3129
    3230= Official Nightly Strategy =
    33 '''Update 4/26/2015'''
     31'''Update 13 Dec 2015'''
    3432Do the following to update the current NMSL scripts at any time.
    3533
    … …  
    6462    - pyfits
    6563
    66 The code is adopted from the DecamLegacy project. See those wiki pages for more information.
     64The code is adopted from the DecamLegacy project. See those [wiki:DecamLegacy/NotesforObservers wiki pages] for more information.
    6765
    6866=== Selection of Pass 1, 2, or 3 ===
    … …  
    118116
    119117More complicated example using these options: [[BR]]
    120 Assuming 18.2 as z-band sky brightness, 1.2" seeing in z and 1.0" seeing in r, photometric conditions (pass 1) and allowing a moon separation of 40 deg and including DESI tiles:
    121 {{{
    122 python ./mosaicstrategy.py -t mosaic-tiles_obstatus.fits -d 2015-03-24 -p 1.0 -pass 1 -sbz 18.2 -seer 1.0 -seez 1.2 --moon-sep-limit 40.0 --expand
     118Assuming 18.2 as z-band sky brightness, 1.2" seeing in z and 1.0" seeing in r, photometric conditions (pass 1) and allowing a moon separation of 50 deg and including DESI tiles:
     119{{{
     120python ./mosaicstrategy.py -t mosaic-tiles_obstatus.fits -d 2015-03-24 -p 1.0 -pass 1 -sbz 18.2 -seer 1.0 -seez 1.2 --moon-sep-limit 50.0 --expand
    123121}}}
    124122
    … …  
    126124To generate a plan for just two hours on the night that starts on 2015-04-06 between 05:00 and 07:00 UTC:
    127125{{{
    128 python ./mosaicstrategy.py -t mosaic-tiles_obstatus.fits -d 2015-04-06 -p 1.0 -pass 1 --start-date 2015-04-07 --start-time 05:00:00 --end-date 2015-04-07 --end-time 07:00:00 --min-dec=34 --max-dec=50 --moon-sep-limit 40.0
     126python ./mosaicstrategy.py -t mosaic-tiles_obstatus.fits -d 2015-04-06 -p 1.0 -pass 1 --start-date 2015-04-07 --start-time 05:00:00 --end-date 2015-04-07 --end-time 07:00:00 --min-dec=34 --max-dec=50 --moon-sep-limit 50.0
    129127}}}
    130128
    131129=== Outputs ===
    132130
    133 This script will many output data files:
     131This script will output many data files to your current directory:
    134132
    135133    1. a single text file called "strategy_mm-dd.txt", with information about all the pointings for the night (exp time, filter, approximately when they should be run, airmass, etc). There is a corresponding plot of what has been observed previously (by pass) and what you will be observing given the plan for the night: saved as a pdf, 'plot_plan_yyy-mm-dd.pdf' (gray = z, red = r, green = g). Planets and moon are plotted as well.
    136134   
    137135    2. many executable script files of the form "Mosaic_Survey<tile id>.sh" for the night corresponding to the plan. There is one script file for each pointing in the plan. A single meta-script is produced  that will call those ".sh" files: moasic_<ut date>_plan.sh.
    138  
    139136
    140137   3. A FITS file called "decam-tiles_obstatus_update_yyyy-mm-dd.fits" that is a temporary updated mosaic obstatus file that assumes all planned observations were completed. This should not be used during the run; instead use the updated tiles file obtained from running the idl program, uptiles (see section on "Creating the Updated Observing Status File" below).
    … …  
    155152}}}
    156153
    157 = Use of Steve Kent's tools for monitoring observing =
    158 
    159 === Not yet installed at Mayall. ===
    160 
    161 During observing, please check frames as they read out. To use kenttools remotely, you must be
    162 logged in as ''DECamObserver'' rather than as ''declsp''. To load kenttools log onto observer2 and
    163 type "observer" at the unix shell prompt. This will load up an environment in which you can run the
    164 kenttools commands.
    165 
    166 prompt>
    167 
    168 The following commands from kenttools are
    169 very useful:
    170        center - find the RA and DEC offsets[[BR]]
    171        seeingall - measures the seeing[[BR]]
    172        psc - provides a heap of useful data[[BR]]
    173        bigload - display the last image[[BR]]
    174        load - display a single CCD from the last image[[BR]]
    175        inv - show an inventory of all the fits files taken during the night[[BR]]
    176 
    177 More details about kenttools can be found here:  https://cdcvs.fnal.gov/redmine/projects/desops/wiki/Introduction_to_kentools
    178 
    179 In addition to kenttools, there is an even more useful version of inv in godb called "qcInv". To use
    180 this instead, log onto ?? as ?? " and type "godb" and then "qcInv" at the
    181 ''pgtcl>'' prompt.
    182 
    183154= Checking the Sky Brightness, Seeing and Transparency  =
    184155
    … …  
    187158
    188159From an IDL prompt, use the MOSSTAT routine to analyze the latest image on disk:
    189 === Not yet installed at Mayall ===
    190 
    191160{{{
    192161   IDL> mosstat
    193162}}}
    194163There are keyword options that allow you to choose different exposure numbers or CCDs
    195 within that exposure.  For example, to analyze chip 'S4' of the exposure number 123456, type:
    196 {{{
    197    IDL> mosstat, 123456, ext='S4'
     164within that exposure.  For example, to analyze chip 'im16' of the exposure number 12345, type:
     165{{{
     166   IDL> mosstat, 12345, ext='im16'
    198167}}}
    199168The full documentation can be seen with:
    … …  
    203172
    204173If the telescope pointing has gone off by more than about 30 arcsec (which happens!), then
    205 this routine will likely fail to match stars.  In that case, the kenttools routine '''center''' described above should be used to find the telescope offset.  Stop observing and ask the telescope operator to apply a pointing offset.
    206 
     174this routine will likely fail to match stars.  If this happens, the operator will need to recenter the telescope.
     175
     176'''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3'''
    207177One can also check the observing progress using the almanac command:
    208178  IDL> almanac, 10001, /noprint
    … …  
    210180
    211181= Creating an almanac file with the observations for the night =
     182
     183'''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3'''
    212184
    213185At the end of the night, an almanac file should be generated for the night and checked into svn.
    … …  
    235207= Writing the human logs =
    236208
     209'''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3'''
     210
    237211Please write about what happened during your night: weather conditions, which pass you observed,
    238212and telescope problems.  Follow the example on the pages at [wiki:DecamLegacy/ObservingLogs].
    … …  
    243217= In case of technical difficulties =
    244218
    245 We have in the past encountered technical difficulties that have restricted where we can observe to a specific range in RA/Dec. For instance, in April 2015, we had a night during which the windscreen was stuck, requiring us to stick to dec < -5 deg tiles.
     219We have in the past encountered technical difficulties that have restricted where we can observe to a specific range in RA/Dec.
    246220
    247221If this happens during your run, you have several options:[[BR]]
    … …  
    299273This will run mosstat on each frame as it shows up and display the results on the screen.
    300274
    301 === Start a window for running kenttools ===
    302 
    303 Kenttools can only be run as the "??", and not from our "??" account.
    304 
    305 Open a new window logged in as ''??'' on ??:
    306 {{{
    307 observer> observer
    308 prompt> inv
    309 }}}
    310 
    311275=== Create the Almanac and Almanac plot files  ===
    312276
     277'''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3'''
    313278At the end of the night, create the Almanac files and check them into svn.
    314279{{{
    … …  
    323288
    324289=== Create a log file ===
    325 {{{
    326 - cd logs/
    327 - observer (kent tootls on observer1)
    328 - inv
    329 - cut and paste the output from the first exposure number to the bottom
    330   into a file log_date.txt (on observer2)
    331 - use this file to determine the number of g, r, and z images for the
    332   summary table on the wiki: grep " g " log_date.txt | wc
    333 }}}
     290
     291'''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3'''
     292
    334293
    335294=== Generating a Coverage Map ===