|
Time Critical |
Last update of this page: Wed Sep 17 15:41:15 2008
Run State: COMPLETED
USD review status:
O.K.!
| Pre-Imaging? | Special-Calibration? | Time-Critical? | ToO/GTO/Large program? | Carry-Over? | |
|---|---|---|---|---|---|
|
|
|
|
|
Special Remarks:
Very strict time constraints!
Abstract for MTS:
This is a UVES/RED programme on a binary system.
Time requirements are very strict. Times for starting the sequence (t0) are given in the
ephemeris file, which contains Tstart and Tend of the suitable windows for all suitable nights (in general more than one window per night is given, to increase a bit the flexibility). The ephemeris file contains visibility windows from 2007/04/05 to 2007/09/12.
Once t0 for a given night has been choosen, this is the sequence that should be followed:
1) start OB bw3_v38x3_1
2) start OB GJ729x2
3) start either OB Feige67x2 or HD161633x2 (according to observability)
4) if the time elapsed from t0 is less than 2 hours, then start bw3v38x3_fill.
If this is the case, stop it at t0+2hrs
5) start bw3v38x3_2 at t0+2hrs
For more details, please see the README file.
The whole execution should take 3 hours. The sequence cannot be interrupted. If it is interrupted, then the whole set of OBs has to be re-executed.
P.S. This is a compensatory run for a VM run that was affected by a TOO/RRM. It should be given very high priority.
README of this run:
Web version of approved README readme_77006601.html