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

Principal Investigator Email Address

• lpodio@cp.dias.ie

Estimated Total Execution Time (hours, including overheads)

• 10:58:10.000

General Description

• DESCRIPTION:
  The observing run consists in spectroscopic observations (SWS-MR, 0.3" slit) of
   5 young accreting stars.
  Each target will be observed in two perpendicular slit positions and in two spectral
   ranges (central wavelengths 1.09 and 1.27 um), except TH 28 and V536 Aql which will
   be observed only at 1.09 um.
  
  AIM:
  These observations will be used to perform a spectro-astrometric analysis of both
   permitted (HeI 10830Ang, Pa-beta, Pa-gamma) and forbidden ([FeII]1.257 um) lines
   in order to disentangle the accretion and wind contribution in their profiles.
  If there is a wind emission, in fact, this will be spatially extended.
  Spectro-astrometry will allow us to highlight extended emission down to few mas,
   i.e. below the seeing limit, and thus to detect jets on very small spatial scales.
  
  OBSERVATIONAL REQUIREMENTS:
  To apply spectro-astrometry we require a good seeing (<0.8"), a high signal-to-noise
   ratio (S/N>10), a good spectral and spatial sampling and a good tracking during
   the observations.
  In order to derive the PA of the micro-jets we need TWO PERPENDICULAR SLIT POSITION
   for each target (one parallel and one perpendicular to the direction of previously
   observed large scale jets).
  Thus the priority is to complete the OBs relative to the two slit positions on a
   given target before proceeding with another target.
  
  SPECIAL REQUIREMENTS:
  To compare the spectro-astrometric signal in the different lines and to compute
   the flux ratios it is important to obtain CONTIGUOUS OBSERVATIONS IN THE TWO SPECTRAL
   RANGES (1.09, 1.27um) to avoid variations of the slit alignment, of the general
   observational conditions (e.g., seeing, airmasses), and of the lines fluxes and
   profiles due to source variability. 
  A waiver request was submitted and accepted to use two central wavelengths in the
   same OBs (execution time 1.2h).

Waiver Requests

• Waiver Requests:
  
  1) OBs longer than 1 hour and with two central wavelengths (submitted 6 Feb, accepted
   7 Feb).
  AIM: to observe each target, with the same slit and PA, in two different spectrocopic
   ranges (1.09 and 1.27um).
  REASONS: (i) to compare the spectro-astrometric signal of the different lines we
   need the same instrumental setting (e.g. slit aligment) and similar observational
   conditions (e.g. seeing, airmasses); (ii) to infer accurate flux ratios we need
   to minimize flux variations due to instrumental/weather variations and source variability.
  
  2) pre-imaging with very low DITs (submitted 7 Feb, accepted 10 Feb).
  REASONS: the targets are very bright (up to magJ=6.9). Thus very short DITs are
   required to avoid saturation.

Critical Observing Condition Constraints

• seeing < 0.8"

Time-Critical Aspects

• No

Special Execution Requirements

• The priority is the completion of all the OBs on a given target before
   proceeding with another target.
  The priority of each target is indicated in the relative OBs.
  
  The aim of the proposal is to observe the HeI 1.08 um line, the Pa-beta and Pa-gamma
   lines and the Fe[II] 1.25 um line. Thus these lines should not saturate. We require
   a check after the acquisition of the first spectrum and, if the lines saturate,
   a lower DIT should be adopted.

Special Calibration Information

• No calibration OBs are submitted.
  Anyway, there are some preferences in the choice of the telluric standards that
   might be taken into consideration during the execution of the Observatory's Calibration
   Plan.
  
  The telluric with the following carachteristics are preferred:
  (i) earliest spectral type: O type (O9.5V, O9V, O6-O8V, O9I), early B type (V or
   I);
  (ii) telluric without emission lines (e) or peculiarities (p);
  (iii) the same telluric in the two spectral ranges (central wavelength 1.09, 1.27um);
  (iV) telluric whose J magnitude is known.

ToO Information

• No

ToO Activators List

• No

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• The slit has to be centered on the target and rotated according to the
   given PA.
  This is the PA of large scales jets associated to the selected sources.
  Anyway these jets are not in the FOV of the camera. 
  Thus the only way to align the slit is by using the given PA.

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

If you submitted OBs for standard stars, did you use the provided StandardStar
 templates ?

• N/A

If you are using a specific offset pattern or position angle, did you
 check carefully the definition in the manual ?

• YES

If you are doing spectroscopy, did you draw the slit on the Finding Charts
 ?

• YES

Did you enter the magnitude of the brightest star in the field-of-view
 in the 'Instrument Comments' field of each OB ?

• YES

If you use the MoveToPixel acquisition, have you given clear instructions
 on the FC and in the OB comment section as to how the field should be centered ?

• N/A