From tszeifer@eso.org Tue May 26 10:01:11 2009 Date: Mon, 25 May 2009 10:46:02 -0400 From: Thomas Szeifert To: Martino Romaniello , Valentin Ivanov , Magda Arnaboldi , Marina Rejkuba , Wolfgang Hummel , Gianni Marconi , Francesca Primas , Christophe Dumas , Mark Neeser , Stefan Sandrock , Pedro Baksai , Nick Kornweibel , Thomas Szeifert , Sandra Castro , Steffen Mieske , Jim Emerson , usd_vircam@eso.org, qc_vircam@eso.org, Simon Hodgkin , Mike Irwin , Jim Lewis , est@eso.org, Lander de Bilbao Cc: RECEPCION ESO/Vitacura Subject: VISTA IOT Tuesday 2009-04-28, 09:00 Chile, 13:00? UK, 15:00 Germany Dear VISTA IOT, we have a problem on May 26 with the Valentin and myself away. I would like to invite for the next IOT on June 2. Sorry for the short notice. Marina, Valentin and Steffen have problems on June 2. cheers, Thomas ******************************************************************** Agenda: ------- 1. Overview about the estimated time lines for the telescope/instrument and phase2 2. Round table (be prepared to say a few words about the state of preparation for VISTA in your group) 3. Status update of old action items 4. New action items 5. Date of next meeting (last Tuesday of the month if there is no special reason like a deadlines) =========================== === 5. Next meetings =============== =========================== Dates proposed by TSZ: ----------------------- 2 June 2009 NN 15:00 - 17:00 (09:00 - 11:00 Chile) 30 June 2009 NN 15:00 - 17:00 (09:00 - 11:00 Chile) 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) =========================== === 3. 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). [ Part 2: "Attached Text" ] VISTA IOT #7 MEETING 2009-04-28 ================================ Minutes by: T. Szeifert ======================= - minor additions from M. Rejkuba April 28, 2009 09:00 Chile, 15:00 Garching -------------------------------------------- CONTENTS: 0: Presence at the meeting 1: VISTA schedule, current status and planned activities 2: Round table (the state of preparation for VISTA in different groups) 3: Summary of Action Items 4: Dates of the next meetings =========== === 0. PRESENCE ======================================================== =========== Santiago - T. Szeifert ................................... [TSZ] Garching - M. Hilker ....................................[MHI] S. Castro ....................................[SCA] W. Hummel ................................... [WHU] M. Rejkuba ................................... [MRE] L. De Bilbao ................................... [LDB] M. Neeser ................................... [MNE] Cambridge - J. Lewis, M. Irwin ............. [JLE, MIR] BigIsland - S. Hodgkin ............. [SHO] ======================================================== === 1. VISTA schedule, current status and planned activities ======== ======================================================== TSZ gave the summary of the schedule of VISTA based on version 1.54 which was received from Michael Sterzik yesterday. Schedule: ---------- - VPO optics, SW - until May 11 - CCC repair - May 11 - 20 - VPO activities - until June 12 - Paranal engineering - until August 5 - SciVerif. - August 10 - 20 TSz proposed to wait for updates until the repair of the closed cycle cooler and to stick with the schedule for the phase2 package as discussed on the last meeting, since these dates are derived from the predicted date of the start of operations on October 1. - end of June (June 22 preliminary date): preliminary version of the instrument package (IP) and all manuals ready - mid July - freeze of the IP and delivery to Garching for the Phase 2 - Start of operations - October 1 In September some time could be reserved for the mirror coating or other interventions. For now there are dry runs scheduled after August 28, with public survey OBs if available. =========================== === 2. Round table activities =============== =========================== 2.1 SciOps Paranal: TSZ - There was a new DFS version installed on Paranal. Pipeline reduction was continued after this without problems and good results even though the detectors are too warm TSZ was working on documents about QC feedback procedures and sky subtraction --> see AIs 2.2 USD/EST: --> works on the survey execution time reporting are ongoing. The execution times will be computed from the time between an OB is started (status 'S') until it is executed (Status 'X'). It was discussed that it would as well be important to analyze the sources of the overheads. TSz summarized that the overall execution time was read from the OB repository to trigger alerts if we are far out of the predictions in terms of overheads. For the other instruments we typically predict overheads with "conservative estimates" which we can't do for VISTA where the overheads are essential for some projects. CASU reported that they do analyzes (for VISTA?) based on the time stamps in the fits headers. TSz reports that Paranal typically does similar scripts for the monitoring of shutter open times in which this could be logged on nightly base or OB by OB. These scripts are still to be done for VISTA in August. --> new p2pp, sadt beta versions received this week should be reviewed now. These version are thought to be close to the final releases. --> MHi and MRe reported that they worked on the specification and implementation of the survey status visualization tools, which would be based on the VIRGO tool, with interfaces to OB database, for OB related parameters (including QC0 grades), and to archive databases, for raw images and advanced data products. The tool will be able to display on a sky map a group of OBs, raw images, and/or data products according to selected parameters extracted from the parent databases. 2.3 QC: --> all data are processed with the QC computer cluster, some technical problems/issues still to be followed up --> Similar to HAWKI there were radioactive events as well on detectors 1, 5 and 12 of the VIRCAM detector array. Subtracting long darks file by file removes the hot pixels and allows easy visualization of the event, which occur at much lower rate then for HAWKI. --> TSz asked if the QC opslogs files would contain image quality estimates which were certainly written by the recipes into the headers of the products and into the PAF file. AI 2009-08: check if the opslogs contain the values 2.4 Pipeline (SCA): --> a new DFS version was delivered and installed on Paranal --> SCA to leave ESO at the end of July. The new pipeline responsible for VIRCAM, OmegaCAM and WFI will be Lander De Bilbao (LDB), who attended the meeting. LDB should be included on the VISTA IOT distribution list. 2.5 CASU: --> data reduction is completed until end of January. (Since then there were only a few data sete delivered). The latest disks sent after the camera intervention have been received. CASU is working on a preliminary report to provide the information needed for the compilation of user manuals and phase2 packages - close to completion in case of the preliminary report, which will be later included to the final report. CASU is as well almost done with a report on suggestions on sky subtraction issues for extended object (or/and very crowded fields). TSz mentioned to have seen effects of the rotating pupil in K band data, while it was commented by Mike or Jim that there are too many uncertainties due to the filter wheel problem and the debris scatter over the instrument until January. TSz mentioned as well that the pupil doesn't look nice and flat on the wave front sensors and he would expect that this could in some way change the illumination in the image plane as well. It was reported that there is not yet enough data to conclude on the sky brightness (TSz: I understood in this case: measured for the respective NB and BB filters at different lunar phases, - correct me if needed). --> getting reduced data online for IOT members - work in progress ====================== === 3. Action Items ======================== ====================== Closed AIs: ----------- - Implement SADT change request from PIs about rotation of focal plane into SADT and P2PP (JEM together with T. Bierwirth and P. Nunes) - this is done, no change in P2PP needed. - JEM: get in contact with T. Bierwirth and P. Nunez for exchange of knowledge with the SADT developer before he leaves at the end of April JEM meets with Bierwirth & Nunes on Thursday 30th at Garching to discuss SADT. - TSZ/VIV: send to JEM information on how Hawk-I deals with sky offsets: templates/OBs? The HAWKI template manual was forwarded to Jim Emerson and Stephen Beard. TSz has prepared a brief summary about the actual situation. CASU looked into the VIRCAM data - is close to issue a draft report. Pending AIs from previous meetings: ----------------------------------- 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). =========================== === 4. Next meeting =============== =========================== There were no concerns about the date of the next meeting Dates proposed by TSZ: ----------------------- 26 Mai 2009 NN 15:00 - 17:00 (09:00 - 11:00 Chile) 30 June 2009 NN 15:00 - 17:00 (09:00 - 11:00 Chile) 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) Please feel free to propose special topics for the agenda.