44 | | = Official Nightly Strategy = |
45 | | **[wiki:MayallZbandLegacy/NightlyStrategy Detailed instructions for NightlyStrategy] |
46 | | |
47 | | |
48 | | = Creating an almanac file with the observations for the night = |
49 | | |
50 | | At the end of the night, an almanac file should be generated for the night and checked into svn. |
51 | | {{{ |
52 | | cd products/mosaic3/logs |
53 | | idl |
54 | | almanac, <START-EXPOSURE>, <END-EXPOSURE> |
55 | | exit |
56 | | svn add Almanac* |
57 | | svn commit Almanac* |
58 | | }}} |
59 | | For example, for the night of March 26/27, 2015, this is done with: |
60 | | {{{ |
61 | | cd products/mosaic3/logs |
62 | | idl |
63 | | almanac, 424978, 425143 |
64 | | exit |
65 | | svn add Almanac_2015-03-26.* |
66 | | svn commit Almanac_2015-03-26.* |
67 | | }}} |
68 | | |
69 | | There are actually two versions of this file, one that is an ASCII file (with .txt extension) |
70 | | and one that is a FITS file (with .fits extension). |
71 | | |
72 | | = Writing the human logs = |
73 | | |
74 | | '''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3''' |
75 | | |
76 | | Please write about what happened during your night: weather conditions, which pass you observed, |
77 | | and telescope problems. Follow the example on the pages at [wiki:DecamLegacy/ObservingLogs]. |
78 | | |
79 | | Catastrophically bad frames (such as saturated frames, or where the telescope moved) are recorded |
80 | | and svn-checked-in to '''products/mosaic3/logs/bad_expid.txt'''. |
81 | | |
82 | | = In case of technical difficulties = |
83 | | |
84 | | We have in the past encountered technical difficulties that have restricted where we can observe to a specific range in RA/Dec. |
85 | | |
86 | | If this happens during your run, you have several options:[[BR]] |
87 | | 1. First, try running mosaicstrategy.py with an appropriate --airmass-limit and/or --moon-sep-limit to try to keep to the required range of tiles. [[BR]] |
88 | | 2. '''Shorten''' your observing period (using --start-date,--start-time and --end-date,--end-time) such that it's scheduling fewer tiles. |
89 | | 3. Increase the assumed seeing such that it schedules longer exposures. |
| 44 | = Are we there yet? = |
| 198 | === Please write human logs === |
| 199 | |
| 200 | '''THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3''' |
| 201 | |
| 202 | Please write about what happened during your night: weather conditions, which pass you observed, |
| 203 | and telescope problems. Follow the example on the pages at [wiki:MayallZbandLegacy/ObservingLogs]. |
| 204 | |
| 205 | Catastrophically bad frames (such as saturated frames, or where the telescope moved) are recorded |
| 206 | and svn-checked-in to '''products/mosaic3/logs/bad_expid.txt'''. |
| 207 | |
| 208 | |
| 209 | === In case of technical difficulties === |
| 210 | |
| 211 | We have in the past encountered technical difficulties that have restricted where we can observe to a specific range in RA/Dec. |
| 212 | |
| 213 | If this happens during your run, you have several options:[[BR]] |
| 214 | 1. First, try running mosaicstrategy.py with an appropriate --airmass-limit and/or --moon-sep-limit to try to keep to the required range of tiles. [[BR]] |
| 215 | 2. '''Shorten''' your observing period (using --start-date,--start-time and --end-date,--end-time) such that it's scheduling fewer tiles. |
| 216 | 3. Increase the assumed seeing such that it schedules longer exposures. |
| 217 | |
| 218 | |