README web version of /home/usg/OPS/MTS/readme_xml/readme_77066605
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
Photometric observations of the transiting planet OGLE-TR-182. Warning:
the high resolution collimator will be used (Coll_HR+2).
One occulting bar is inserted in the field of view to block the light of a nearby
bright star. 8 reference stars have been selected for the mask alignment. As the
alignment accuracy is not critical, MIDAS alignment procedure results can be accepted
even if only 1 reference star is found to be valid.
We plan to observe 2 consecutive transits during the following night: 2007-03-15/16
and 2007-03-19/20. Observations in both case should be started as early as possible
in the evening twilight (mid-transit point shortly after or at the end of the twilight).
See the time-critical aspects section for details).
We have prepared series of 3 OBs for the two epochs:
--OGLE-TR-182_epoch1_01,02,03:
for the 2007-03-15 transit (R band HR imaging)
--OGLE-TR-182_epoch2_R_01,02,03:
for the 2007-03-19 transit (R band HR imaging)
--OGLE-TR-182_epoch2_B_01,02,03:
for the 2007-03-19 transit (B band HR imaging)
The 2007-03-15 transit will be observed with the R filter. If sufficient quality
data of the first transit can be secured, then the second transit will be observed
with the B filter. If not, the second series will be taken again with the R filter.
The nighttime astronomer will be informed early enough about our filter choice (one
CoI will be on duty at Paranal).
The total execution time for each of the 3 series of OBs is a bit more than 3 hours
(i.e. longer than the planned nighttime observations). There are two reasons for
that:
1) Observations will start in the twilight
2) The acquisition will be made only once per night --> the nighttime astronomer
will have to skip the acquisition templates of the second and third OBs of a given
night. This will save time.
We have asked for clear conditions but thin clouds if they are located low enough
(altitude lower than 35 degrees) are not a problem.
Waiver Requests
A waiver was submitted asking for the authorization of executing sequences
of OBs lasting more than 1 hour. Waiver ID: 177.C-0666F.01.wav
Waiver granted on March the 1st 2007.
If the conditions become really bad (thick clouds) after the first hour of execution,
the nighttime astronomer should interrupt the sequence. If thin clouds arrive after
the 1st hour of execution or if the seeing value exceeds our constraint (i.e. worse
than 1.5'' on the image), the sequence should be continued as the data obtained
in such conditions would remain usable.
Critical Observing Condition Constraints
R-band OBs: with exposure times currently selected in the OBs (60sec),
there are risks of saturation if the seeings becomes too good. We ask the nighttime
astronomer to check the target counts. We aim at obtaining a peak signal between
30000 and 40000 ADUs. If the measured signal exceeds 40000, the nighttime astronomer
should adjust the exposure times in all the observing templates. We suggest:
Seeing >= 0.8'' => extime=60seconds
0.6 <= Seeing <0.8'' => exptime=45 seconds
seeng < 0.6'' => exptime=30 seconds
If the exposure times need to be reduced, then extra-templates should be added in
order to end the sequence at the specified UT hour.
B-band OBs: with 100 sec integration time, the target peak signal should not exceed
40000 ADU even with a seeing of 0.4'' (very unlikely at this wavelength) => no
adjustement foreseen
Time-Critical Aspects
The aims of these observation is to cover to half-transits of OGLE-TR-182
b. The mid-transit UT dates are:
2007-03-16T00:36:00
and
2007-03-20T00:06:00
Observations should start a bit before mid-transit and end about 1 hour after the
end of the transits (we need to sample well the out-of-transit level). The mid-transit
time of the 2007-03-19/20 transit takes place a few minutes before the end of the
evening twilight. It is critical in this case to start the measurement in the twilight.
Even if this is less critical for the 2007-03-15/16 transit, we also request early
observations startup. The following intervals account for these requirements:
epoch1:
2007-03-15T23:50:00 -- 2007-03-16T02:54:00
Total duration: 03:04
Nighttime duration: 02:40
epoch2:
2007-03-19T23:45:00 -- 2007-03-20T02:30:00
Total duration: 02:45
Nighttime duration: 02:20
Special Execution Requirements
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