======================================================== === 4. AI review ======== ======================================================== AI 2009-01: Monitor execution times & survey completion status Is being followed up by MAR, MRE. 2009-07-29: There is a first prototype AI STATUS: ONGOING AI 2009-02: Iterate draft of implementation plan, on hold waiting for C. Dumas (TSZ) - timeline draft circulated 02/07/09 AI STATUS: CLOSED - document on BSCW version 2.1 - 2009-06-30 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 STATUS: CLOSED - BSCW document version 1.1, 2009-06-25 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. Documentation still missing. Discussion about the magnitude ranges that SADT takes for AG/AO stars. TSZ: this is a configuration issue. AI STATUS: OPEN; deadline for SADT manual delivery August 21. 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 completion. A dedicated template for sky subtraction is not foreseen at this stage. There is also no pupil rotation detected in the latest dataset. Better wait for the final VPO report. JEM sent CASU web page with info from QC processing. DONE. AI STATUS: While this AI was CLOSED, the report from CASU is still not available and is crucial for the User Manual and Fact Sheet to be sent to the PIs at the time of the announcement of the SV and dry runs. AI 2009-06: VIV: by the end of June send the new simulation report and code to be taken over for future simulation. Deadline: end of June. AI STATUS: ongoing. New deadline: end of August 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 shifted to the end of July 2009. 2009-07-29: due to M2 oscillations shifted to August 10. AI STATUS: OPEN AI 2009-08: QC to check if the opslogs contain the values for the image quality AI STATUS: 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. 2009-07-29: from the last weeks observations TSZ has impression that the standard templates and the sky subtraction works. VIV made exercise with VVV people, but is waiting for feedback from P. Lucas who is on vacation. It may be necessary to reduce two tiles together. AI STATUS: ON HOLD; JEM to request feedback from CASU. AI 2009-10: TSz to send to CASU an example feature introduced by the effect of the rotating pupil AI STATUS: 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. 2009-07-29: TSZ iterating with R. Schmutzer, but DFI (T. Bierwirth) will also need to be involved. For surveys, given the small range of programmes it is expected that there are not too many different OBs, and this might need to be followed in a different/manual way in the beginning - this could imply a major change for the tools that cannot be done in the last moment. AI STATUS: 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. 2009-07-29: Answer is NO. But is this necessary? JEM thinks yes if processing of data takes this into account. TSZ: this will need to be done together with P2PP/OT programmers and VLT software support after discussion. TSZ will raise it, but cannot promise a solution. AI 2009-12: ONGOING New AI (added after the discussion around the table): AI 2009-13: TSZ to send opslogs and fits logs + some scripts to MNE and MRE AI STATUS: CLOSED - done after the IOT AI 2009-14: GHU to check that the seeing distribution function in the scheduler for VIRCAM takes into account the finite (0.51") nominal resolution of the instrument. AI STATUS: NEW AI 2009-15: MNE check the opslogs from the last ESO commissioning (data sent by TSZ as per AI 2009-14) and formulate official request for JEM to allow ESO people SV/EST to access, see these data. AI STATUS: NEW