Changes between Version 2 and Version 3 of PublicPages/MayallZbandLegacy/NotesforObservers
- Timestamp:
- Dec 13, 2015 1:51:16 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PublicPages/MayallZbandLegacy/NotesforObservers
v2 v3 5 5 [[PageOutline]] 6 6 7 Log on to the ?? account on the observer2machine:8 Username : ??[[BR]]7 Log on to the mzls account on the mayall-idl.kpno.noao.edu machine: 8 Username : mzls [[BR]][[BR]] 9 9 Password : Ask Arjun, David, or previous observers [[BR]][[BR]] 10 10 11 11 Two environment variables define the locations of data and code: 12 '''$ ??_DATA=''' -- This is where our raw data files are written [[BR]]13 '''$ ??_OBS=$HOME/mosaic3''' -- This contains the observing product with code and versioned log files. [[BR]]14 To set these, type "setenv ??_DATA<path>"12 '''$MOS3_DATA=''' -- This is where our raw data files are written [[BR]] 13 '''$MOS3_OBS=$HOME/mosaic3''' -- This contains the observing product with code and versioned log files. [[BR]] 14 To set these, type, e.g., "export MOS3_DATA=<path>" 15 15 16 16 Other directories in the home directory: 17 '''idl/''' -- IDL products that we make use of, including the idlutils product and the Goodard libraries (a more current version than in idlutils, that does funpack) [[BR]] 18 '''!ObservingStrategy/''' -- Outputs from Anna Patej's observing strategy code [[BR]] 19 '''OBSOLETE/''' -- Obsolete code, data files, log files, etc. [[BR]] 20 '''ps1/''' -- Doug Finkbeiner's Pan-STARRS1 catalogs used by the IDL DECSTAT routine for computing astrometric offsets and photometry [[BR]] 21 '''rawdata@''' -- Convenient link to the raw data directory $??_DATA [[BR]] 22 17 '''ps1/''' -- Doug Finkbeiner's Pan-STARRS1 catalogs used by the IDL DECSTAT routine for computing astrometric offsets and photometry [[BR]] 18 23 19 Documentation for the IDL scripts can be printed from the IDL prompt with the DOC_LIBRARY command, for example: 24 20 {{{ 25 IDL> doc_library,' decstat'21 IDL> doc_library,'mosstat' 26 22 }}} 27 23 … … 39 35 Do the following to update the current NMSL scripts at any time. 40 36 41 - login to the home directory of ?? 42 - cd mosaic3 43 - python2.7 py/mosaic3strategy.py -t obstatus/mosaic-tiles_obstatus.fits -d 2015-04-08 -p 1 -pass 1 --moon-sep-limit 40 --start-date 2015-04-09 --start-time 02:00:00 -seez 1.15 -sbz 18.45 --dir <dir_name> 44 45 Assuming that uptiles is running in an IDL window on ??, this will always use the most up-to-date version of the mosaic-tiles_obstatus.fits file. Once this finishes running (usually a couple of minutes), cd to <dir_name> and execute the script: 46 47 prompt> ./mosaic_<UTdate>_plan.sh 37 - login to mayall-idl as mzls 38 - cd products/mosaic3 39 - python2.7 py/mosaic3strategy.py -t obstatus/mosaic-tiles_obstatus.fits -d 2015-12-13 -p 1 -pass 1 --moon-sep-limit 50 --start-date 2015-12-14 --start-time 02:00:00 -seez 1.15 -sbz 18.45 --dir <dir_name> 40 41 Rename the script, so we don't overwrite it later: 42 43 mv mosaic_2015-12-13_plan.json mosaic_2015-12-13_plan1.json 44 mv strategy_2015-12-13.txt strategy_2015-12-13_plan1.txt 45 46 The mosaicstrategy script outputs a JSON file (e.g., mosaic_2015_12-13_plan.json in the above example). In order to produce the execution script for NOCS, run Behzad Abareshi's script: 47 48 python ./py/jnox.py --in mosaic_2015-12-13_plan1.json --out mzls_2015-12-13_plan1.sh 49 50 Then copy this output (e.g., mzls_2015-12-13_plan1.sh) to the exec directory of the observer account on the mosaic3 computer: 51 52 scp mzls_2015-12-13_plan1.sh observer@mosaic3:/home/observer/exec/ 53 54 Start uptiles running in an IDL window on mayall-idl; this will always use the most up-to-date version of the mosaic-tiles_obstatus.fits file. Once this finishes running (usually a couple of minutes), in a nocs terminal window on mosaic3, cd to exec and execute the script: 55 56 ~/exec> ./mzls_2015-12-13_plan1.sh 48 57 49 58 = Instructions and details for mosaicstrategy.py = … … 82 91 -p *portion of night (1.0, 0.5 (first half), -0.5 (second half))* [[BR]] 83 92 -pass *desired pass - input 1, 2, or 3* [[BR]] 84 --dir *name of the dir where the output scripts are located* 93 --dir *name of the dir where the output scripts are located* [[BR]] 85 94 For instance, to generate a pass 3 plan for the entire night of April 26, 2015, run: 86 95 {{{ … … 98 107 --moon-sep-limit *minimum allowed moon separation, default is 50.0 deg* [[BR]] 99 108 --moon-alt-limit *moon altitude in deg required for switching between z and g,r* [[BR]] 109 --min-dec *Declination minimum limit for choosing tiles [[BR]] 110 --max-dec *Declination maximum limit for choosing tiles [[BR]] 100 111 101 112 3. Custom Scheduling: [[BR]] … … 116 127 To generate a plan for just two hours on the night that starts on 2015-04-06 between 05:00 and 07:00 UTC: 117 128 {{{ 118 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 --m oon-sep-limit 40.0129 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 119 130 }}} 120 131 … … 133 144 134 145 The FITS file listing which tiles have been completed should be updated throughout the night. 135 This file is '''$ DECALS_OBS/obstatus/decam-tiles_obstatus.fits'''. The following IDL command146 This file is '''$MOS3_OBS/obstatus/decam-tiles_obstatus.fits'''. The following IDL command 136 147 will monitor exposures as they are taken throughout the night, automatically updating this file: 137 148 {{{ … … 141 152 At the end of the night, you should check the updated tile file into the svn repository: 142 153 {{{ 143 cd $ ??_OBS/obstatus154 cd $MOS3_OBS/obstatus 144 155 svn commit obstatus/mosaic-tiles_obstatus.fits --username <YOUR-NAME> 145 156 }}}
