README web version of /home/usg/OPS/MTS/readme_xml/readme_77066604
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
The objective is to perform high-precision photometry of planetary transits
where the planet is known to be periodically transiting.
The target objects are candidates from the OGLE survey that were followed up with
FLAMES in the past, and where the radial velocity curve confirms the interest of
the system. With the photometric follow up, we now want to precisely measure the
radius of the star and the planet, and the precise epoch of the transit center (which
may be shifted by minutes by another planet in the system).
This observation requires:
-time critical sequences of typically 4-6 hour duration (with no interruption)
-saturation on the target star should be checked and avoided all along the sequence,
and exposure time adapted when required (the chosen exposure time should be fine
in normal conditions, according to the ETC)
-the field is not jittered during the sequence and we aim at mmag precision: the
star of interest should then be acquired in a cleaned area of the CCD, and not at
the crossing of readout quadrants
-the HR collimator is used to have a large sampling of the PSF
-the OBs have been prepared to suit the allocated execution time (20h), please repeat
additionnal VR sequences to complete the time if needed (thanks!).
-we are aware that two objects (ogle-56 and ogle-10) culminate close to the zenith.
We think that it should not be so critical and that the sequence should not be interrupted.
Alternatively, we may propose other observing epochs where the transits occurs further
away from culmination, in July.
Waiver Requests
Request :
Our FORS1 observing sequences should be longer than 1hour: the science objective
is to monitore full transits of planetary systems, which last from 2 to 3.5 hours.
We also need some reference flux before and after the transit, minimum half an hour:
this is 1) to insure that the transit is fully covered by our observing sequence
(preicion on the phase and/or orbit shifts may occur) and 2) to get the necessary
reference for systematics removal. So the total observing sequence should be of
3 to 6 hours. Could you please give us the permission to provide OBs longer than
1 hour? This will save acquisition time and insure stability in the position of
the target star, and allow high precision (mmag typically) to be achieved.
Critical Observing Condition Constraints
Time-Critical Aspects
Time sequences for each star:
OGLE-138 should be observed during the first half of the night MAY 27-28:
precisely from 27-may-2006 at 22:30 UT to 28-05-2006 at 4:30 UT (6 hours)
The sequence is divided in 6 OBs to comply with the rule, but the acquisition sequence
should not be repeated (unless needed once).
This is the only transit observable in good airmass conditions during KUEYEN service
nights in period 77.
car.109.8.1088 should be observed twice :
1) during the night MAY 24-25: sequence starts at 1:00UT UT and stops at 5:00 UT
(4 hours)
AND
2) during the night JUNE 30-JULY 1st: sequence starts at 22:30 UT and stops at 01:30
UT (3 hours)
These are the two only epochs were this transit can be partially seen. Both partial
transit sequences will build up a full transit. As one of the recently confirmed
planetary system (FLAMES run of the LP), we do not have extremely precise period
estimate and thus the sequence is long to get the ingress and egress, from which
precise ephemeris will be derived (and more!).
OGLE-56 should be observed during one sequence only, during 3 consecutive hours:
in the OB, we propose two epochs of observations. The OB should be executed once
only, on the night that is more convenient for this program (for instance, best
quality of the night!). The choice is between:
-night MAY 29-30. The sequence starts on May 30 at 3:30 and stops at 6:30 UT (3
hours)
OR
-night JULY 2-3. The sequence starts on July 3 at 1:00 and stops at 5:00 UT
Additionnal possibility:
-night May24-25: the sequence starts at 7:00UT and stops at 10:00UT
OGLE-10 should be observed during one sequence only, during 4 consecutive hours:
in the OB, we propose two epochs of observations. The OB should be executed once
only, on the night that is more convenient for this program (for instance, best
quality of the night!). The choice is between:
-night JULY 1-2. The sequence starts on July 1st at 01:30 and stops at 05:30 UT
(4 hours)
OR
-night JUNE 3-4. The sequence starts on June 4 at 03:40 and stops at 07:40 UT (4
hours)
Additional possibilities (less good for elevation):
-night JUNE 28-29: the sequence starts on June 28 at 23:00 UT and stops on June
29 at 3:00UT
-night May31-June1st: the sequence starts on June 1st at 1:00UT and stops at 5:00UT
Special Execution Requirements
Long sequences: the acquisition should be done once only if possible (no
change of guide star during the sequence, as much as possible), the sequence should
be extended to fit the total execution time of a sequence if needed
Acquisition: the target star should be placed in a quadrant of the CCD
Science exposure: it should not get to saturation but please check the flux level,
especially if the seeing turns very good! Thanks!
Please read the TimeCritical Aspects
Special Calibration Information
ToO Information
ToO Activators List
Is this a Pre-imaging run ?
Pre-imaging Requirements
Source(s) of Pre-imaging
Pre-imaging sources not listed above
Do all your OBs comply with the instrument-specific requirements listed
on the instrument-specific Phase 2 web page ?
If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
Category for each Observing Template ?
Do all your finding charts comply with both the general and instrument-specific
Phase 2 Web Pages ?
If you submitted OBs for standard stars, did you specify the magnitude
and spectral type of all standard stars in the OBs ?
Have you included OBs for any calibrations that you need but which are
not part of the Calibration Plan ?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
If you have preferences which OBs should be executed first, did you make
use of the User Priority field in the OBs ?
If this is a run that requires coordinated observations with other facilities,
did you give proper instructions in the Time-Critical Aspects Section ?
If you have prepared your finding charts with tools other than FIMS,
do they comply with the specifications on the FORS1 Phase 2 web page ?
Last creation of page: Tue Oct 6 15:40:13 2009
If you have comments, please contact usd-help@eso.org