README web version of /home/usg/OPS/MTS/readme_xml/readme_81000400
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
GENERAL DESCRIPTION
Definition SETUP: one normal setup contains 2 OBs: position star with dic1 and
position star with dic2, or position fos4 with dic1 and position fos4 with dic2.
The observations are OBs which have NOT BEEN EXECUTED IN THE LAST SEMESTER
of the Program 381.D-0004 which is a direct continuation of earlier semesters
programs 070.D-0607(A), 071.D-168(A),072.D-0524(A), 074.D-0141(A),
077.D-0618 and 380.D-0036A. We are monitoring
Eta Carinae continous changes of the spectrum and brightness.
The 4 OBs will be used to follow the so called spectroscopic event
starting around January 11th 2009.
Detailed constrain for observing time are given below in Time-Critical Aspects.
We are obtaining one full spectrum of the star and observe a special
region (FOS4) within the nebula around Eta Car which shows the reflected
stellar spectrum. To peak up on the FOS4 position we are using an
offset star north-east of this position.
A guide star and a finder chart for the guide star is given.
The guide star's designation is U0300_10504917
the position 10:45:12.898 -59:44:19.32 V about 12.1.
Since the object is variable a S/N ratio cannot be given in advance.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Special Execution Requirements
SPECIAL EXECUTION REQUIREMENTS
Since we expect flux and line profiles to change with time, it is important
that a full setup - consisting of 2 OBs (Dic1 and Dic2 for star or FOS4) -
is taken at least within the same night, better right after each other.
With these left-over observation time we are planning to observe Eta Car
during its spectral event around Jan 11th and thereafter.
Since the maximum effect of the spectral changes is expected around
Jan 11 we would like to have the one STAR positions observed close
to that date (if possible +- 2d) and the other about 25 days after that date.
For the FOS4 position we prefer them to be executed 14 days after each
STAR position.
That OBs have been named accordingly
308408 ETA CAR STAR JAN DIC1 should be executed around JANUARY ~11th
308409 ETA CAR STAR JAN DIC2 should be executed around JANUARY ~11th
308406 ETA CAR FOS4 JAN DIC1 should be executed around JANUARY ~25th
308407 ETA CAR FOS4 JAN DIC2 should be executed around JANUARY ~25th
308398 ETA CAR STAR FEB DIC2 should be executed around FEBRUARY ~5th
308402 ETA CAR STAR FEB DIC1 should be executed around FEBRUARY ~5th
308403 ETA CAR FOS4 FEB DIC2 should be executed around FEBRUARY ~19th
308405 ETA CAR FOS4 FEB DIC1 should be executed around FEBRUARY ~19th
Special Calibration Information
ToO Information
ToO Activators List
Is this a Pre-imaging run ?
Pre-imaging Requirements
Source(s) of Pre-imaging
Pre-imaging sources not listed above
Do all your OBs comply with the instrument-specific requirements listed
on the instrument-specific Phase 2 web page ?
If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
Category for each Observing Template ?
Do all your finding charts comply with both the general and instrument-specific
Phase 2 Web Pages ?
If you submitted OBs for standard stars, did you specify the magnitude
and spectral type of all standard stars in the OBs ?
Have you specified the S/N ratio at given wavelength in the User Comments
field of each OB?
Have you included OBs for any calibrations that you need but which are
not part of the Calibration Plan ?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
If you have preferences which OBs should be executed first, did you make
use of the User Priority field in the OBs ?
If this is a run that requires coordinated observations with other facilities,
did you give proper instructions in the Time-Critical Aspects Section ?
If you need secondary guiding, are there suitable objects within 30 arcsec
from your target ?
Last creation of page: Tue Oct 6 15:40:23 2009
If you have comments, please contact usd-help@eso.org