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

Principal Investigator Email Address

• suz@astro.ex.ac.uk

Estimated Total Execution Time (hours, including overheads)

• 18

General Description

• The primary goal of this program (080.C-0718) is to confirm cluster
  membership and determine dynamical masses for a number of candidate
  pre-main sequence low-mass eclipsing binaries which were identified in
  a number of young open clusters on the basis of I-band photometric
  monitoring as part of the Monitor project (see e.g. LP 175.C-0685). To
  do this, we are using FLAME+UVES and the standard CD3/580nm setting,
  primarily to measure precise (~200m/s) radial
  velocities. 
  
  Additionally, we are using GIRAFFE and the HR14A setting to monitor
  radial velocities and Halpha profiles for several hundred candidate
  cluster members with light curves from the Monitor project in order to
  investigate the connection between rotation, accretion and
  binarity. Note that this differs from the proposal where we said we
  would use HR15. Since writing the proposal we have investigated the
  relative performance of the two settings for RV determination and
  found HR14A would be slightly better. We will obtain 1 epoch at HR15
  during the visitor mode run (run A) to measure Lithium EWs in the
  clusters where this is useful (NGC2362 and NGC2547, ONC was already
  covered in HR15 in P78).
  
  This run (run B) should be executed after run A (visitor mode, 11 to
  16 Dec 2007), which it complements. It targets 4 fields in 3 clusters:
  NGC2362 (1 field), NGC2547 (2 fields) and M50 (1 field). There are 4
  identical OBs (i.e. 4 epochs) for each field.
  
  Please note the special execution requirements concerning the time
  interval between OBs for a given field.
  
  Notes on the finding charts:
  
  The images are 30'x30' from MAST DSS (POSS 2 red).
  The black plus sign marks the field centre, the black circle the
  FLAMES FOV (25' diameter), the red diamond the guide star, the red
  squares the fiducial stars, the green circles the UVES fibres, the
  blue circles the Medusa fibres, and the blue crosses the sky
  fibres). We have checked our astrometry against 2MASS and find them to
  be consistent at the 0.06" level.

Waiver Requests

• A waiver request to allow the OBs to run up to 70 min was accepted
  with the proviso that the OBs will not be re-executed if the
  conditions degrade after 1h.

Critical Observing Condition Constraints

• The observations should be executed in clear conditions and with <=0.8"
   seeing to achieve the
  required signal-to-noise, and observing at airmass > 1.6 should be
  avoided or the fibre configurations will not be valid. There are no
  lunar illumination constraints, but in grey or bright time the moon
  should be kept > 30 deg from the targets.

Time-Critical Aspects

• The observations are not time-critical, but please note the special
  execution requirements regarding interval between consecutive OBs.

Special Execution Requirements

• Run B consists of 4 identical OBs per field, i.e. 4 epochs, ideally to
   be spread over a period of ~4 weeks starting 1 week after the end of run A. The
   exact interval between consecutive OBs for a given field is not critical, but should
   be no less than 8h, and
  preferably no more than 1 week. I have specified lose time intervals (two weeks
   for each OB, staggered a week apart) in the hope of achieving this, but these should
   be interpreted losely: it is preferrable to execute an OB outside its specified
   interval than not to execute it at all. It is desirable to vary the interval 
  between consecutive OBs to minimise structure in the window function. In practice,
   the order in which the OBs for a given field are executed doesn't matter as they
   are all identical. 
  
  Although we would prefer it if the OBs of run B were executed after run A (as it
   will enable us to diagnose and fix any problems with the fibre and instrument configurations
   while at the telescope during run A), it would not be catastrophic if some of the
   OBs for this run were executed before run A.

Special Calibration Information

• ---(Empty)---

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 ?

• N/A

Did you specify in your OBs the hour angle range for which your Target
 Setup files are valid ?

• YES

Did you specify in your OBs the magnitudes of FACBs and Guide Star for
 all your fields ?

• YES

Are the FACBs and Guide Star in the brightness ranges specified in the
 FLAMES manual ?

• YES

Did you enter the expected signal to noise in your OBs ?

• YES