|
Time Critical |
| DDT |
Last update of this page: Wed Oct 7 15:41:04 2009
Run State: TERMINATED/IA
USD review status:
O.K.!
| Pre-Imaging? | Special-Calibration? | Time-Critical? | ToO/GTO/Large program? | Carry-Over? | ||
|---|---|---|---|---|---|---|
|
|
|
|
|
Special Remarks:
Trying this again now, but the execution window is narrow
Abstract for MTS:
Unfortunately the user is not used to SM observations it seems, so I have
not been able to get him to simplify the strategy. There are several
complicating factors here:
1) The constraint set is not the easiest, especially for the U-band.
2) It is a moving target which is rapidly getting fainter.
3) He needs simultan observations on FORS1 and 2.
There is another window of opportunity through May 10. The PI has submitted a new
README file describing this.
Here start of several previous USD comments on this run
--------------------------------------------------------
Deep imaging of the extinct comet candidate. Moving target. The correct observing windows are in the Ephemeris file.
There are 3 OBs, but ONLY 2 need to be executed!
OB "1" should be observed before April 20.
If possible observe OB "S" on April 20 simultaneously with the same OB on FORS1 (run A). If that is successful please ignore OB "2" - send a usd-help ticket so that the last OB can be canceled.
If simultaneous observation fails please observe OB "2" and inform us to delete the OB "S".
Please see README for the details on observations and the necessary calibrations. The PI asks NOT to have differential tracking on during short expousres - I don't know if it is possible to switch the tracking off and on during one single OB. The PI has been warned that this may not be possible...
Due to the very limited opportunities for simultateous FORS1 and FORS2 observation, the PI has relaxed his requirements. The first FORS2 OB can be executed stand-alone (without the FORS1 OB), as long as the second FORS2 OB is observed together with a FORS1 OB if possible.
Here is the old (previous) version of MTS:
README of this run:
Web version of approved README readme_78506601.html