1 / 11

Lunar Archives in PDS Ed Guinness PDS Management Council Washington, DC April 3, 2008

Lunar Archives in PDS Ed Guinness PDS Management Council Washington, DC April 3, 2008. Lunar Reconnaissance Orbiter. Launch: October 28, 2008 (nominal, will probably slip) Mission: 1 year under ESMD, then extended mission under SMD Payload:. LRO Archive Development Work.

ion
Download Presentation

Lunar Archives in PDS Ed Guinness PDS Management Council Washington, DC April 3, 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lunar Archives in PDS Ed Guinness PDS Management CouncilWashington, DCApril 3, 2008

  2. Lunar Reconnaissance Orbiter • Launch: October 28, 2008 (nominal, will probably slip) • Mission: 1 year under ESMD, then extended mission under SMD • Payload:

  3. LRO Archive Development Work • PDS Archive Development Work for LRO: • Help Project write Data Management and Archive Plan • Participate in LRO Data Working Group biweekly meetings led by LRO Project • Help instrument teams design data products and additional archive components, documented in Data Product SISs and Archive Volume SISs • Conduct peer reviews of raw and derived data product design • Conduct tests of data delivery from instrument teams to PDS nodes • Help teams provide input to PDS Catalog and PDS Data Dictionary about LRO data sets • Lead node for PDS is the Geosciences Node

  4. LRO Archive Development Status * EDR = raw data products RDR = derived data products

  5. LRO Concerns • SPICE • Instrument teams are expecting SPICE kernels to be available for derived product generation. • NAIF is uncertain whether LRO mission operations is fully prepared to generate and deliver SPICE kernels. • LOLA product design delayed • Data provider was waiting for instrument tests; now has necessary instrument details and is catching up. • Raw products have been designed and reviewed. • Derived product design is in progress. • LROC product design delayed • Data provider is busy with instrument preparation. • EDR product design is in draft form, peer review starting. • Derived product design has begun; and not reviewed.

  6. LCROSS (Lunar CRater Observation and Sensing Satellite) • Launch: Piggyback on LRO (nominally October 28, 2008) • Mission: Drop empty fuel container on surface and observe impact; then impact itself • Payload:

  7. LCROSS Archive Development Work • PDS Archive Development Work for LCROSS: • Help Project write Archive Plan • Lead bimonthly Data and Archive Working Group meetings • Help the LCROSS instrument lead (one person for all instruments) design data products and additional archive components, documented in Data Product SIS and Archive Volume SIS • Conduct peer review of raw and derived data product design • Conduct tests of data delivery from LCROSS to PDS nodes • Help LCROSS provide input to PDS Catalog and PDS Data Dictionary • Lead node for PDS is the Geosciences Node

  8. LCROSS Archive Status • Status of archive tasks: • Archive Plan complete • Data product design in progress but behind schedule • Geosciences Node gave PDS Archiving presentation at LCROSS Astronomy Workshop • Issues: • Archive development is behind schedule • Instrument team is very small (2-3 people) and probably overextended • Many canceled meetings and slipped delivery dates • Peer reviews should have started April 1, but as yet no documents or sample data have been provided to review • Uncertainty about Earth-based observations • Data types and formats are unknown • How to coordinate and simplify archives from several sources, including many who are inexperienced at producing PDS archives

  9. GRAIL • Discovery mission to measure lunar gravity field • Maria Zuber, MIT, is the PI • Uses two small spacecraft with the trailing spacecraft chasing the leading one (heritage from terrestrial GRACE mission) • Launch fall 2011 • Operations from early 2012 until lunar eclipse in June 2012 • Data Management Plan in development • Dick Simpson to work with data producers as our Radio Science Advisor • Raw data to be handled by JPL • Expect derived products (gravity coefficients) from science team • Secondary payload LADEE (Lunar Atmosphere and Dust Environment Explorer) carries a dust counter and neutral mass spectrometer.

  10. PDS Liaison to ESMD • Jeff Plescia, APL, is the PDS liaison to the ESMD program. • Works with ESMD to understand and clarify its requirements on PDS, especially implications for lunar geodesy and cartography. • Advises the Geosciences Lunar Data Node on recovery of older lunar data sets (e.g. Apollo), helping to determine feasibility, to set priorities, and to review completed archives. • Reports to Geosciences Node manager.

  11. LASER Program • Call included request for proposals to recover lunar data considered important to the science and exploration programs • Selections to be announcement shortly • A mechanism is needed between LASER Program and PDS to enable PDS to plan for such data recovery projects • How does PDS know what data recovery proposals are selected in order to plan schedules and resources for working with PI’s to get the recovered data into PDS? • How does NASA HQ track that the proposed data sets, in fact, successfully make it into the PDS archive collections?

More Related