VISTA IOT PRELIMINARY AGENDA, 2010-03-23 15-17h Garching / 14-16h UK / 11-13h Chile 1. VISTA status and planned activities (TSz) 2. VISTA PPRS Summary (VDI) 3. SADT and AG/AO star catalogues (UltraVISTA OBs) 4. Overheads (AO Priority, jitter sequences, execution times) 5. Header keywords for pipeline reduced data (see the enclosed report from Adam Dobrzycki) 6. Re-processing of VISTA data by CASU (JL) 7. Feedback from the PIs (if any; i.e. reclassified OBs; MRe?) 4. Action Items review (see bellow a summary from the 2009-01-26 IOT) 5. Others 6. Date of the next meeting: end of Apr, 2010, possibly Apr 23, Fri. * * * Header Keywords =============== After viewing both QC products and the "CASU new pipeline" products, I have only a limited set of comments. With "CASU new" products I have one serious issue and few minor ones. The QC products only have issues with checksum stuff and INHERIT, see below. The serious problem with CASU frames one is that there is no EXTNAME keyword in the extensions. I would consider that an absolute must for all frames containing extension HDUs. Its value must uniquely identify the extension. Both raw frames and QC products do have them. CASU frames either do not have them at all or -- in st_cat frames -- have them non-unique. The less serious stuff: - Frames preserve ZHECKSUM and ZDATASUM from raw frames. Those keywords only make sense in tile compressed files, which none of the files I have seen is. This touches both CASU and QC frames. - CASU frames preserve ORIGFILE and ARCFILE from raw frames. This is less serious, since those keywords will be set to correct values by the archiving process, but still... - CASU frames use INHERIT=F. In principle, this is not a FITS error, but I think it is a content error - I think that frames should use INHERIT=T. The inheritance conventions says clearly that setting INHERIT=T means that all kewyords are inherited, except for the ones that are specifically listed in the considered extension. Thus in the T case the extension-specific stuff would be taken care of in extensions, while the global observation stuff would be implicitly included. The effect of setting it to F is equivalent to specific exclusion of, for example, OBS, TEL and INS hierarchies, as if they did not apply to the extensions. QC products do not use INHERIT at all - I think they should, too. Cheers - Adam * * * Action Items Summary from the 2009-01-26 IOT ============================================ Progress report on previous action items: * AI 2009-01: Monitor execution times & survey completion status Is being followed up by MAR, MRe. 2009-07-29: There is a first prototype 2009-10-06: no news (MRe) 2009-12-01: no news STATUS: ONGOING * 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. Thought to be ready On September 6, 2009 2009-10-06: a report will be ready on Nov 17 (MAr) 2009-12-01: the report is not ready (MAr) 2010-02-26: agrred plan for the delivery of final version of SADT by end of April, and acceptance reviw in June STATUS: CLOSED * AI 2009-06: VIV: by the end of June send the new simulation report and code to be taken over for future simulation. 2009-10-06: report writing in progress (VIv); to be transferred to the EST during Oct SciVer (TSz) 2009-12-01: MRe: the simulation delivered to OPO and Gaiteee takes over. VIv: the completeness rate is ~85%, we will need one extra year to complete the already approved surveys. TSz: we have to look again at the overheads 2010-01-26 GHU reports on her advancement with VIV's code. More work to be done though. Further complications may arise form the request of scheduling Chilliean time which is not allocated to VVV. and from open use programs in P88. STATUS: ONGOING * 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 programs 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. 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. 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. 2009-10-06: the information about the containers must be included in the keywords, CASU must be included in this work because it will have an effect on the pipeline (JEm); this is also relevant for the sky offset template (MAr); not really, because the sky offset is in the same OB as the primary target tile (JEm); in the past we used for this purpose the DPR keyworks (TSz); this info might be needed also for the ESO archive users (WHu); a good example for the archive is to identify the telluric standards, corresponding to a given data set, so the issue is relevant generally for all ESO instruments (MRe). 2009-12-01: MRe and Th. B. are looking into it, working with the BoB people. STATUS: ONGOING * 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. STATUS: ONGOING * AI 2009-20: installation of a new served for faster/cheaper/better data reduction, to be available for semi-real time data reduction during the Science Verification run on 16-30.10.2009. TSz will talk to Christophe Dumas. 2009-12-01: the data had to be compressed to ensure that a copy is kept until the USD disks arrive in Garching and are checked 2010-01-26 most problems are related to disk space (TSZ) STATUS: ONGOING * AI 2009-21: Create poor weather conditions (particularly poor seeing) back up SciVer programs. The approved SciVer programs request seeing 0.8 arcsec or better, if the SciVer was last week, it would result in almost zero data. STATUS: ONGOING * AI 2009-22: Increase the jitter box size of the sky flats to ~1/2 of the detector size. STATUS: ONGOING * * New Action Items from this meeting: * AI 2009-23: JEm should deliver the SADT by Dec 10 STATUS: CLOSED * AI 2009-23: MHi will contact Andine about extrapolating the 2MASS to Z-band magnitudes. 2010-02-26 MHI reported the negative answer STATUS: CLOSED AI 2010-01: TSZ the calibration database should be updated with new flats and mastre calibrations and how to do it regularly, as no procedure is currently in place. STATUS: NEW - WHU should give Thomas Bierwirth a usb disk with the updated calibrations before Feb7, 2010. Then on try to define a procedure for a regular update of reference frames on Paranal AI 2010-02: TSZ: how many standard stars fields should be taken? Effort in February to take up to 3 fields. Request to implement a change of jitter pattern by JLE, from 4 to 5 jitter. Try to keep calibrations plan withing 1 hrs total execution time. STATUS: NEW - JLE suggests to discuss issues with PIs, and provide feedbacks to TSZ, expecially in the ZY band calibrations in particular. * * * 6: Others N.A. * * * 7: Date of the next meeting: 16 Feb, 2010, 14 h Garching / 10 h S-go