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

Principal Investigator Email Address

• pvdwerf@strw.leidenuniv.nl

Estimated Total Execution Time (hours, including overheads)

• 1h19m27s for each OB of 1612, 1h20m3s for 1714

General Description

• Targets are FAINT (K~20), BIG (~2.5") high z galaxies, which we observe
   at 4 different positions in the 8x8" FOV (--> hence no need for sky positions).
   The bright offset star (K=14.83) must be ACCURATELY CENTERED in the fov because
   the galaxies are so big. Continuum might be visible after subtracting two frames
   and median collapsing, but do NOT worry if no continuum is seen. 
  The observing sequence starts with observing the offset star at the first two positions
   (AB) where the target will be observed, then observing the target at 4 different
   positions (ABCD) and then observing the offset star again at the last two positions
   (CD). Rationale is that based on extensive visitor mode experience we have noticed
   that the target can move significantly on the chip (depending on parallactic angle,
   elevation etc). We correct for this using the star observations during the data
   reduction.
  
  For both targets, two finding charts have been attached. The first ("fc_big_ms1054-XXXX.jpg")
   shows a large area  with the target and offset star. The second ("fc_small_ms1054-XXXX.jpg")
   shows the 8x8 arcsecond fov at the different offset positions on the science target.
   
  
  "Verify" gives a warning that the target moves outside the FOV. IGNORE this warning
   (the target is in the FOV, it the OB structure (first observing a psf star &
   not using the blind offset option) that causes this error. 
  
  notes for individual targets:
  
  MS1054-1714: 
  *** Note the large distance between offset star and target: 70". 
  *** There are two galaxies in de fov, the target 1714 and another high-z galaxy
   which happened to fit in the FOV as well. Therefore, the offset star is observed
   at four (not two) positions before and after the science frames. 
  *** H band is correct (in the proposal it says Ha in K band (based on a phot z),
   but during our GTO run last april we found Ha in H band).
  
  MS1054-1612: 
  *** uses the same offset star as 1714 (not an error)

Waiver Requests

• We have submitted a waiver request on  Fri, 07 Jul 2006, which was approved
   on 14 Jul 2006, requesting
  
  1) have more than once Science template
  2) take up to 1.5 hours to execute.

Critical Observing Condition Constraints

• Seeeing <0.8
  clear sky
  airmass < 2

Time-Critical Aspects

• N/A

Special Execution Requirements

• Complete all OBs on target 1714 before proceding to target 1612

Special Calibration Information

• telluric standard, preferentially a hot star

ToO Information

• no

ToO Activators List

• N/A

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• N/A

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 the magnitude of the brightest object in the field in
 each SINFONI OB?

• YES

If you are using the AO: Did you indicate for every OB the magnitude
 of the guide star, and its distance to the target (if any)?

• 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

Did you make really sure that none of your OBs ever saturates the detector?

• YES

If you are using the AO: did you enter the correct Strehl Ratio (on-axis,
 K-band) AND the seeing value in the constraint set?

• N/A