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

Principal Investigator Email Address

```
tozzi@arcetri.astro.it
```

Estimated Total Execution Time (hours, including overheads)

```
3:04
```

General Description

- JHKs imaging of comet 67P/CG, target of the Rosetta Mission.
- This program should be execute as close as possible with the other program 381.C-0123(A),
 for VRI imaging with FORS2.
- This program consists of three OBs, (MOV_67P_May_JHK_1, _2 and _3) that possibly
 should be executed during three succesive nights, to check comet variability. 
Indeed the constrains for runs _2 & _3 are less stringent, since we prefer to
 have data, even in in non good weather conditions

- Please insert appropriate proper motion, as given in the ephemeris file

Waiver Requests

```
No Waiver Request was submitted
```

Critical Observing Condition Constraints

This program should be executed or as close as possible with program 381.C-0123(A)
 at FORS2.

PLEASE DO NOT OBSERVE:

- on night 2-3/5/08 (all night) because of a bright star in the ISAAC FOV 
- at the beginning of  night 10/5/08  because of a bright star in the ISAAC FOV
 
- on night 15/5/08 after 3 UT because of a bright star in the ISAAC FOV 
- on night 18/5/08 after 9 UT because of a bright star in the ISAAC FOV

Time-Critical Aspects

This program should be executed  as close as possible with program 381.C-0123(A)
 at FORS2.

The 3 OBs (MOV_67P_JHK_May_1, _2 and _3) should be possibly executed during three
 consecutive nights.
For the successive nights (runs _2 & _3) the sky condition are less stringent,
 since it is better to have data in bad condition than to have nothing.

The time difference between the OBs _1, _2 & _3  should be not less than about
 24h. So no more than 1 OB have to be executed in the same night.

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 ?

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?

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

If this is a run that requires coordinated observations with other facilities, did you give proper instructions in the Time-Critical Aspects Section ?

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 ?

```
N/A
```

If you are doing spectroscopy, did you draw the slit on the Finding Charts ?

```
N/A
```

Did you enter the magnitude of the brightest star in the field-of-view in the 'Instrument Comments' field of each OB ?

```
N/A
```

If you use the MoveToPixel acquisition, have you given clear instructions on the FC and in the OB comment section as to how the field should be centered ?

```
N/A
```

Last creation of page: Tue Oct 6 15:40:23 2009
If you have comments, please contact usd-help@eso.org