Download
1 / 6
60 likes | 164 Views
IRS Data Flow & Questions. SINGS Team Meeting 21-22 November 2002 Baltimore, MD. L. Armus SIRTF Science Center. General IRS data flow / timeline.
E N D
IRS Data Flow & Questions SINGS Team Meeting 21-22 November 2002 Baltimore, MD L. Armus SIRTF Science Center
General IRS data flow / timeline • Our validation dataset should be taken in the 1st three weeks of nominal operations (after SV). We will then have about four weeks to get back to the SSC with our “report” before the rest of the observations get released. (This should be about two months into normal operations). • We will get “privileged” access to the SINGS data in the archive at some point between L+4 and when the archive officially opens. We may also have access to some SV data (TBD). • All BCD’s will be taken from the archive, as processed by the automated IRS pipeline. These BCD’s will be inputs to the cube builder and feed our first delivery of “best post-BCD’s”. They will also double as important feed-back to the IRS pipeline development effort at the SSC.
General IRS data flow • Post-BCD processing (for the L+9 delivery) will be done by IRS sub-team, lead by Helene and PD. This will involve de-fringing of all 1D spectra, and co-addition of source and “background” spectra before subtraction. • All cubes and maps for the 1st cube release at L+21, will be created, validated (level 0 QA) and tuned by the IRS sub-team. • J.D., Danny, Helene and PD will all be trained in cube-making. • Tom and Helene will lead the product validation effort. • SINGS team members should become familiar with CUBISM and CubeView, and suggest enhancements for ongoing development. • Science products not created for SSC delivery will be created by a wider team of trained Cubists. All SINGS team members should have scientific input into cube production and be familiar with CubeView, since this is the whole point of making the glorious interface.
General IRS data flow (model) • Our 1st maps get delivered at L+15 [18]. These will be derived from the nuclear, HII and radial strip cubes for 1/3 of the sample or what’s in archive at L+12 [15]. • 1st week = select data for processing. Process all new data ? • weeks 1-4 = create cubes, use CubeView to create product maps and make first pass at QA for all products. • week 8 = deadline for SINGS team comments on the maps and decision on which products to incorporate into the SSC delivery. • weeks 9-12 = final run for maps (cubes ?) and final data quality check before delivery to SSC.
Some remaining data issues • How are we going to cross-calibrate the IRS maps (generated with cubism) and the IRAC or MIPS maps ? Things we might have to deal with include: • Flux offsets, morphological differences, gradients, etc. The fact that we can make 8m and 24m maps from the IRS data should help. Should have a quick way in CubeView to generate IRAC and MIPS-like maps from included transmission curves. • Also, what does “validation” mean for each sub-team ? Need a checklist from each sub-team that is known to all SINGS team members. • How do we alert the SSC to real problems with the data….not simply in our cube building ? • How will we co-ordinate deliveries, processing and analysis of targets across team (instrument) boundaries for our own use ? ….Synchronization. • Might need a “meta-team” to allow effective science extraction. • Do we completely de-couple this internal science work from the official data deliveries ?
