Subject: VISTA IOT Tuesday 2009-06-30, 10:00 Chile, 15:00? UK, 16:00 Germany, (reminder)

From: Thomas Szeifert <[email-masked]>
Date: Tue, 30 Jun 2009 09:12:32 -0400

Dear VISTA IOT,

here the locations for the IOT today:

   Santiago, Athena room     10:00
   Garching, SkyLight        16:00
   Paranal,  Control room    10:00
   London&Cambridge by phone 15:00

best regards,
Thomas

PS: Valentin, Lander and Jim can't make it today.

********************************************************************

Agenda:
-------
1. Overview about the estimated time lines for the telescope/instrument
    and phase2
2. Review readiness for the call for science verification and dry run
    OBs
3. Round table (be prepared to say a few words about the state of
    preparation for VISTA in your group)
4. Status update of old action items
5. New action items
6. Date of next meeting (last Tuesday of the month if there is no
    special reason like a deadlines)

     ===========================
=== 6. Next meetings           ===============
     ===========================

Dates proposed by TSZ:
-----------------------
28 July 2009      NN             15:00 - 17:00  (09:00 - 11:00 Chile)
25 Aug. 2009      NN             15:00 - 17:00  (09:00 - 11:00 Chile)
22 Sep. 2009      NN             15:00 - 17:00  (09:00 - 11:00 Chile)

     ===========================
=== 5. open Action Items        ===============
     ===========================

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

AI 2009-02: Iterate draft of implementation plan, on hold waiting for C. Dumas
    (TSZ)

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-04: JEM: get in contact with F. Comeron to formalize the SADT delivery.
   Not yet ready to do this, though JimE chatted to Fernando about it.

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-06: VIV: by the end of June send the new simulation report and code
    to be taken over for future simulation

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.

New action items:
-----------------

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

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-10: TSz to send to CASU an example feature introduced by the effect
    of the rotating pupil

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-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).