README web version of /home/usg/OPS/MTS/readme_xml/readme_83082401
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
This is a spectroscopic run for only one target (binary brown dwarf) in
the Ks filter. The brighter component Kelu1 A has K=12.32 and the fainter component
K=12.75. Since the target is too faint in R-band we will use 2MASS 130539-254129
(S201113311069) as AO guide star (R=14.5) as well as SVGS (K=12.13), coordinates
are for Epoch 2000.0
Acquisition:
------------
ATTENTION:
Due to the relatively large offset between our target and the SVGS the binary components
need to be moved slightly upwards in the slit, so that target and SVGS fit on the
slit view detector. Therfore we calculated a Pointing position(= no real target)
between target and SVGS which should be placed in the center of the slit. The corresponding
coordinates are provided in the target box of the OB. This should also lead to the
alignement of both!! target binary components in the slit during acquisition. If
this procedure works out there should be still ~8.3" distance between Kelu-1 and
the upper end of the detector which would provide enough space for the given noddthrow.
To fit both Kelu-1 components in the slit, the position angle of the slit has to
be 42.9 degrees! PLEASE make shure that both! binary components stay in the slit
during the whole observation!!!!!
The coordinates for the target Kelu-1 AB calculated for Epoch 2009 are
RA: 13 05 40.007 and DEC: -25 41 06.7
and are also provided on each Finding Chart. Kelu-1AB is a higher proper motion
object with pmRa ~0.285"/yr and pmDEC ~0.03"/yr (also provided in the target box).
The offset calculated between target and SVGS for Epoch 2009.0 will be ~ -12.39"
in RA and -22.5" in DEC. Depending on the time of observation the RA/DEC offsets
will slightly change. PLEASE always! verify after aligning the given Pointing position
in the slit center, that both Kelu-1 components are really in the slit!
We provide 3 Finding Charts (including a 2'x2' and a magnified one) for the science
OBs with all relevant coordinates and the slit orientation. The red dot on the slit
shows the calculated Pointing Position and should correspond to the slit center
as given in the manual.
OBSERVATION:
------------
We will use the 25/1/i wavelength setting (central wavelength= 2293.2nm) with the
0.2" slit. With a separation of the binary components of ~0.38" it should be possible
to spatially resolve the 2 spectra. For a sufficient accuracy of our RV measurement,
a S/N ratio ~30 for the fainter component Kelu1 B is required. To achieve a very
precise RV determination we will use simultaneously the N2O gas-cell as a wavelength
reference. Additionally we will observe 1 nodding cycle without the cell to receive
a reference template. The same principle will be performed during the calibration
OB for a telluric standart.
PLEASE be also aware about the critical observing condition constrains and the special
calibration information for this run!!! (As described therein)
Beside our own telluric standart calibration OB, normal standart calibration for
bias, arcs and flats provided by ESO are sufficient. Nevertheless, if we could get
one set of flats with the N2O cell infront. That would help a lot with data reduction.
THANK you very much for your support concerning all the different issues of this
run!!!!
Waiver Requests
Critical Observing Condition Constraints
If it should turn out that due to the higher proper motion of the target,
the calculated Pointing position is not accurate enough to aligne both binary components
in the slit and still include the SVGS in the FoV, please feel free to adjust the
parameters accordingly.
If in the end the AO guide star does not work out as SVGS (due to distance to target
and slit orientation), one could also try to use the brighter component of the binary
target (Kelu1 A) as the SVGS (binary component distance = 0.38"). It should be bright
enough (K=12.32). In this case please check carefully if the binary itself prevents
the slit-view system to operate correctly or if it offsets the target from the slit!
If this should also fail, it would be still worth trying to use CRIRES without AO
and the 0.4" slit (adjusting the DITs in the science and calibration OB accordingly!!).
Time-Critical Aspects
Special Execution Requirements
Special Calibration Information
We added a calibration OB:
CAL_telluric_standard to be able to perform telluric correction during data reduction.
We chose the standart HIP 68269 (B8V) with R=5.24 and K=5.38 and a S/N ratio of
159@2293.2nm.
The telluric standard is bright enough to serve as AO and SVGS. Please execute this
OB right after the science OB. Please be aware that the slit orientation has to
be the same as for the science OB (as indicated in the OB). We will obtain (in the
same way as for the science OB) one dataset with the N2O gas-cell and one without
(as reference template).
If possible, please place the telluric standart at the same position on the science
detector as Kelu1 (=science target) in the OB before. This will ease any necessary
correction of the science data.
If it turns out to be necessary to change the telluric standard, a range between
B4-A0 will be acceptable. Nevertheless it is very important!!!! to observe at nearly
the same airmass as the science object.
ToO Information
ToO Activators List
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?
Do any OBs include wavelength or flatfield calibrations?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
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?
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?
Last creation of page: Tue Oct 6 15:40:30 2009
If you have comments, please contact usd-help@eso.org