Subject: VISTA IOT meeting 2009-07-29: reminder, agenda, action points

From: Valentin D. Ivanov <[email-masked]>
Date: Wed, 29 Jul 2009 02:29:21 -0400 (CLT)

Locations:

- Garching, room 231 (IP 134.171.3.187), participants: Michael
Hilker, Magda Arnaboldi, Marina Rejkuba, etc.
- Santiago, no specific room, participant Tomas Szeifert
- Paranal, Residencia, participant Valentin Ivanov
- UK, via phone at +44 20 7882 5040, participant Jim Emerson

IOT agenda:

- Statis of VISTA (Thomas Sz.)
- Pipeline (Lander de B.)
- ESO survey team meeting (Mark N.):
    1. Schedule for Science Verification (SV).
       How will the SV be affected by the telescope
       and instrument interventions that are scheduled
       betweenJuly 27 and SV?
       There needs to be a few nights of commissioning
       time following the intervention in order to create
       a new calibration data set, before SV begins.
    2. Who will be on-site for Science Verification
       (from PSO etc.)?
    3. Data from the ESO commissioning of VISTA needs
       to be released to the SV team in Garching for data
       reduction practice and for testing the survey
       visualization tool.
    4. For the creation of the public survey dry runs
       (100 hours allotted to each PS), the results from
       the OB execution simulation are required.
- progress report on the action items
- round table

     ======================
=== 4. Action Items        ========================
     ======================

AI 2009-01: Monitor execution times & survey completion status (WIP:
             MAR,MRE) Is being followed up by MAR, MRE.
AI 2009-01: ongoing

AI 2009-02: Iterate draft of implementation plan, on hold waiting for C.
             Dumas (TSZ)
AI 2009-02: ongoing (timeline draft circulated 02/07/09)

AI 2009-03: Formalization of the procedure of feedback from CASU about the
    image quality of science data (WIP draft fragment sent by TSZ, MRE 
opened
    mailing lists to CASU, QMUL people involved in science operations).
    Sciops Paranal does check the data for image quality, checks the sky 
for
    clouds, will later query the image quality and zero points from the
opslogs
    files. QC does check the calibration data, and does spots check on some
    selected files to track down principle problems. QC does not check if 
the
    data is taken within constraints. CASU does for WFCAM a WEB page with
    a night report, but so far doesn't check if observations were taken
    within the constraints or not. TSz pointed out that the night report 
will
    be sent to CASU, QMUL,... as well and will look if the constraints can
    be propagated in a convenient way downwards. Any other steps are to be
    discussed soon. (TSz: This needs to be simple enough not to cause
    additional workloads. It wasn't meant to send new requirements, but
    to look if we can get some simple feedback at low cost, if there is
    something found in the data). AI 2009-03: ongoing, TSZ is currently
working on the document (draft circulated
 	    on 03/07/09)

AI 2009-04: JEM: get in contact with F. Comeron to formalize the SADT
           delivery. Not yet ready to do this, though JEM chatted to 
Fernando
           about it. AI 2009-04: ongoing, JEM is in charge of the SADT
revisions

AI 2009-05: JLE: send CASU report to TSZ; particularly critical sky
subtraction
    issue, but also needed information about the astrometry, calibration
    accuracy, and other items that should be covered in the User Manual
    A draft version is close to completition. AI 2009-05: A dedicated
template is not foreseen at this stage. There
             is also no pupil rotation detected in the latest
             dataset. Better wait for the final VPO report. This AI is
             now considered CLOSED.

AI 2009-06: VIV: by the end of June send the new simulation report and 
code
    to be taken over for future simulation AI 2009-06: ongoing. VIV is
finalizing it.

AI 2009-07: MAR/MRE: contact PIs at the end of May (once the handover is
    done/certain) and inform them about the time line and activities. 
Should
    wait until the Closed Cycle Cooler is repaired. AI 2009-07: AI shifted 
to
the end of July 2009

AI 2009-08: QC to check if the opslogs contain the values for the image
    quality AI 2009-08; yes, CLOSED

AI 2009-09: After there is a task in "track" to work on the template for
    proper
    sky field observations: TSz should forward the information to IOT to
    follow up the steps to make the pipeline work with this change. AI
2009-09: ongoing

AI 2009-10: TSz to send to CASU an example feature introduced by the 
effect
    of the rotating pupil AI 2009-10: CLOSED. It was an effect caused by a
dirty pupil in January

AI 2009-11: TSz should find out if the constraints sets could be carried
    with the OBs, to the OS and the fits header of the VIRCAM files.
    Otherwise it is not easy to propagate these data by interfaces. AI
2009-11: ongoing

AI 2009-12: TSz should check how/if the fits keywords of the raw
    file have the information about the concatenation and other scheduling
    containers. (TSz: I have had already something like this in my mail and
    must have forgotten later to look into this). AI 2009-12: ongoing

-- 
***********************************************
   +    Dr. Valentin D. Ivanov
+E     European Southern Observatory
    S+  Ave. Alonso de Cordova 3107
   O    Casilla 19001, Santiago 19, CHILE
   +    Tel. ++(56)(2)463-3252, FAX ... 463-3001
        http://www.sc.eso.org/~vivanov
***********************************************