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

Principal Investigator Email Address

• Anne.Dutrey@obs.u-bordeaux1.fr

Estimated Total Execution Time (hours, including overheads)

• 5

General Description

• This run aims at observing one Herbig Ae star (hd100546, young stellar
   object surrounded by a massive protoplanetary dusty disk) and one binary star (SS
   Leporis= Ae+M) surrounded by a circumbinary disk. Both objects should be well resolved
   with the G0-H0 AT baseline. Although the uncorrelated flux of HD100546 is above
   the limiting sensitivity, the correlated flux could drop below the 50Jy limit if
   the source is very resolved. It should not be the case for the very bright SS Lep.
   Calibrator for SS Lep is Sirius (brightest star in the field of view, finding chart
   is given in the N band since the visible images are saturated).

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• no critical observing conditions
  although not defined as an official observing parameter, we would prefer to have
   a coherence time not shorter than 2ms.

Time-Critical Aspects

• no time critical aspect

Special Execution Requirements

• No priority among targets.
  hd100546 :Priority shall be given to the extreme azimuth angles, which corresponds
   to early and late observations of the target.
  SS lep: No priority in the execution of the 2 OBs. Science OB(sslep) shall always
   be executed BEFORE calibrator OB (sirius) due to similitudes in airmass conditions.
   LST constraints indicate that the 2 OBs should not be exectute at the same hour
   angle (prerefably one before and one after transit).

Special Calibration Information

• Science OB(sslep) shall always be executed BEFORE its calibrator OB (sirius)
   due to similitudes in airmass conditions.
  Sirius is very bright in the visible (V=-1.47), this magnitude is not accepted in
   the guiding star mag field although observations with ATs might make the guiding
   possible for such a star (OBs template are designed for UTs !). I have changed the
   magV to "0" instead of -1.47 in order to be able to validate the OB. Default chopping
   throw might also be different for ATs and UTs because of the different field of
   view.

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 ?

• N/A

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 ?

• YES

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

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 ?

• N/A