120 likes | 205 Views
Common Archive Observation Model (CAOM). What is it and why does JWST care?. Roadmap for the Space Telescope Science Institute Archive and Data Center https://trac.stsci.edu/trac/SADC/wiki/WikiStart/ac_roadmap. Strategic Goals
E N D
Common Archive Observation Model (CAOM) What is it and why does JWST care?
Roadmap for the Space Telescope Science Institute Archive and Data Centerhttps://trac.stsci.edu/trac/SADC/wiki/WikiStart/ac_roadmap Strategic Goals • Increase the science research productivity of the astronomical community through the products and services we provide. • Enable exemplary science through the development of science products and services. • Maximize the long-term archival benefit of the data holdings within the STScI Archive and Data Center. • Actively collaborate with other archive centers to increase the overall productivity and science return to the research community. • Promote and engage the user community on the value and use of the STScI data holdings.
Public Science Multi-Mission Archive Advantages • Primary point of entry for access to browse and access SCIENCE data for ALL missions housed at STScI. • Browser-based search and visualization tools. • All data is available on disk for immediate access • proprietary rights can be enforced • Identify related datasets from different missions to enable multi-wavelength science analysis. • Including community contributed or mission generated high level science products. • Virtual Observatory compliant data access. • Users can easily discover data, retrieve and analyze using VO tools. • Inter-archive access Improves scientific return and impact for all missions
Benefits of Public Science Archive for JWST • Integration with other mission archives increases scientific impact of JWST. • Meets JWST requirement to provide user access using VO protocols and services. • Reduces work – interfacing JWST to PSA simpler • Decouples core operational archive from external access. • Operational systems will have a more predictable load • Highly variable user access will not interfere with operations • MAST already committed to implement this for (15) existing missions archives over next 2-3 years. • Incorporating JWST into this ongoing work now allows JWST data to influence the design • Public archive will allow data access as soon as JWST launches.
Common Archive Observation Model • Unified model for metadata for all archives • Enable cross-mission searches and enhance scientific value • Simplify access with common set of software • Model is extensible for mission specific metadata if needed • Layered software • Use VO protocols for all services (internal & external) • Write access services once, use for all missions • Lower maintenance costs • CADC developed and implemented CAOM v1 • Collaborate with CADC to implement/extend model • Use CADC lessons learned and implement v2
Common Archive Observation Model v2.0Summary of main concepts • OBSERVATION • Metadata describing the characteristics of an observation • simpleObservation : describes a single set of observed photons • compositeObservation : describes the combination of 2 or more simpleObservations • Proposal, Telescope, Instrument, Target, Combination type, etc • PLANE (1:n planes per observation) • Metadata describing a distinct construct within the observation • e.g. multiple detectors or filters would each be a plane • Position (Footprint), Energy, Time, Polarization, Metrics • PRODUCT (1:n products per plane) • Metadata describing a distinct product within each plane • e.g, image/spectrum , errors, weights, previews • Includes pointer (URI) to actual data files • ARTIFACT (0:1 artifacts per product) • Metadata describing each unique product • SpatialWCS, SpectralWCS, TemporalWCS, PolarizationWCS • Queries can access any of these layers • Will create views for VO defined data models e.gObsCore and protocols e.g. ConeSearch, SIAP, SSAP
CAOM development overview • Start with limited set of heavily used archives • GALEX, HLA, MAST SIA/SSA • Leave mission databases unchanged and only create combined CAOM database for science queries • CADC has multiple CAOM databases with mission specific extensions AND harvests a combined set of CAOM-core data to a single database for science queries • Goal to have prototype database by end of March for data services working group to develop queries against • Use experience to refine data model with CADC and update ingest tools • Map remaining missions into model and harvest metadata • Include JWST SID archive, and JWST archive as it develops
Current Status • Created scripts to construct CAOM database with all relationships • Created spatial functions, STC/S conversion functions • Database loading • Scripts to copy data from mission db to CAOM db • IDL tool to harvest data from headers and/or mission db and load CAOM db • GALEX imaging survey – done • HLA images – done • MAST SIA/SSA tables – in progress • Implement VO TAP service – about to start
Proposed Plans • Map rest of MAST missions metadata to CAOM • Ingest metadata into prototype db • Look at possible JWST science data – map to CAOM to see if CAOM extensions are required. • Look at possible inclusion of CAOM directly into JWST mission archive • Simplify harvesting of JWST metadata into multi-mission access • Would allow re-use of access services for internal users