|
Time Critical |
Last update of this page: Wed Oct 7 15:41:04 2009
Run State: TERMINATED/EP
USD review status:
O.K.!
| Pre-Imaging? | Special-Calibration? | Time-Critical? | ToO/GTO/Large program? | Carry-Over? | |
|---|---|---|---|---|---|
|
|
|
|
|
Special Remarks:
Execute the remaining OB on a specific night. See the MTS abstract!!
Abstract for MTS:
NOTE (05/03/2009). One single OB is left (333949: ob-T50-11). This should have been executed on Feb 25 (UT) but the epoch was missed due to weather problems. It should now be executed nx11 days after the original date. So, executed this OB on one of the following *UT* nights:
March 8, 19, 30
April 10, 21
May 2, 13, 24
-------------
This is a UVES/red programme on stars for precise RV measurements. The programme is composed by two runs, A) and B). Run B) includes some of the targets of run A), which must be re-observed at least 20 days after.
Note that there are some notes about some of the targets. See the Readme for more details. In particular, there is a target (T50) that needs to be observed at a rate of one OB per night for 11 consecutive nights.
The PI has been informed that this is going to be difficult. If the sequence has to be interrupted for one or two nights, this is the suggested recovery strategy:
-case 1) sequence was interrupted somewhere in the middle but can be continued before end of 11 day period (counted from the start of the sequence), e.g. observations done in night 1-4 and in night 7-11
then: observations for the missing nights should be repeated 11 nights later (or n times 11 nights later), e.g. if night 5 and 6 are missing, observations should be done in night 16 and 17 (or 27 and 28).
-case 2) sequence was interrupted somewhere in the middle and cannot be continued before end of 11 day period (counted from start of the sequence), e.g. observations done in night 1-6
then: start to continue sequence n times 12 nights after last observations, e.g. when interruption occurs after 6 nights observations, continue in night 18 or night 30.
Note that the PI has specified some target priorities. See the UsrP field in OT.
README of this run:
Web version of approved README readme_82002301.html