1、KIDS requirements,Dave Wilman for the KIDS teamThe KIDS operational plan and the role of AstroWise.List focussed on open questions: discussion required!By no means an exhaustive list,1. Monitoring Tool,Requirements:We would like a tool to: Define the observationsAnd to monitor and manage:Progress of
2、 observationsProgress of reductionDelivery to ESO,Current Implementation:The VISTA consortium is developing the Survey Area Definition Tool (SADT) which will interface with P2PP to automatically generate OBs and guide stars. Availability: early 2007.P2PP will be upgraded to allow timelink, concatona
3、tion and grouping of OBs so that survey strategy can be optimized.VISTA consortium developing a tool to monitor survey progress: The EST will look at this and see if a version of this tool can be made available to ESO and other survey teams.,1. Monitoring Tool,1. Monitoring Tool,Action Items:Check t
4、he existence, capability and availability of the ESO monitoring tool.,2. Strategic Organisation and Distribution of Data Reduction,Management Tool (item 1)Uniform plan for data reduction:Consistent scripts / use of web-interfaceDistribution of data for actual reduction.Distribution of responsibiliti
5、es for recipes and testing.,3. Field Layout and meshing with VIKING,Observing Strategy and Dithering of KIDS:see KIDS webpageMeshing with VISTA:Probable solution: Matching KIDS tiles in Dec, but not in RA.,4. Dealing with Tiling and overlaps,Split into 1 square degree chunks (imaging and catalogue)?
6、Provide catalogue only once the full depth is available in all bands for that chunk?Deal separately with the overlap regions and the resulting cross-calibration?How will these divisions work technically? (i.e. can SWARP apply its own boundaries to a set of images, which due to dithering and tiling o
7、verlaps will cover a larger area than the chunk?),5. The size of KIDS,There has been discussion with ESO about extending the area of KIDS. Technically, what is the maximum data-rate which we could handle for reduction?Manpower (reduction, testing, re-reduction)Computer power (rate of processing),6.
8、Absolute Photometric Calibration,Calibration of the absolute photometric zeropoint:North: Calibrate using SDSS sources: SDSS accuracy not good enough for our relative photometry (0.02mags) but OK for the absolute photometry?Well understood calibration in worse seeing SDSS dataSDSS photometry already
9、 exists. South: Calibrate using our own photometric pass:Easier to calibrate, with reduced systematicsNo reliance on external source of dataPossible synergy with ATLASMay help improve absolute astrometryAlternatives (e.g. SSS) rely on data which does not yet exist, and with unknown systematics.,7. Q
10、uality Control,Local / Short-term: during data processing; Simple checks of data products: plots and QC parameters (see next slide);Global / Long-term:Photometric accuracy using multi-band catalogues;Colour-colour diagrams (and photo-z);Number counts;Delegated responsibility by expertise?(e.g. Munic
11、h has expertise in fine-tuning photometry using a multi-band catalogue),8. QC Parameters and Plots,QC parameters to be computed from each node when processing data?Code required to make certain tests: build on existing inspect methods (plots) and QC parameters (values)Store QC parameters in database
12、 and process to management tool?Require a full list of such tests, frequency and responsible persons.,8. QC Parameters and Plots,Example QC Plots and Parameters:Astrometry: Local: plots of residuals (dx,dy,dra,ddec) vs (x,y,ra,dec)Global: cross-checks (and a long-term check might be to look for syst
13、ematic and random offsets between bands)Values: rms, Npairs, coefficients and errors on linear fits of residuals?.Photometry:Images: Background level variation in subwindows?PSF(time, chip, position, colour, mag)Manual(?) check for fringe-patterns, ghosts, satellite tracks, cosmic rays etc Catalogue
14、s:STD: plots: raw ZP (time, chip, position, colour, mag)STD: values: raw ZP rms, Nobj etcSCI: in overlap regions: ZP residuals (time, chip, position, colour, mag)etc etc.,QC Params: KIDS page 1,QC Params: KIDS page 2,QC Params: KIDS page 3,QC Params: KIDS page 4,QC Params: KIDS page 5,9. Photometric
15、 Accuracy,Require accuracy of 0.01mag required for photo-z.(Potential) Astrowise tools to help reach this accuracy:Galctic Extinction Map IngestionSextractor Double-Image mode (measure the flux at the same position in all bands, even where in some bands we only get upper limits)Shapelets: The GAAP (
16、PSF-matching) method (Kuijken et al): can we reach the required accuracy with this method?Convolution (brute-force): Johannes has plans to implement within AstroWise, and to test the computational requirements.,10. Ingestion of NIR data,How will NIR data be ingested into AstroWise?At what stage of r
17、eduction will it be ingested? Pre-regridding?What kind of Weight-Maps will/can come with the data?Is Ingestion of reduced images already tested?UKIDSS / VISTA / 2MASS?,11. Data Storage,Deletion of files ! Is it necessary to consider deletion of:Redundant files?Intermediate files?Our tutorial in Muni
18、ch, plus Johannes WFI data is already filling our diskspace.Please consider how we can safely delete data within a Project context!,12. Visual Inspection of Data,PanoraPix: Will it be ready in time for KIDS?What is the status of the cut-out server?It would be nice to view each chunk of KIDS data sep
19、arately: if PanoraPix is not ready, will this be possible?,13. Tracking of artifacts,We will want to know automatically which sources in the catalogue are real.How do we treat:Ghosts?Bright-star artifacts?,14. Node Project Managers,Who are they?Munich: David Wilman , Hans Vaith ,Groningen: Edwin A.
20、Valentijn ,Paris: Herve Aussel ,Leiden: Merijn Smit ,Bonn: Oliver Cordes ,Napoli: Mario Radovich radovichna.astro.itEach manager should be able to manage/organise the people at their node.A good start would be to get started with test cases ASAP!,15. KIDS Daily Operations,Contact between nodes / peo
21、ple.Frequency / method:A forum / mailing list?Regular telecons?On a longer timescale, regular meetings?,16. Timescale for ESO delivery,What we told ESO in the Management Plan RIx reply:“A good multi-band catalogue is essential to qualify the photometric (and astrometric) calibration of our data prod
22、ucts, and to our science (in particular to get good photo-zs). We will reevaluate seeing requirements for u, g & i (but not r) bands each semester, with the aim to keep the bands in step. However, particularly at the beginning of the survey, observing practicalities will mean that there is no way th
23、at we have identical coverage in all bands.Photometric calibration will require the photometric pass which will precede the main survey pass and establish zero-points across the KIDS area. Also we require re-observation with OmegaCAM of our secondary standard star fields during the first year, as ou
24、tlined in the OmegaCAM Calibration Plan. Multi-band photometry is also required for vital fine-tuning of photometric accuracy (colour-colour and photo-z checks). For all these reasons, we request a full year (after delivery of the final band for a given tile) for initial catalogue delivery. Once the
25、 photometric calibration is better established, we are happy to catch-up to a 6 month timescale. The frequency of delivery can be as ESO prefers. This can be almost as continuous as desired.”,17. WFI test program,There is a need for a federated test program which simulates the reduction of KIDS data
26、 (i.e. managing the distribution of reduction and testing amongst ourselves).Pre-requirements:Federation of AstroWise - requiredNodes ready with the AstroWise system installed working on the clusters requiredStable and relatively bug-free installation of AstroWise requiredConsistent plan for reduction on an appropriate dataset requiredAll software elements in place (e.g. aperture-matched photometry etc) - preferable,18. VLT followup,Is there any action required regarding the ESO VLT followup of KIDS targets?,
