README web version of /home/usg/OPS/MTS/readme_xml/readme_82505200
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
The star (WR25) we want to monitor is a massive WR+O binary with a period
of 208 days. We already have a nice radial velocity curve except we have a gap at
the moment of the maximum separation in velocities (which is crucial for the orbital
solution determination). The aim of this DDT time is to cover the fast radial velocity
variations that occur between the 19 of March and the 29 of March. One spectrum
every two day would be sufficient. With the science exposure, a wavelength calibration
is necessary. The exposure time is 1800 sec + 15 sec for wavelength calibration
+ overheads. This amounts to about 3/4 hour. We designed 6 OBs to cover the 5 hours
that have been granted. A uniform repartition of the six exposures among the dates
19 to 29 would be the best approach. The six OBs are perfectly identical. They are
labelled EGWRDDT 1 to 6. It would be nice to have about two measurements taken during
the run of Evans et al.. In order to not interfere with this run, we suggest to
observe during the evening twilight (when no SM slot is present).
Waiver Requests
Critical Observing Condition Constraints
For the nights 19-21-23, a visitor mode run is present. Therefore, for
these nights, we suggest to observe WR25 during the evening twilight, just before
the night, in order to minimize the impact on the visiting mode run. For dates later
than 25, night observations are possible and thus requested. Please do not hesitate
to contact me in case of doubt (gosset@astro.ulg.ac.be).
Time-Critical Aspects
The aim is to monitor the radial velocity variations of WR25 in the period
19 March to 29 March. The ideal cover would be to observe on the nights 19-21-23-25-27-29.
However, the first nights in the list do not correspond to SM time. However it would
be nice if you could anyway observe at these dates: the star can be observed during
the evening twilight. It is well positioned and bright enough.
Special Execution Requirements
Special Calibration Information
The observed object is very blue. Usually, the default flats taken in
the framework of the calibration plan are slightly deficient in the far blue (3800-4100).
Therefore, we have difficulties to extract the blue orders due to the bad nature
of the flat. Therefore, it would be useful to have one or a few flats well-exposed
in the blue. This could lead to slight saturation in the red. These flats could
be acquired at any moment during the day.
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 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 ?
Did you set 'New Preset' flag in all acquisition templates to 'True'?
If you use any lamp, did you check that it should never be left on at
the end of any OB?
Last creation of page: Tue Oct 6 15:40:28 2009
If you have comments, please contact usd-help@eso.org