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

Principal Investigator Email Address

• s.clark@open.ac.uk

Estimated Total Execution Time (hours, including overheads)

• 16.5hrs

General Description

• This program, composed of 6 different runs, is designed to look for shifts
   in the positions of spectral lines of massive OB stars in the young massive cluster
   Westerlund 1 in order to 
  identify binaries. As such the program has rather complex time constraints which
   we detail in the time critical aspects section.
  
  We have 4 configs. in each run (A)-(D), of which one contains bright stars and the
   3 
  remaining containing fainter stars. Runs (E) & (F) only contain the bright star
   config.

Waiver Requests

• Given the work being done on FLAMES two waivers wwere applied for and
   granted. The first was simply to submit the OBS after the Feb 14 deadline such that
   additional monte carlo simulations  could be undertaken to refine our observing
   startegy. In light of this we applied for and were granted a  second in order to
   obtain more epochs of observations.

Critical Observing Condition Constraints

• None

Time-Critical Aspects

• The program is designed to search for massive binaries with periods of
   days to hundreds of days  within Wd1, and also to provide the first constraints
   on the radial velocity curves of putative binaries. As such the scheduling of the
   runs is important.
  
  Each of the runs (A), (B), (C) and (D) are intended to be observed in a given month
   (end May-June, July, August & September respectively). However we emphasise
   that if this isn't possible in a given month due to poor weather or technical problems,
   we request that the observation be taken later in the semester whenever possible.
   This is because although such an observation will not be optimal for detecting long
   period binaries it *will* be useful for both identifying short period binaries with
   periods of a few days and also placing constraints on their radial velocity curves.
   
  
  Runs (E) & (F), intended to constrain the radial velocity curves of the brighter
   binaries each comprise 2 short (~32mins) OBs and may be slotted in whenever possible
   in the semester, although if possible separated by a few days from any other observations
   (although if not possible any data would be very valuable). We summarise these constraints
   below.
  
  Run (A) - optimal end-May - June, otherwise July-Sept.
  Run (B) - optimal July, otherwise Aug-Sept.
  Run (C) - optimal August, other wise Sept.
  Run (D) - optimal Sept.
  Run (E) - any time during semester
  Run (F) - any time during semester
  
  If possible we require that runs are always separated by a minimum of a few days
   from any other observations  to maximise the likelihood of detecting radial velocity
   shifts, but would rather data were taken if this were not possible.
  
  Finally, if possible we would request that the 4 OBs  in each run (A) - (D) be carried
   out on the same night, and if this isn't possible with as long as possible separation
   from other executions of the same target configuration (field1 - field4;  given
   in the OB name)
   in order to maximise the baseline for long period binaries (again subject to the
   fact that any observation is better than none!).
  
  For the two OBs in each of runs (E) & (F) there are no constraints on when these
   are taken beyond those described above - we assume these will be slotted in whenever
   there is space in the service queue

Special Execution Requirements

• None

Special Calibration Information

• None

ToO Information

• None

ToO Activators List

• None

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• none

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