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

Principal Investigator Email Address

• Jonay.Gonzalez-Hernandez@obspm.fr

Estimated Total Execution Time (hours, including overheads)

• 1

General Description

• This 1hr OB is submitted as RRM compensation time for the UVES visitor
   program
  080.D-0333(A). We request a 3005s observation of star CS22876-032 
  (v=12.84) with the same setup used in the visitor run:
  
  Image Slicer #3 (IS#3:high resolution is required); UVES red arm (we need both the
   
  Mg b line at ~5184A and the Li resonance line at ~6708A).
  Template adopted: UVES_red_acq_imsl and UVES_red_obs_exp.
  As we need IS#3 observations, the slit position is not indicated in the finding
   chart.
  
  We aim at a S/N~133@6710A (i.e. at the Li resonance line).
  Grey time is requested as in the proposal,
  0.4 of fractional moon illumination is the average FLI in 
  the 4 days awarded for the visitor run (16-19 October).
  Gray time is required as we are looking for a signal corresponding to 
  1/700 of the light of the star at the wavelength 6707.8A. 
  This corresponds to a magnitude of mV  19-20 for the sky for a mV = 13 star.
  Therefore we need a grey sky. 
  
  Please, check the *Image Slicer Alignment* before the observations:
  during our first observing night the IS was found not aligned. 
  
  Check also the exposure meter during the observation.
  When observing the target at +-2HA a significant drift of the object 
  was noted at the end of the exposure: 
  a cut through the frame revealed several times a not centered slicer profile.
  Therefore, if you notice that the counts are constantly decreasing in the 
  exp meter during the observation then apply an offset to the 
  telescope to recover the higher counts. Please, check the centering 
  of the slicer profile on the frame after the observation and the S/N achieved 
  around 6710A.
  
  Note, that the submitted OB is already cached on the mountain with 
  the same name (but a different exposure time).
  When importing the OB in the p2pp I had the following warning 
  which should not be relevant (observation were performed 
  from OBs created with the same version of the p2pp):
  
  CS22876-032.obx was successfully imported but has the following warnings
  Warning the following parameters were not imported for UVES_red_acq_imsl
  TEL.TARG.ADDVELALPHA
  TEL.TARG.ADDVELDELTA
  
  Please, send any observation related communication to both the PI 
  (Jonay.Gonzalez-Hernandez@obspm.fr) and to Lorenzo Monaco (lmonaco@eso.org). 
  
  Thank you!
  
  ciao, Lorenzo

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• Gray time is required. Please, check (1) the IS#3 alignment and 
  (2) the exposure meter during the exposure. 
  When observing the target at +-2HA a significant drift of the object 
  was noted at the end of the exposure: 
  a cut through the frame revealed several times a not centered slicer profile.
  Therefore, if you notice that the counts are constantly decreasing in the 
  exp meter during the observation then apply an offset to the 
  telescope to recover the higher counts. Please, check the centering 
  of the slicer profile on the frame after the observation and the S/N achieved 
  around 6710A.

Time-Critical Aspects

• No time critical aspects.

Special Execution Requirements

• ---(Empty)---

Special Calibration Information

• ---(Empty)---

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 specified the S/N ratio at given wavelength in the User Comments
 field of each OB?

• 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

If you need secondary guiding, are there suitable objects within 30 arcsec
 from your target ?

• N/A