# Presentation: 072716

## SBN Report to MC

- Mike A’Hearn

- Management Council

- 2001 Jul 10-11

## Topics

- Introductions
- Progress vis a vis Plan
- Issues for the Future

- Management Council

- 2001 Jul 10-11

## Introductions

- Ludmilla Kolokolova
- Will be joining SBN to replace Ed Grayzeck later this month
- Currently at U. Florida
- Expert on comets and dust
- Author of review chapters, e.g., in Comets II book
- Author of more nearly 100 refereed articles
- Experienced database manager

- Management Council

- 2001 Jul 10-11

## Active Missions

- Management Council

- 2001 Jul 10-11

## Active Missions p2

- Management Council

- 2001 Jul 10-11

## Other Planned Items

- Management Council

- 2001 Jul 10-11

## Accomplishments Not in Plan

- Management Council

- 2001 Jul 10-11

## Issues for Discussion

- Non-NASA missions
- On-the-fly calibration
- Minimizing formats

- Management Council

- 2001 Jul 10-11

## Non-NASA Missions

- Issue
- Current PDS monthly reporting asks NASA for advice on how to deal with non-NASA missions (mainly foreign but DoD also relevant)
- NASA needs us to recommend the approach, which they can then approve or veto, *e.g.,* via POP process
- Proposed approach
- Non-NASA missions are identified by anyone - DN, CN, PDS Mgmnt, NASA
- Lead discipline node (or nodes) decide whether US investigators would benefit from access to data
- If no, no further action across all of PDS
- If yes
- See next page!

- Management Council

- 2001 Jul 10-11

## Non-NASA Missions p2

- If mission has value to US investigators
- and if DN reports some likelihood of public, PDS-compatible archiving
- CN &/or DN report interest to NASA HQ via PE (automatic if US instruments are involved)
- PE ensures archiving commitment in MOU with non-NASA agency
- DN works with foreign mission to ensure PDS-compatible, publicly available archive
- Lead DN and all relevant supporting nodes put appropriate resources in next POP proposal budget (NASA’s chance to say yes or no)
- Support services (NAIF, DSN, etc.) that mainly help the project do not expend resources unless HQ approves in POP process

- Management Council

- 2001 Jul 10-11

## Non-NASA Missions p3

- Additional Points
- PDS (via PE) should be involved in MOU discussions from the beginning
- PDS must be kept informed of status and relevant content of MOU
- Arrangements will probably vary from one mission to another
- These missions should, in POP process, be presented at lower priority than NASA’s missions

- Management Council

- 2001 Jul 10-11

## On-the-fly Calibration

- Long-lived instruments gradually improve calibration retroactively
- Probably already experienced in some Mars missions
- Now becoming an issue for SBN (Rosetta, Dawn, New Horizons)
- Galileo did not archive calibrated products but this was as an exception
- Likely will be an issue for Cassini
- If data volumes are small, instrument teams can recalibrate entire historical dataset periodically
- Does not work for large volumes of data

- Management Council

- 2001 Jul 10-11

## On-the-fly p2

- Recommend long-term goal  - PDS steps up and supports software (with requirements on delivered software) for on-the-fly calibration of selected missions
- On-the-fly calibration is routine at STScI
- On-the-fly calibration is expensive, but better scientifically for a long-lived mission (but NOT for a short duration mission!)
- PDS must be more familiar with the data than is often the case now
- Instrument teams must provide software and data under rigidly controlled conditions
- Must start with some simple example cases to estimate scope of problem and to demonstrate capability

- Management Council

- 2001 Jul 10-11

## Limiting Formats

- On-the-fly calibration will require minimizing formats
- Users want number of formats minimized for ease of reading into analysis environments
- We continue to allow almost anything
- Are nodes officially authorized to limit formats?

- Management Council

- 2001 Jul 10-11