README web version of /home/usg/OPS/MTS/readme_xml/readme_79077800
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
This project aims at observing massive accretion disks in the CO fundamental
band at 4.6mum with AO. 4 sources have to be observed in two spectral setups to
cover the whole fundamental band. To achieve the necessary S/N ratio several OBs
have to be executed for most targets (SCI_IRAS18162-*, SCI_IRAS18151-* and SCI_G309.92-*),
only one source has a single OB (SCI_AFGL4176). Each science OB has a corresponding
calibration OB (CAL_*) as described in each OB. Since each science OB takes approximately
1 hour, calibration would be done at similar intervals. This approach is necessary
if the OB will be executed over many nights. However, if the science OBs will be
executed many in a row within a single night, we prefer to do the calibration only
every 2-3 hours and spent correspondingly more time on the targets. Depending on
weather and seeing conditions, these descision can please be taken by the operator.
The choice of the calibration stars and times were directed to achieve at least
the same S/N ratio or better than the corresponding science targets to assure that
the calibration does not decrease the science S/N ratio.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Special Execution Requirements
To achieve the necessary S/N ratio several OBs have to be executed for
most targets (SCI_IRAS18162-*, SCI_IRAS18151-* and SCI_G309.92-*), only one source
has a single OB (SCI_AFGL4176). Each science OB has a corresponding calibration
OB (CAL_*) as described in each OB. Since each science OB takes approximately 1
hour, calibration would be done at similar intervals. This approach is necessary
if the OB will be executed over many nights. However, if the science OBs will be
executed many in a row within a single night, we prefer to do the calibration only
every 2-3 hours and spent correspondingly more time on the targets. Depending on
weather and seeing conditions, these descision can please be taken by the operator.
The choice of the calibration stars and times were directed to achieve at least
the same S/N ratio or better than the corresponding science targets to assure that
the calibration does not decrease the science S/N ratio.
For a better orientation of the calibrator HR4731, we added a 2nd finding chart
with an AO coronographic image (obtained with the ESO 3.6m telescope + ADONIS, Tokovinin
et al. 1999). Please observe the central brightest component.
Special Calibration Information
To achieve the necessary S/N ratio several OBs have to be executed for
most targets (SCI_IRAS18162-*, SCI_IRAS18151-* and SCI_G309.92-*), only one source
has a single OB (SCI_AFGL4176). Each science OB has a corresponding calibration
OB (CAL_*) as described in each OB. Since each science OB takes approximately 1
hour, calibration would be done at similar intervals. This approach is necessary
if the OB will be executed over many nights. However, if the science OBs will be
executed many in a row within a single night, we prefer to do the calibration only
every 2-3 hours and spent correspondingly more time on the targets. Depending on
weather and seeing conditions, these descision can please be taken by the operator.
The choice of the calibration stars and times were directed to achieve at least
the same S/N ratio or better than the corresponding science targets to assure that
the calibration does not decrease the science S/N ratio.
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:20 2009
If you have comments, please contact usd-help@eso.org