README web version of /home/usg/OPS/MTS/readme_xml/readme_83061300
Principal Investigator Email Address
Jean-Louis.Monin@obs.ujf-grenoble.fr
Estimated Total Execution Time (hours, including overheads)
24h50mn
General Description
This run addresses simultaneous spectroscopy of individual components
in young binaries.
The binaries are tight, with separations between 0.1 and 2.0 arcsec, with a median
separation value = 0.45 arcsec.
For each target, we provide the position angle of the binary in the OB, oriented
from the primary.
The AO and SV guide stars are always the same, this is : the brightest star of every
pair.
The PA is drawn on the finding charts, starting from the primary.
To get the 2 spectra simultaneously, the slit should be oriented along the binary
PA.
In all cases, the OB are designed so that target = AO guide star = SV guide star.
The median K magnitude difference between the primary and the secondary is dK=1.
Hence the AO should be OK on the primary. In some rare cases the 2 stars are of
very similar brightness
but then the separation is very small. Look in the user comments for details on
individual sources.
We will observe at 3 wavelength setting :
Bracket gamma (2166 nm)
Ca I triplet (2263 nm)
CO lines (2293.2 nm)
The first 2 settings above are free settings. We had a waiver approved on this question.
Also, some of our blocks exceed the 1 hour time limit and we also have a waiver
approved on this.
In total, we have 3 waiver approved :
WaiverID: 083.C-0613A.01
WaiverID: 083.C-0613A.02
WaiverID: 083.C-0613A.03
When running the VERIFY process, the verifcation fails but only because of reason
concerning the waivers
here above (exec time > 1 hour and 2 free settings + one on the acquisition).
The observing method should be the following : identify the source from the Finding
chart, and
when the AO loop is closed, one should see the 2 components of the binary.
Then the slit should be aligned along the binary PA (look on the finding chart).
There is one source that is going to be more tricky : ROXs 16 : this is a binary
(AB) with sep=0.6, and
the A component (the brightest one) is itself a binary with sep 0.1''. There should
be 2 observations of this object
at 2 different PA (look at the OB).
If possible, the targets should be observed in the following (priority) order :
Elias 2-26
AS 205
SR 9
Haro 1-4
DOAr 24 E
WSB 3
ROXs 2
V853 Oph
WL 4
YLW 16A 1 & 2
SR 24 N
DOAr 23
ROXs 31
YLW 19
ROXs 16 AB
ROXs 42 C
SR 12
ROXS 5
VSSG 14
ROXs 16 A-ab
IRS 51
For every object, we have chosen DIT values to get a S/N=50 (or so) at 2166nm, and
70 (or so) at 2263 nm and 2293nm.
If the S/N is 20% lower than these values, the observation is OK.
Note that we use a free setting at 2166nm and at 2263 nm (waiver granted). We use
a standard setting at 2293.2 nm.
Calibrations (Telluric) :
We have only 2 Telluric stars situated very close to our targets (they are all gathered
in a small part of the sky, average RA = 16:20, average DEC = -24.
We have duplicated the calibration OBS to put them in the middle of the science
OB list with names CAL_. We use the same PA orientation of the
slit
(SKY position) for the science OB and for the CAL_ star.
The Telluric stars are both A0V stars with V very close to 7. The S/N in 10s should
be of the order of 50 at 2166 and 2263, 2293.2
Waiver Requests
Three waiver requests were submitted and granded :
WaiverID: 083.C-0613A.01
WaiverID: 083.C-0613A.02
WaiverID: 083.C-0613A.03
They concern the use of free wavelength settings and the fact that some OBS are
a bit over 1 hour exec time.
Critical Observing Condition Constraints
No real critical observing constraints are requested. We request the seeing
to be good (0.6'') but not extremely good, because we observe binaries that can
be very
tight and we need the AO correctionto be good.
Time-Critical Aspects
No time critical aspect in term of coordinated observations for instance.
On the other hand, we would like some short science OBs (20-30 mn exec time) to
be performed back to back with only one telluric star to calibrate both, because
20 telluric stars x 20 mn adds 6 hours to our exec time that we did not take into
account at preparation time.
Special Execution Requirements
None
Special Calibration Information
---(Empty)---
ToO Information
---(Empty)---
ToO Activators List
---(Empty)---
Do the README file and the instrument comments of the telluric stars
OBs include the required S/N/pixel of the spectrum of the telluric star, its spectral
type and allowed spectral range?
YES
Do any OBs include wavelength or flatfield calibrations?
NO
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
N/A
If the slit viewer guide star is different from the target, are the RA
and DEC offsets accurate to within 0.05 arcsec and do they take into account the
relative proper motion between the two objects?
N/A
If you have preferences which OBs should be executed first for objects
at similar RA, did you make use of the User Priority field in the OBs?
YES
Last creation of page: Tue Oct 6 15:40:30 2009
If you have comments, please contact usd-help@eso.org