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

Principal Investigator Email Address

• mk@roe.ac.uk

Estimated Total Execution Time (hours, including overheads)

• 5

General Description

• These OBs are for compensation of the time loss during the RRM trigger
   on Sept 7th-8t. We used different slit widths for a same object but only one acquisition
   through-slit during the run and the data are perfectly OK, we would like to go on
   as such. The OB are longer than 1hr but identical to those executed during our run.
   
  
  PKS2310-322 ... PMOS mode observation with Grism 600I, with two
  telescope offset postions (take 4 waveplate positions at each offset
  position), and another short exposure with wide slit (8arcsec).
  
  Q0144-3938 ... PMOS mode with (1) Grism 600I (essentially identical
  as above) (2) Grism 300V (no order sorting filter), 4 waveplate positions
  (3) Grism 300V with a wide slit (4) three more exposures with the same
  config as (2).
  
  flxstd-LDS749B ... PMOS mode with (1) Grism 600I, (2) Grism 300V (no order sorting
   filter)
  
  Since the second one takes a lot of time, for Q0144-3938:
  *** please reset ADC after (3) ***
  [we need as much blue photons as possible].
  
  Note:We have an observing run which is linked to this program in two weeks
  (075.B-0593(B) - set to be after this program), so we would be very happy
  if we could get the data before the run, if it's at all possible.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• moon:g Seeing: n Sky Trans: THN

Time-Critical Aspects

• Note:We have an observing run which is linked to this program in two weeks
  (075.B-0593(B) - set to be after this program), so we would be very happy
  if we could get the data before the run, if it's at all possible.

Special Execution Requirements

• These OBs are for compensation of the time loss during the RRM trigger
   on Sept 7th-8t. We used different slit widths for a same object but only one acquisition
   through-slit during the run and the data are perfectly OK, we would like to go on
   as such. The OB are longer than 1hr but identical to those executed during our run.

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 ?

• 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 have prepared your finding charts with tools other than FIMS,
 do they comply with the specifications on the FORS1 Phase 2 web page ?

• YES