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

Principal Investigator Email Address

• rmennick@astro-udec.cl

Estimated Total Execution Time (hours, including overheads)

• 10 hours

General Description

• This observing run is aimed to explore the nature of the eclipsing close
   binary V393 Sco. Two periodicities should be well sampled: the orbital periodicity
   (7.7 days) and the long periodicity of unknown nature: 252 days. 
  
  The Finding Charts for Science Target (V393Sco) and Telluric template (Hip087370)
   are in optical wavelengths, due that we could not receive a J-band image from 2MASS
   or other infrared image database. However, the stars are so bright, that it is impossible
   to make an error in its identification; the stars are far the brightest sources
   in their fields in any wavelength.
  
  S/N expected for Target and Calibration about 350 and 450 respectivelly at 1083nm,
   as said in the OB "instrument comments" field

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• N/A

Time-Critical Aspects

• V392 Sco has good observability during all semester (April-September,
   more than 180 days, about 70% of the long period). We ask for three
  sub-runs (chunks) each 7-days long (ONE (OB-science+OB-calib)  PER NIGHT) repeated
   every two months (April-May, Jun-July, August-September). With that schedule we
   can obtain optimal 
  data for science. If it is possibe,  get CRIRES observations the same night that
   UVES observations specified in service mode run 081.D-0457(B); this quasi-simultaneous
   scheme is ideal, but can be relaxed: if we get at least some of the observations
   the same nights is good and if even this is not possible our program can be run
   with non-simultaneous CRIRES-UVES observations.
  
  Some questions posted by the staff of the User Support Department (Ferdinando Patat)
   regarding time critical aspects are replied below:
  
  We propose a minimum time separation between chunks
  of 2 weeks and  each chunk one week long.
  
  Ideally, once a chunk is started, the 7 (science OB + calib OB) that are included
  must be executed at a rate of one per day during 7 subsequent
  nights.
  
  In the case of interruption of a sequence by any reason,
  the sequence can be re-started at any time in the 2-month window,
  but hopefully as soon as possible.
  
  In the case that the service mode runs last less than
  7 consecutive nights, we propose to continue with the
  sequence when the new service mode run starts. Each chunk
  should be one week long, ideally.

Special Execution Requirements

• ---(Empty)---

Special Calibration Information

• We are requesting one telluric spectrum per science OB

ToO Information

• N/A

ToO Activators List

• N/A

Do the README file and the instrument comments of the telluric stars
 OBs include the required S/N/pixel of the spectrum of the telluric star, its spectral
 type and allowed spectral range?

• YES

Do any OBs include wavelength or flatfield calibrations?

• NO

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

• N/A

If the slit viewer guide star is different from the target, are the RA
 and DEC offsets accurate to within 0.05 arcsec and do they take into account the
 relative proper motion between the two objects?

• N/A

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

• N/A