README web version of /home/usg/OPS/MTS/readme_xml/readme_80009500
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
Note added on 18th December 2008 regarding l Car observations in HR mode
of AMBER with FINITO (approved change of mode): this particular observations of
l Car do not have time constraints. We focuse on the Brackett gamma line (2.1655
micrometers) and few metallic lines in the HR wavelength range of AMBER.
-----------
Note added on 12th December 2008 regarding RS Pup observations (approved additional
target): this Cepheid is relatively faint (mK~4), but within the FINITO/AMBER capabilities
as listed on the instrument web page. The P2PP verification prevents us from entering
magnitudes above 3.0 in the corresponding OB fields. The true values are listed
in the "User Comments" field. These particular observations of RS Pup do not have
time constraints. This is fine to try the observation of this star with a seeing
< 1.0 arcsec.
-----------
This run intends to observe with AMBER 3 cepheid stars with their calibrators. Each
star has to be observed 10 times at different pulsation phases. For each star, the
observations are done 1 time at phase around 0.1, 4 times at phase around 0.4, 1
time at phase around 0.7 and 4 times at phase around 0.9.
These observations lead to some time-critical aspects that are explained in the
OBs.
Note added on october 31th:
The time-critical aspects of this program are related to the actual pulsational
phase of the cepheids and not to very specific dates. It means that the date intervals
that have been given for each OB are calculated to match the expected pulsational
phase and thus many dates are possible.
For improving the accuracy on the determination of the angular diameter variation
during the cycle, it has been shown (Nardetto et al.) that 4 points around phase
0.4 and 4 points around phase 0.9 are necessary. These four points should be independant.
They could be done during the same night. They could be done during the same cycle
and on successive nights if the pulsation period is such that the selected phase
interval is respected (for long period it is possible and it has been indicated
in the time intervals of the OB). They could also be done on different cycles and
then the measurements are almost separated by a period.
I hope it helps to clarify and simplify the programmation.
Important note added on 2008 january 30th: To simplify the scheduling, we have relax
our constraints on the actual pulsational phase and accept that the observations
occur at the correct phase +-0.1 and not as set initially (+-0.5). The time intervals
have been changed accordingly in this README file.
Note added on april 24th for the carryover of this program in P81 (convention for
the dates: means the night starting that night)
1) zeta Gem is not observable at all during P81, so all OBs called SCI_zgem... or
CAL_zgem... have to be forgotten.
2) l Car is observable in P81 from april to beginning of july. The interesting dates
for my program are the followings:
lcar_0.1: 16-19 may (4 nights possible), 20-23 june (4 nights possible)
lcar_0.4: 27-29 may (3 nights possible), 01-04 july (4 nights possible)
lcar_0.7: 02-05 may (4 nights possible), 06-09 june (4 nights possible)
lcar_0.9: 09-11 may (3 nights possible), 13-16 june (4 nights possible)
3) bet Dor is observable in september only. The interesting dates for my program
are the followings:
bdor_0.1: 05,15,25 september (3 nights possible)
bdor_0.35: 07,17,27 september (3 nights possible)
bdor_0.6: 31 august, 10,20,29,30 september (5 nights possible)
bdor_0.75: 01,02,11,21 september (4 nights possible)
Waiver Requests
Critical Observing Condition Constraints
A seeing better than 1" is required for accuracy purpose of this demanding
program.
For zeta Gem and its calibrator, due to the high declination, the LST interval is
short and due to the shadowing effects I was not able to find a solution with a
large enough LST interval and and airmass smaller than 1.5 allowing to use FINITO.
Thus, zeta Gem and its calibrator are not prepared with FINITO but if possibilites
arise I would be very grateful because of the global consistency of this program.
Time-Critical Aspects
1) zeta Gem is not observable at all during P81, so all OBs called SCI_zgem...
or CAL_zgem... have to be forgotten.
2) l Car is observable in P81 from april to beginning of july. The interesting dates
for my program are the followings:
lcar_0.1: 16-19 may (4 nights possible), 20-23 june (4 nights possible)
lcar_0.4: 27-29 may (3 nights possible), 01-04 july (4 nights possible)
lcar_0.7: 02-05 may (4 nights possible), 06-09 june (4 nights possible)
lcar_0.9: 09-11 may (3 nights possible), 13-16 june (4 nights possible)
3) bet Dor is observable in september only. The interesting dates for my program
are the followings:
bdor_0.1: 05,15,25 september (3 nights possible)
bdor_0.35: 07,17,27 september (3 nights possible)
bdor_0.6: 31 august, 10,20,29,30 september (5 nights possible)
bdor_0.75: 01,02,11,21 september (4 nights possible)
Special Execution Requirements
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 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 indicate for each science star OB the corresponding calibrator
star OB (and vice versa) in the 'Instrument Comments' field ?
Did you check that your chosen calibrator is bright enough for the instrument
mode used ?
If you use calibrator stars which are not in the CalVin database, did
you specify their characteristics in the README file and in the OBs ?
Do you use the same DIT for pairs of science target and associated calibrator?
Are the magnitudes of science target and calibrator within +/- 1 mag
?
Did you verify that your coordinates are as accurate as possible (2Mass
coordinates recommended) and that they include proper motions if available ?
Did you specify the LST range of the calibrators such that they cover
the range from 30 min before the start of the LST range of the science target to
30 min after the end of the LST range of the science target ?
Last creation of page: Tue Oct 6 15:40:20 2009
If you have comments, please contact usd-help@eso.org