Principal Investigator Email Address
jorma.harju@helsinki.fi
Estimated Total Execution Time (hours, including overheads)
11.0
General Description
The program aims at the detection of H2 S(1), H2 S(0), CO(2-0), and H3+
R(1,0)& R(1,1) doublet in absorption
against background stars. The reference wavelengths are 2123.40, 2236.1, 2340.0,
and 3646.3 nm.
The targets in priority order, and the telluric standards which should be observed
before or after the target are:
1. J172241-270504 & HIP84970
2. CK-2 & HIP88149
3. J162923-241359 & HIP84970
The corresponding OBs are named J17_H2_S1 & CAL_J17_H2_S1, etc .....
CK2_H2_S1 & CAL_CK2_H2_S1,
etc ....
J16_H2_CO & CAL_J16_H2_CO,
etc ....
In the proposal J16... was supposed to be observed with 0.2" slit, but this has
been changed to 0.4" because
of the overheads due to nodding are longer than anticipated. The nodding position
is changed every 5
minutes for the 2123.40, 2236.1, and 2340.0 settings, and every 3 minutes for the
3646.3 nm setting.
Waiver Requests
Our waiver request for a free wavelength setting of 2340.0 nm was approved
Critical Observing Condition Constraints
Nothing to add to what is said in the the Constraints box
Time-Critical Aspects
None
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?
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?