README web version of /home/usg/OPS/MTS/readme_xml/readme_75020601
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
* This programme has the aim to use UVES/FLAMES/Giraffe to measure radial
velocities for two
detached eclipsing binaries in the open cluster NGC 2506 and determine membership
information for other stars in the field from radial velocities.
*The programme consists of 10 OBs. The execution order is determined by the 'Priority'
section of each OB.
* All coordinates (target stars, guide and FACB) are given in the UCAC2 system
and should
be accurate to better than 0."1
*Finding charts produced with SKYCAT are attached to each OB.
*Each Target Setup file has been checked (with FPOSS) for validity in the +-4h.
*Please see 'Special Execution Requirements' section for a description of possible
observing dates and sequencing.
Magnitudes, Guide-Stars and S/N
-----------------------------------
We have 4 different setups in the OBs, called NGC2506-Setup[0-3]-Expnumber.
Guide star: All four setups use the same VLT guide star: UCAC2-28000650, with
R_ucac2= 11.9
FACB stars:
Setup 0, 1, 2 all use the same FACB stars:
OOPS there seems to be no more space in this field.... please see the remainder
in ** Special Calibration Information **
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
The primary objects for this project are detached eclipsing binaries in
the open
cluster NGC 2506. We have two primary targets, and need to observe these at specific
phases. Furthermore the RA and DEC for NGC 2506 is such that we can only observe
in
April and early May.
Please see description in 'Special Execution Requirements' for observing dates
and
sequencing.
Special Execution Requirements
This programme has 10 OBs.
There is a total of 4 different FLAMES setups called :
NGC2506-Setup0
NGC2506-Setup1
NGC2506-Setup2
NGC2506-Setup3
It is obly possible to observe this object in April and early May.
At the end of this section we give a number of possible observing dates for the
programme.
For each day there is the constraint that the objet has to be observed within
+-4h of the
meridian, which for this object means that for all the given dates the observing
window
extends from sunset until the object is approx. 2.5h past the meridian (since
an observing block lasts
1.75h), and the FLAMES configuration has been checked for +-4 hours.
We ask that the OBs are executed in order like this:
OB NAME SETUP
1 NGC2506-Setup0-1 NGC2506-Setup0
2 NGC2506-Setup1-1 NGC2506-Setup1
3 NGC2506-Setup2-1 NGC2506-Setup2
4 NGC2506-Setup3-1 NGC2506-Setup3
5 NGC2506-Setup0-2 NGC2506-Setup0
6 NGC2506-Setup1-2 NGC2506-Setup1
7 NGC2506-Setup2-2 NGC2506-Setup2
8 NGC2506-Setup3-2 NGC2506-Setup3
9 NGC2506-Setup0-3 NGC2506-Setup0
10 NGC2506-Setup1-3 NGC2506-Setup1
We do not have any special preference for any of the dates given below, only
that
once the programme is started the sequence of setups given above is kept.
Only one OB should be executed per night.
The first column gives the starting day for the night, the second the month and
the third the year.
So the first line means the night starting in the afternoon of April 2nd 2005
etc. ......
The possible observing dates are:
D M Year
20 03 2005
23 03 2005
25 03 2005
28 03 2005
29 03 2005
30 03 2005
The 6 lines above were added on Thursday March 17, by Frank Grundahl.
02 04 2005
04 04 2005
05 04 2005
07 04 2005
08 04 2005
10 04 2005
12 04 2005
14 04 2005
15 04 2005
17 04 2005
18 04 2005
20 04 2005
23 04 2005
24 04 2005
25 04 2005
27 04 2005
28 04 2005
30 04 2005
ADDED ON MAY 10
THE FOLLOWING DATES ARE ALSO A POSSIBILITY (VERY FIRST THING IN EVENING)
THE TWO FIRST DATES ARE THE BEST.
NIGHT OF MAY 12/13
MAY 13/14
MAY 15/16
MAY 17/18
MAY 19/20
03 05 2005
04 05 2005
05 05 2005
Special Calibration Information
Magnitudes, Guide-Stars and S/N
-----------------------------------
We have 4 different setups in the OBs, called NGC2506-Setup[0-3]-Expnumber.
Guide star: All four setups use the same VLT guide star: UCAC2-28000650, with
R_ucac2= 11.9
FACB stars:
Setup 0, 1, 2 all use the same FACB stars:
UCAC2 - 27999958 R_ucac2 = 13.69
UCAC2 - 28000498 R_ucac2 = 13.92
UCAC2 - 28000340 R_ucac2 = 13.96
UCAC2 - 27999914 R_ucac2 = 13.59
Setup 3:
UCAC2 - 28000114 R_ucac2 = 13.15
UCAC2 - 28000498 R_ucac2 = 13.92
UCAC2 - 28000340 R_ucac2 = 13.96
UCAC2 - 27999906 R_ucac2 = 12.55
S/N
Nearly all stars are brighter than V=15.5. For these we expect a S/N of 30 or
above per exposure for the instrument setting (HR14A) and 2700s exposure time.
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 ?
Did you specify in your OBs the hour angle range for which your Target
Setup files are valid ?
Did you specify in your OBs the magnitudes of FACBs and Guide Star for
all your fields ?
Are the FACBs and Guide Star in the brightness ranges specified in the
FLAMES manual ?
Did you enter the expected signal to noise in your OBs ?
Last creation of page: Tue Oct 6 15:40:07 2009
If you have comments, please contact usd-help@eso.org