README web version of /home/usg/OPS/MTS/readme_xml/readme_80015000
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
Observations consist of the time resolved spectroscopy of the rapidly
pulsating A star. Data are to be obtained on 4 different nights, for 2.5-3 hours
each night. There are 4 similar observing blocks. Each consists of 129-155 science
exposures and one attached wavelength calibration.
The two higher priority OBs (hr3831_A and hr3831_B) should be executed at specific
nights in order to cover certain rotation phases of the star. This information cannot
be entered in "time intervals" field of OBs because the number of suitable nights
exceeds 5. Instead, we give the list of suitable nights for each OB in "Time-Critical
Aspects". This information is repeated in "Special Execution Requirements".
The two lower priority OBs (hr3831_C and hr3831_D) can be executed on any night.
Waiver Requests
The total length of each OB is 2.5-3 hours (waiver request submitted 25-07-2007,
ID: 080.D-0150A.01, approved 31-07-2007).
To maximize the duty cycle we are using fast readout mode "625kHz,4ports,low gain"
(waiver request submitted 25-07-2007, ID: 080.D-0150A.01, approved 31-07-2007).
Critical Observing Condition Constraints
We accept the risk of degrading observing conditions (seeing, sky transparency)
after first hour of OB execution. However, OB execution has to be started sufficiently
early during the night so that last scientific exposures are obtained when the star
is at airmass<2.0.
Time-Critical Aspects
Due to the length of OBs (2.5-3h), observations have to be obtained during
the period when the star is above airmass 2.0 longer than the toal length of one
OB. This period starts around 2008-01-01 and lasts until the end of Period 80.
The two lower priority observing blocks (hr3831_C and hr3831_D) can be executed
on any night.
The two higher observing blocks (hr3831_A and hr3831_B) should be executed at particular
rotation phases of the star. Suitable dates (corresponding to the beginning of the
night, Chilean time) are
For hr3831_A:
2008-01-03
2008-01-06
2008-01-17
2008-01-20
2008-01-23
2008-01-26
2008-02-06
2008-02-09
2008-02-12
2008-02-15
2008-02-26
2008-02-29
2008-03-03
2008-03-06
2008-03-17
2008-03-20
2008-03-23
For hr3831_B:
2008-01-07
2008-01-10
2008-01-13
2008-01-16
2008-01-27
2008-01-30
2008-02-02
2008-02-05
2008-02-16
2008-02-19
2008-02-22
2008-02-25
2008-03-04
2008-03-07
2008-03-10
2008-03-13
2008-03-24
2008-03-27
2008-03-30
Special Execution Requirements
We ask to avoid, if possible, interruptions in OB execution.
The two lower priority observing blocks (hr3831_C and hr3831_D) can be executed
on any night.
The two higher priority observing blocks (hr3831_A and hr3831_B) should be executed
at particular rotation phases of the star. Suitable dates (corresponding to the
beginning of the night, Chilean time) are
For hr3831_A:
2008-01-03
2008-01-06
2008-01-17
2008-01-20
2008-01-23
2008-01-26
2008-02-06
2008-02-09
2008-02-12
2008-02-15
2008-02-26
2008-02-29
2008-03-03
2008-03-06
2008-03-17
2008-03-20
2008-03-23
For hr3831_B:
2008-01-07
2008-01-10
2008-01-13
2008-01-16
2008-01-27
2008-01-30
2008-02-02
2008-02-05
2008-02-16
2008-02-19
2008-02-22
2008-02-25
2008-03-04
2008-03-07
2008-03-10
2008-03-13
2008-03-24
2008-03-27
2008-03-30
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:20 2009
If you have comments, please contact usd-help@eso.org