Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/sci/activities/vltsv/svdoc.pdf Дата изменения: Thu Oct 5 12:30:45 2006 Дата индексирования: Sat Dec 22 20:25:27 2007 Кодировка: Поисковые слова: р п р п р п р п р п р п р п р п р п р п р п р п р п р п р п р п р п р п

VLT Science Verification Policy and Procedures
Version 2.0 - August 2006

Science Verification Observations
An integral part of the Commissioning of a new VLT instrument is a series of Science Verification (SV) observations. SV observations may also be conducted in the case of a major instrument upgrade. The equivalent of at least 11 VLT UT nights should be dedicated to SV observations. SV Observations are scheduled after commissioning has advanced to the point where the instrument is sufficiently well characterized to permit science driven observations, Thus, SV usually happens before the end of the commissioning phase, and always before the instrument is released for regular science operations. At the end of the scheduled SV runs the VLT Programme Scientists submits to the Director General a report on the status of completion of the planned SV observations. If the corresponding set of data is judged insufficient to reach the goals of SV, the Director General may decide for further SV observations to be executed during the first scheduled regular runs in Service Mode. All SV Observations are conducted in Service Mode and usually some members of the SV Team are present at Paranal Observatory for a prompt reduction of the data, and the selection of the observations to be executed.

Goals of Science Verification
The goals of SV include: · · · · · · · Offer ESO users first science-grade data from a new instrument Experiment Phase II preparation tools for a new instrument Demonstrate the scientific potential of a new instrument Foster an early scientific return from the new instrument Experiment any pipeline and reduction tools that may be available at the time of SV Provide feedback to Operations (Paranal and Garching), Instrument Division, and Data Flow Systems, as appropriate Involve scientists from the ESO community in the prompt scientific exploitation of the data.

Science Verification Programmes and Data Policy
· · · The SV Plan of an instrument is developed by a dedicated SV Team. The PI(s) of the instrument subject to SV and the Instrument Science Team are involved in the definition of the SV plan. The SV Programme is finally submitted by the VLT Programme Scientist to the Director General for approval.

1


· · ·

SV observations of targets already included in GTO or approved GO programmes with the same instrument could be executed only with the agreement of the PI. Raw and calibration SV data passing quality control are made immediately public via the ESO archive, following the "Data Access Policy for ESO Data". The SV Team will make efforts to release reduced SV data within two months from the conclusion of SV observations.

Selection Criteria for SV Programmes
SV Programmes are selected according to the following criteria: · · · · · · Should have outstanding scientific interest Push the VLT + Instrument close to their limit Address a scientific issue widely studied within the ESO Community Result in a sufficiently complete dataset for its prompt exploitation to be scientifically rewarding Use the core modes of the instrument Help PIs and Co-Is of approved GO to GTO programmes to get promptly acquainted with the data from the instrument

The SV Team
Composition of the SV Team A dedicated SV Team is assembled for each of the various SV phases, including Garching and Chile staff and fellows (typically up to 8-10 people). In the selection of the SV Team members the VLT Programme Scientist will follow the following criteria: · · · Strong scientific interest for the specific capabilities of the instrument Technical experience with the type of data being produced by the instrument Wide coverage of the main scientific areas that the instrument is designed to satisfy

To all activities of the SV Team will also be invited to participate: · · · · The Instrument PI and Co-PI, or one person designated by each of them The ESO Instrument Scientist The ESO user Support Scientist for the instrument The ESO Quality Control Scientist for the instrument

2


Duties of the SV Team The duties of the SV Team include: · · · · · · · Development and pre-selection of the SV projects Preparation of the OBs when SV runs take place prior to the completion of the corresponding P2PP tools Maintenance of SV WEB pages, describing the SV plan, and including informative lists of SV data as they become public. Real time assessment of the SV data at Paranal Observatory Delivery through the SV WEB and the ESO Archive of the raw, calibration, and pipeline calibrated data, if available. Assist PI's with the preparation of OB's and provide further information to users about the data sets. The SV Team can have access to the Commissioning data prior of SV observations.

Scientific Exploitation of the SV Data
The scientific exploitation of the SV data can start as soon as the data are publicly released. The formation of groups and teams for the scientific exploitation of the SV data is left to the initiative of the individuals. SV Team members are encouraged to promptly use the data and to stimulate the participation of scientist from the community. Authors are kindly asked to send to ESO (Office of the VLT Programme Scientist) at submission time copy of any paper that may result from the use of SV data, along with a concise technical report on the use of the data, pipeline, etc, Authors are kindly encouraged to include as co-authors those members of the SV Team that contributed significantly to the preparation (and execution) of the observations, and/or to the reduction of the data.

3