README File creation instructions
The README file contains an overview of the run, aspects specific to it, and an instrument-dependent checklist. The README file interface is accessible from the P2PP main GUI via either the Readme button or the Readme menu at the top bar; see the P2PP User Manual for a detailed description. The README file has the following sections:
- A non-editable section giving basic information on the run as scheduled: the program ID and type (normal, large, guaranteed time, or director's discretionary time), instrument, PI name, priority class, and approved execution time.
- A list of sections accessible through tabs where specific aspects of the run can be described:
- General Description: a short and concise summary of the observation, providing the night astronomer with any information needed to meet your science objective (e.g. SNR). Decision paths and/or OB modification requests that depend on the outcome of previously executed OBs are not allowed.
- Waiver Requests: a short summary of any approved Phase 2 waiver requests, including when they were submitted and when they were approved.
- Critical Observing Conditions Constraints: any information about required observing conditions other than those defined in the Constraints Set box that are critical for the achievement of the goals of the project.
- Time-Critical Aspects: any information on timing of the observations other than those encoded in the parameters of the (time-link, concatenation) OB container.
- Special Execution Requirements: any specific information regarding the execution of your observation such as on proper target identification or details on the execution procedure.
- Special Calibration Information: if you have submitted OBs for calibration, please describe them here, why you have submitted them, and how they should be executed relative to your science OBs (e.g. same night, once per observing run, etc.), unless included in an OB concatenation. In particular, for some instruments, you must provide the magnitude and spectral type for all user supplied photometric or spectrophotometric calibration stars.
- ToO Information: please indicate here if this is a Target of Opportunity run and give any special details.
- ToO Activators List: please give here the names of the investigators who are authorized to trigger a Target of Opportunity observation.
- Pre-Imaging Requirements: if this is a pre-imaging run, please indicate it here and describe any special requirements; for instance the need to obtain on- and off- observations in narrow-band filters contiguously.
- An entry for the e-mail address of the Principal Investigator of the programme. Please do not enter here any address other than that of the Principal Investigator, even in the case that the person preparing the Phase 2 package is not the PI.
- Estimated Total Execution Time: please include here the execution time as given by the execution time report of P2PP.
- Is this a Pre-imaging run? this is a tick box that must be checked if the run is pre-imaging for another run. This is important to ensure that pre-imaging runs receive the correct execution priority.
- In case pre-imaging was required to prepare these OBs, you must indicate the source of pre-imaging in the corresponding box. If the source is none of those listed there, you can indicate the actual source in the entry below it.
The last part of the README file is a check list including most of the relevant aspects related to Phase 2 preparation with the corresponding instrument. You must click either yes or N/A to ensure that you have taken all these aspects into account.
A tutorial showing how to attach Finding Charts, edit the README file, and submit OBs and containers is available in text and video format. Another dedicated text tutorial provides step-by-step guidelines for the preparation of the Service Mode README file content.
Additional Contents for the NACO README file
In addition to the general requirements for README FILES, the following NAOS-CONICA specific recommendations should be followed:
- The magnitude of the brightest object in all fields (at or near the wavelength of the observation), including standard stars, must be specified.
- If the brightness exceeds those cited below, full justification must be supplied.
- For LGS mode OBs, the V magnitude of the Tip-Tilt star and its separation from the main target (in arcseconds) must be specified.
- For LGS in SE mode, this must be explicitly stated.
- For NGS OBs the type of wavefront sensor used and the magnitude of the AO reference star (at the appropriate wavelength) must be specified.
Observational Brightness Limits
Observations involving fields with objects brighter than those specifed in the table below cannot be guaranteed. Requests for observations not compliant with these limits must be submitted as a Phase 2 Waiver Request.
|SW broad band imaging||6|
|SW narrow band imaging||4|
|LW broad band imaging||5|
|LW narrow band imaging||3|
If the neutral density filters are used, subtract 4 magnitudes. NOTE: Spectroscopic observations with the ND filters are not supported.
If the N90C10 dichroic is used, subtract 3 magnitudes.
OBs that require maximum field rotation with pupil tracking
Prior to Period 90 NACO users with OBs that required maximum field rotation were asked to provide the following information in the README:
Please explain explicitly in the ReadMe file at which LST the OB should be started, taking into account the preset and acquisition overheads. In this context please bear in mind that in Paranal, the latitude is -24º35’. Further, if the declination of the object is within 4º of this value, the telescope cannot “cross” the meridian. Therefore such objects must be observed either before or after the meridian (LST +/- 10 minutes).
Starting with Period 90, however, there exists in the new version of P2PP the concept of LST time ranges for OBs, and hence there is no requirement to document this in the README. These LST time ranges will be used in an automatic way at the telescope to guide in scheduling OBs for execution. However, here is where an important difference with the past comes into play. The LST range that one specifies for a given OB represents the whole time period within which the OB must fit in order to be scheduled. This has two consequences:
- The execution time of the OB must be less than the length of the LST range specified (that is, the OB must "fit" into the LST window given).
- In order to capitalize on the maximum rotation achieved when the target transits the meridian the LST range specified in the OB should be (roughly) symmetric with respect to that LST and sufficiently short that it would not be possible to have the OB fully executed on either side of culmination, but not so short that it compromises the chances that it can be scheduled at the telescope.
If in doubt, contact the User Support Department by clicking on "Ask for help" within the ESO USer Portal, or by sending an e-mail to firstname.lastname@example.org.