README web version of /home/usg/OPS/MTS/readme_xml/readme_81505600
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
The aim of this program is to obtain CRIRES high resolution spectra of
H2 1-0S(1) emission at 2.12 micron with the wave-ID 27/1/n (2117.7 nm)
H2 1-0S(0) emission at 2.22 micron with the wave-ID 25/-1/n (2236.1 nm)
H2 2-1S(1) emission at 2.24 micron with the wave-ID 25/-1/i (2242.8 nm)
and the CO ro-vibrational lines at the 4.7 microns employing two waveIDs:
(12/1/n and 11/-1/n),
of the T Tauri star V1647 Ori.
This star is at the beginning of new outburst period.
The observations
(i) are WITHOUT AO.
(ii) employ a NS slit of 4",
(iii) use chopping and nodding in the slit.
The observations start by acquisition, thereafter each wavelength ID is observed.
In total we observe five wave ID settings. Before each waveID setting a wavelenght
calibration observation is requested (except for settings at 4761.0 and 5034.8 nm
because there is no suitable lamp).
V1647 Ori has K mag =7-10 (it is a variable star) the expect S/N/pixel is 200-20
V1647 Ori is the brightest IR source in the 30" vicinity of the given 2mass coordinates.
There is a nebulae north of the object (see attached image).
The observation of a spectrophotometric standard star (HIP 26594) is required immediately
preceding or
following the science observations. We provide the OB STD_V1647Ori_CRIRES_epochXX
for this.
HIP 26594 has K=4.8 we expect a S/N/pixel of 300 @ 2121.8 nm
IMPORTANT: scheduling (!)
Monitoring observations:
The run consist of four (4) observations spaced 1.5+-0.5 months:
The first one should be executed as soon as possible (October) (note NOV 19: partially
executed in the 21/22 oct night)
The second should be executed in November-December (note NOV 19: executed in the
17/18 Nov night)
The third should be executed in January-February
The fourth should be executed in February-Mars
Quasimultaneous FORS2 observations (within few days after CRIRES observations) should
be executed (proposal run C)
NOTE (added 19 NOV): in the proposal observations in 3 epochs were requested,
but, data from october (epoch 1) was incomplete (telluric standard observation was
not completed).
For this reason a fourth epoch (observation on February-Mars) was added to the program.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Monitoring observations:
IMPORTANT: scheduling (!)
The run consist of four (4) observations spaced 1.5+-0.5 months:
The first one should be executed as soon as possible (October, OB V1647Ori_CRIRES_epoch1)
(partially executed night 21/22 oct)
The second should be executed in November-December (OB V1647Ori_CRIRES_epoch2) (executed
night 17/18 nov)
The third should be executed in January-February (OB V1647Ori_CRIRES_epoch3)
The fourth should be executed in February-Mars (OB V1647Ori_CRIRES_epoch4)
Quasimultaneous FORS2 observations (within few days after CRIRES observations) should
be
executed (proposal run C)
Special Execution Requirements
Special Calibration Information
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:26 2009
If you have comments, please contact usd-help@eso.org