README web version of /home/usg/OPS/MTS/readme_xml/readme_80035101

Principal Investigator Email Address

• cusano@tls-tautenburg.de

Estimated Total Execution Time (hours, including overheads)

• 1.5h

General Description

• We would like to observe the spectroscopic binary BS_Indi with AMBER.
   The two components have an average separation of 40 mas, and can thus be resolved
   with AMBER. BS_Indi has a magnitude in the K band of 6.6, it thus has to be considered
   a rather faint object for AMBER, quite close to the limiting magnitude of the instrument.
   Thus in order to detect the fringes it is presumably necessary to use an integration
   time of 50 msec. Thus, please carry out the observation with this integration time
   long enough to detect the fringes. With the standard integration time of 25 msec
   it will presumably not be possible detect the fringes.  Since it is not possible
   to specify the correlation time in the proposal but only the seeing, we asked for
   0.8 arcsec seeing for BS Indi, because under good seeing conditions the
  correlation time is usually also long. Thus, we ACTUALLY DO NOT NEED 0.8 arcsec
   seeing, we simply need wheather conditions that are good enough to detect fringes.
   See "Special Calibration Information" for informations about our calibrator HD207043.

Waiver Requests

• ---(Empty)---

Critical Observing Condition Constraints

• As pointed out above, with a K-magnitude of 6.6 this star has to be considered
   as faint for AMBER. It is thus presumbly necessary to use an integration time of
   50 msec for detecting the fringes. Since long correlation times usually come with
   good seeing conditions, we requested a seeing of <= 0.8 arcsec. However, we actually
   do not need 0.8 arcsec. What we really need are wheather conditions that allow to
   detect the fringes of BS Indi. The observation can
  be done also under worse weather and seeing conditions, as long as fringes are detected.

Time-Critical Aspects

• The observation should be done between October and December, when the
   object is visible.

Special Execution Requirements

• ---(Empty)---

Special Calibration Information

• The visibility calibrator choosed (HD207043) is not in the CalVinc database.
   HD207043 has a magnitude in the K band of 6.05, it is a G5V
  star and it is located at a distance of 34 pc. The angular diameter of the star,
   assuming a physical solar diameter given the spectral class, should be 0.27mas.
   The star is not resolved by the choosed baseline configuration and we think than
   we can use it as a calibrator comparing the observed visibility to that one of a
    point source.

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• ---(Empty)---

Source(s) of Pre-imaging

• ---(Empty)---

Pre-imaging sources not listed above

• ---(Empty)---

Do all your OBs comply with the instrument-specific requirements listed
 on the instrument-specific Phase 2 web page ?

• YES

If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
 Category for each Observing Template ?

• N/A

Do all your finding charts comply with both the general and instrument-specific
 Phase 2 Web Pages ?

• YES

If you submitted OBs for standard stars, did you specify the magnitude
 and spectral type of all standard stars in the OBs ?

• YES

Have you included OBs for any calibrations that you need but which are
 not part of the Calibration Plan ?

• N/A

If you are observing Moving Targets, have you attached suitable ephemeris
 files to your OBs?

• N/A

If you have preferences which OBs should be executed first, did you make
 use of the User Priority field in the OBs ?

• N/A

If this is a run that requires coordinated observations with other facilities,
 did you give proper instructions in the Time-Critical Aspects Section ?

• N/A

Did you indicate for each science star OB the corresponding calibrator
 star OB (and vice versa) in the 'Instrument Comments' field ?

• YES

Did you check that your chosen calibrator is bright enough for the instrument
 mode used ?

• YES

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 ?

• YES

Do you use the same DIT for pairs of science target and associated calibrator?

• YES

Are the magnitudes of science target and calibrator within +/- 1 mag
 ?

• YES

Did you verify that your coordinates are as accurate as possible (2Mass
 coordinates recommended) and that they include proper motions if available ?

• YES

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 ?

• YES