README web version of /home/usg/OPS/MTS/readme_xml/readme_80504301

Principal Investigator Email Address

• beaulieu@iap.fr

Estimated Total Execution Time (hours, including overheads)

• 3h

General Description

• The purpose of this observation is to measure the transit of a planet
   in front of Star GL436, so to detect a possible change of duration of that transit
   caused by another planet.
  
  The challenge is that the transit is a few m-mag deep.
  
  The observations are TIME CRITICAL.
  
  If the OB finishes before the 3h, just repeat it again to fill the 3h.

Waiver Requests

• 3 waivers were requested and granted:
  
  - 3h long OB, defined by the time-critical window
  - bin 1x1
  - BADAO image analysis

Critical Observing Condition Constraints

• PHOT, or very good CLEAR.
  If worse, abort.

Time-Critical Aspects

• Observations must start on 2008-03-01T02:15 UT at the latest, that is
   during the night FRIDAY Feb.29 to Sat.Mar.01 at 23:15 am local time. Try to start
   a little earlier, not later.
  
  
  Observations starts                 23:15 local Feb.29 = 02:15 UT Mar.01
  The transit is supposed to start at 00:15 local Mar.01 = 03:15UT (CRITICAL)
  mid-transit       =                 00:45 local Mar.01 = 03:45UT
  end of transit    =                 01:15 local Mar.01= 04:15UT (CRITICAL)
  observations end                    02:15 local Mar.01 = 05:15 UT
  
  sun at -18        =                 06:20 local = 09:20 UT 
  
  
  The 2 most important moments are the beginning and the end of the transit. Do **NOT**
   interrupt the seguence around these times (+/- 10min)!!!

Special Execution Requirements

• = Observations must be executed with BADAO, so to get a \"defocused\"
   image
  
  = Check the level of the target AND the top left bright star (reference star). The
   top counts should be in the 40 000 - 50 000 adu range. If not, adjust the DIT accordingly.
   Check once in a while during the sequence, while the object gets higher, and adjust
   once in a while if needed. The sequence can be aborted and restarted from the original
   position (i.e. it is not critical to do all the random offsets, it is ok to restart).
   Do not abort around the begin and end of transit (see time critical section).
  
  
  = If the sky degrades to worse than CLEAR, with no hope of improvement, abort and
   move on to another program...

Special Calibration Information

• As many twiFF in V 1x1 as possible. Target: 100 frames!!

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• ---(Empty)---

Source(s) of Pre-imaging

• ---(Empty)---

Pre-imaging sources not listed above

• ---(Empty)---

Do all your OBs comply with the instrument-specific requirements listed
 on the instrument-specific Phase 2 web page ?

• YES

If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
 Category for each Observing Template ?

• N/A

Do all your finding charts comply with both the general and instrument-specific
 Phase 2 Web Pages ?

• YES

If you submitted OBs for standard stars, did you specify the magnitude
 and spectral type of all standard stars in the OBs ?

• N/A

Have you included OBs for any calibrations that you need but which are
 not part of the Calibration Plan ?

• N/A

If you are observing Moving Targets, have you attached suitable ephemeris
 files to your OBs?

• N/A

If you have preferences which OBs should be executed first, did you make
 use of the User Priority field in the OBs ?

• N/A

If this is a run that requires coordinated observations with other facilities,
 did you give proper instructions in the Time-Critical Aspects Section ?

• YES

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 ?

• N/A