|
Time Critical |
Last update of this page: Tue Oct 7 15:41:35 2008
Run State: TERMINATED/IA
USD review status:
O.K.!
| Pre-Imaging? | Special-Calibration? | Time-Critical? | ToO/GTO/Large program? | Carry-Over? | |
|---|---|---|---|---|---|
|
|
|
|
|
Special Remarks:
OBs must be executed on specific time windows.
Abstract for MTS:
This is a FORS1/IMG/IPOL programme on the comet 2P/Encke. OBs must be executed in specific time windows, specified in the Time Constraints of each OB. For practical reasons, these dates are also written in the OB names themselves. The PI has submitted an ephemeris file which contains all relevant data to be entered in the OBs at execution time (this is a moving target).
Pairs of IPOL+IMG OBs must be separated by at least 2 nights.
At each epoch, two OBs must be executed: the IPOL part (_IPOL_) has to be immediately followed by the IMG part (_IMG_). The acquisition of IMG OB can be skipped.
Each IPOL+IMG sequence should be completed anyway, even if the conditions change from CLR to THN. To solve these possible problems, the PI has submitted some dummy OBs, which will normally not appear in the queues (to avoid confusion). When sky transparency violations occurr, the PI will contact USD and ask one of those OBs to be executed under CLR conditions. These OBs include only imaging and will re-image the field where the affected comet observations took place.
USD will queue the relevant OB and notify Kueyen with an email. These dummy OBs are not time critical.
NOTE: do not execute the OBs if seeing is too good (<0."5).
README of this run:
Web version of approved README readme_78050900.html