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

Principal Investigator Email Address

• wgieren@astro-udec.cl

Estimated Total Execution Time (hours, including overheads)

• 7.0

General Description

• Our goal is to obtain 3 radial-velocity measurements for about 650 main-sequence
   stars in the open cluster NGC 6134 with GIRAFFE-MEDUSA. From these measurements,
   we will be able to establish cluster memberships of the targets. Morevover, binary
   stars will be uncovered.
  
  We have prepared 7 plate configurations. Each plate configuration has to be observed
   3 times. The first epoch will be taken in April 2006, the second between April 2006
   and August 2006 and the third epoch in August 2006. The timing of the observations
   is not critical. There are only 2 easy constraints:
  
  1) the same field should not be observed twice during the same night
  
  2) we want to maximize the time span between the first and the tird epoch. This
   is why observing months have been specified (April 2006 and August 2006). The date
   of the second epoch is not important if constraint number 1 is respected.
  
  About OB names:
  
  NGC6134_Field01_A corresponds to epoch 1 of the first field (taken during run A)
  NGC6134_Field01_B is the second epoch of the same field (taken during run B)
  NGC6134_Field01_C is the third epoch of the same field (taken during run C)
  NGC6134_Field02_A is the first epoch of the second field (taken during run A)
  etc...
  
  The "B" OB of a field should not be taken before the "A" and the "C" not before
   the "A" or the "B". "B" OB of a field can be taken even if there are still missing
   "A" for other fields.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• Airmass has to be less than 2.0
  We wish observation to be taken at dark time but grey time is still acceptable if
   the angular distance to the moon is bigger than 30 degrees.

Time-Critical Aspects

• As written in the general description:
  
  1) OBs for a given field have to be taken in the following order:
  
  for the ield number X
  NGC6134_FieldX_A (corresponding to run A)
  NGC6134_FieldX_B (run B)
  NGC6134_FieldX_C (run C)
  
  2) "A" OBs must be taken in April 2006
  3) "C" OBs must be taken in August 2006
  4) "B" OBs can be taken anytime between April 2006 and August 2006 but the same
   field should not be observed twice the same night.

Special Execution Requirements

• ---(Empty)---

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