README web version of /home/usg/OPS/MTS/readme_xml/readme_81026201
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
Run B is a carryover from period 81, and the goal of the program is to
obtain *spatially-resolved* spectra of Eta Carinae and its inner nebula during the
periastron passage of the companion (2009 January 11 +- 1.3 days). Only a J-band
finding chart is provided for Eta Car, since the target morphology is very similar
in the K-band, i.e., a bright central star surrounded by an extended bipolar nebula
(~16 arcsec). The CRIRES slit should be centered on the bright central star, and
the PA should be 325 degrees (which does not correspond to the major axis of the
nebula). A 1-sec exposure should be made in order to not saturate the spectrum from
the central star. A large NDIT will be used to build up enough S/N. Longer exposures
of 45--60s, at offset positions from the star, will be made in order to trace the
morphology of the wind-wind collision zone in the inner arcsecond. Each Eta Car
OB should be immediately followed by the respective calibration OB.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Dramatic changes in the line strengths and radial velocities are expected
to occurr due to the periastron passage of a massive companion. The run B data will
be directly compared to our pre-periastron data from 2007 and 2008 (run A), and
the scientific results of our program will be maximized if run B is observed in
the range 2008 December 25th until 2009 January 25. Therefore, we greatly appreciate
if run B could be observed in this time interval.
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:23 2009
If you have comments, please contact usd-help@eso.org