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

Principal Investigator Email Address

• ejehin@eso.org

Estimated Total Execution Time (hours, including overheads)

• 05:59:40

General Description

• The goal of this run (A) is to obtain high resolution spectra with UVES
   in DIC#1 and DIC#2 of the 2 brightest fragments (C and B) of the split comet 73P/SW-3.
  The ToO will be triggered when the comet is in outburst (sometime before June 20).
  
  - Precise coordinates (RA and DEC), 
  - Differential tracking rates, 
  - And the position angle (PsAng) 
  must be updated for each observation before starting the OBs (see execution requirements),
   using the ephemeris which will be sent with the activation.
  
  There are 4 OBs of 1h30m, 2 for each objet (1 DIC#1 and 1 DIC#2 OB) : 
  MOV_Comet73P_B_DIC1 : DIC#1 350+580 (slit=0.5 arcsec, SKY, ADC)
  MOV_Comet73P_B_DIC2 : DIC#2 437+860 (slit=0.5 arcsec, SKY, ADC)
  MOV_Comet73P_C_DIC1 : DIC#1 350+580 
  MOV_Comet73P_C_DIC2 : DIC#2 437+860
  
  As we are observing an extended object moreover at high airmass and with a given
   slit orientation we use the SKY option with the ADC.

Waiver Requests

• We are using a non std setting for the blue of DIC#1. It is very similar
   to 346nm (350nm) and has already been used with success.

Critical Observing Condition Constraints

• None.

Time-Critical Aspects

• - The coords need to be filled at the precise time 2 min of the preset
   because it is a very fast moving object (to get it right in the small UVES FOV)
  
  - The comet is only visible at the end of the night during about 2 hours. The OBs
   are 1.5h long so only 1 OB can be done per night. The OB needs to be started not
   too late in order to have enough time to complete it properly. 15 minutes of twilight
   can be used without problem!
  
  - When one OB is executed for one of the fragment, the 2d OB should be executed
   as close as
  possible to it (in one of the next following night). The 2d trigger and the 4rth
   will then be sent very close to 1rst and 3rd.

Special Execution Requirements

• - *Choice of Guide Star* ! : The comet is a very fast moving object :
   6 arcmin in 1h30m. The guide star will need to be chosen *very* carrefully to avoid
   to change the GS during the long exposure (and of course avoid to cross the UVES
   FOV). The comet is moving nearly exactly to the South-East. So the GS needs to be
   chosen in that direction to maximise the time to keep it in the guide probe.
  This strategy has already been done in the past and works very well.
  In case a change of GS needs to be done the exposure needs to be PAUSED before changing
   the GS, then the comet nucleus put back on the slit (in case it goes out) and then
   the exposure CONTINUED. 
  
  - As our targets are moving objects, the following quantities need to be updated
   in the OB before execution :
  
  1) the precise coordinates (those in the OBs are just indicative)
  under the columns : R.A._(ICRF/J2000.0) and _DEC
  
  The 2 fragments are bright (V = 7-8 mag) and will be easy to identify.
  If you dont see the comet, please look again the ephemeris, especially the UT date.
  
  2) the additional tracking velocities 
  under the columns : dRA*cosD and d(DEC)/dt
  
  If the comet is moving with respect to the slit during the exposure, 
  this means that the diff. tracking was not properly set ! Please look again the
  ephemeris, especially the UT date.
  
  3) the Position Angle (to have the slit along the comet tail)
  under the column : PsAng (given in degrees and measured from N-->E)
  
  These quantities are to be taken from the provided - 1 min steps- ephemeris.

Special Calibration Information

• none.

ToO Information

• These ToO observations will be triggered during an outburst of the comet
   (between May 25/ June 20). The ephemeris will be sent at that time.

ToO Activators List

• Jehin Emmanuel (ejehin@eso.org)

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• none

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 ?

• N/A

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 ?

• 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