Final Product Generation and Release
2MASS Final Product Generation and Data Release
External Review Board - June 2001
I. Final Product Generation
- Pipeline processing generates Working Source Databases
- Expect ~1.3e9 point sources and ~4.7e6 extended sources in DB's
- "Detections" to low SNR to insure completeness
- Duplicate apparitions for sources in Tile overlap regions and multiply observed Tiles
- Artifacts from very bright stars and bright stars off Tiles, meteors
and other non-celestial artifacts
- Extended source databases include galaxies and galactic extended sources
- Objective of Final Product Generation (FPG) is to draw highly reliable,
complete Catalogs from Working Databases
- Select best apparition of Tiles for inclusion in release
- SNR thresholds for reliability and flux accuracy
- Incremental releases use conservative SNR>7 cut
- Consider lower threshold for final release, and characterize impact
- Point sources - chi-squared and N/M limits to remove radiation hits
- Identify and select correct apparition for duplicate sources
- Identify and remove/flag bright star and other artifacts
- Ancillary additions and clean-up:
- Point/Extended source links, contamination flagging
- Identification/blanking extended sources entries in untracked
seeing areas, galactic center
- Miscellaneous artifact clean-up and flag setting
- Extensive analysis to validate Catalog quality
- Prepare release documentation
- Prepare soft and hardcopies of release data
- Prepare IRSA tools/links to Catalogs
- 2MAPPS v3.0 front-loads some FPG tasks during scan processing, and
includes operations that help expedite FPG
- Global astrometric solutions and uncertainties
- Very bright star photometry to facilitate DB artifact identification
- Extended source/galaxy classification
- Meteor streak removal to minimize spurious detections
- Known asteroid and comet cross-identification
- Science-based diagnostics in QA to assist with final product analysis
- FPG schedule is ambitious and has little margin - 8 months from
end of final processing to data product release.
- FPG is Database- and Human-Intensive Task
- Delays in start of Operational Processing compress schedule for FPG
- Schedule risk mitigation steps include:
- Hardware augmentation to speed final processing. (Additional
Sun E220r committed by SSC)
- Descope amount of data run through final processing. (Q>5 or
minimum). Tradeoff is loss of additional good science data.
Deadline for useful decision is August-September.
- Front-loading FPG tasks into pipeline processing, as described
above.
- Improving DB task performance - goal is 6x, have demonstrated 4x
- Pipeline software engineers begin work on optimizing FPG tasks
as soon as Operational Processing begins.
- Mini-catalog generation test and validate FPG procedures.
Scheduled for late Nov.-Feb. time frame.
- Eliminate some FPG tasks, although no obvious candidates.
II. Final Product Distribution Modes Modeled on Successful
Distribution of Incremental Data Release Products
- Primary access mode to Catalog and Image data via on-line tools
of the Infrared Science Archive
- Catalog Searches (GATOR)
- Point Source Catalog Statistics Tool
- Interactive Atlas Image Retrieval - Quicklook Images (lossy-compressed Atlas Images)
- Batch Image Retrieval (January 2001) - Atlas Images (held at SDSCC) and Quicklook Images
- Extended Source Image Retrieval
- On-line Catalog and Quicklook Image access at
Centre de Donnees astronomiques de Strasbourg (CDS) via the
VizieR Service and
the Aladin interface (IDR1 and IDR2 in place - final products
under negotiation)
- Catalog files available via anonymous ftp from IPAC and mirror site
at CDS
- Catalogs available on and DVD-Rom
- Explanatory
Supplements available on-line, and on final release DVD-ROM. Hardcopy
under consideration.
Back to Agenda
Last Updated: 2 June 2001
R. Cutri - IPAC