NASA Planetary Data System Structure Mission Interfaces and

NASA Planetary Data System Structure, Mission Interfaces and Distribution Science Archives in the 21 st Century April 25 2007 PDS Project Scientist Reta Beebe 4/25/07 1

The Planetary Data System (PDS) PDS, a distributed archive, consists of Discipline and Support Nodes. Discipline nodes represent traditional areas of scientific investigation and target their work toward one or more of the diverse user communities within planetary science, providing assistance for both data providers and users. (T 14/Showalter is an example of discipline node service) Support nodes provide expertise and ancillary information needed to interpret and preserve the data and for the integration of the PDS system. Data nodes for specific instruments with large data volumes can be negotiated. The data structure must be compatible with PDS standards and node data is catalogued in and accessible through the PDS. The node contents are transferred to a discipline node of the PDS at the end of the mission. 4/25/07 2

4/25/07 3

PDS Management and Coordination Management duties are shared by a Program Manager, a Program Scientist and the Management Council (MC), composed of representatives from all nodes. The MC communicates via face-to-face meetings, monthly scheduled telecons and structured emails. PDS is tasked with supporting all missions of the Planetary Exploration Division and providing reliable and easy access to the archived data. This requires working with headquarters planners, proposers, instrument teams, missions and a broad spectrum of users. 4/25/07 4

Characteristics of the PDS Archive The PDS archives and makes available space-borne, ground-based, and laboratory experiment data from over 50 years of NASA-based exploration of comets, asteroids, moons, and planets. Many of the data sets are unique in that the observations cannot be duplicated. Planetary missions frequently have short or intermittent observing phases that result in extended calibration phases possibly resulting in limited accuracy of calibration and an incomplete understanding of instrument stability and characteristics. The archives include data products derived from a very wide range of measurements, e. g. , imaging experiments, gravity and magnetic field and plasma measurements, altimetry data, and various spectroscopic observations. The wide range of archival products and associated disciplines are fundamental reasons why PDS is organized as a confederation serving various science communities. 4/25/07 5

User and Customer Challenges User desires and expectations are becoming more complex and demanding with time as data and mission complexity increase. They want and need derived products, rapid access, flexible search capability, refined catalogues, readily accessible data visualization, analysis, and cross-correlation tools. Experienced users want interfaces with familiar data manipulation packages. Inexperienced users are “Google” oriented but PDS data are not always adaptable to the expected level of indexing. Interdisciplinary science requires parametric, geographic or spatial searches across missions, instruments and data sets. Lack of reduced data records frustrate users who wish to find and download highly processed data at specific localities for further analyses, time intervals etc. 4/25/07 6

Operational Challenges Users require that PDS supports heterogeneity for both technology and science - tools that run on a wide variety of platforms and adapt for different uses. Users expect to be able to search all of the PDS data holdings within the system and perform correlated searches for products. They expect online access and distribution of all the data holdings and to download data products of increasing sizes. Mission loads require PDS be able to scale critical functions, storage infrastructure to support the increase of volume, architecture to support the complexity of missions with many types of instruments and operations to support the increasing number of missions occurring concurrently. Aging and obsolete technology must be refreshed to ensure long term usability of the data and the system. Data in the archive must be periodically validated to ensure long term preservation. 4/25/07 7

Active or Planned Missions 4/25/07 8

Mission and Data Provider Challenges Flagships, PI led Discovery and New Frontiers missions, and missions in the Mars Program present a wide range of challenges. These challenges are amplified by the NASA policy to compete missions or instruments, bringing a constantly changing group of data providers to the PDS. Combinations of NASA funded teams based at individual institutions, internationally supplied instruments and the ensuing variable funding and physical locations of the teams further complicate budgeting, planning and data ingestion. 4/25/07 9

Mission and Data Provider Challenges(cont. ) Data volumes will continue to increase: Mars Reconnaissance Orbiter will produce ~100 TB Mars data volume is likely to be surpassed by that returned from the Moon in the next 10 years. Missions, instruments and data are becoming more complex: Rovers generate complex sets of products Flagship Missions strive to satisfy many science goals leading to a variety of instruments, complex structure of data returned, and extended missions with reduced budgets for archive production 4/25/07 10

Mission and Data Provider Challenges(cont. ) Smaller or more focused missions present challenges: The budget is limited and the funding profile differs from that used in initial design & planning Mission phases are compressed and require rapid PDS response PDS must supply tools to help with data archiving tasks, provide a Common Data Model, and participate as early as possible Problem: Intrinsic problems of sustaining mission science and data analysis budgets sharply limit production and archiving of higher order products. 4/25/07 11

History and Progress In the past the AOs did not include data planning requirements. Proposers were not challenged to present cost-effective plans to produce data useful to non-team members. Data pipeline planning was deferred until after launch. By the point in the mission when PDS began its interface, most teams had a partially completed pipeline and resisted PDS needs and standards as “Creeping Requirements”. This led to many data formats, variable documentation and low level products. Successful archiving requires PDS science node involvement from proposal briefing and assessment to user assistance and archive maintenance. Production of quality advanced products requires heavy involvement of Mission instrument scientists. 4/25/07 12

NASA Data Levels NASA Levels Product Description Raw Telemetry data stream as received at the ground station, with science and engineering data embedded. Level 0 Instrument science data (e. g. , raw voltages, counts) at full resolution, time ordered, with duplicates and transmission errors removed. Level 1 A Level 0 data that have been located in space and may have been reversibly transformed (e. g. , calibrated, rearranged) in a reversible manner and packaged with needed ancillary and auxiliary data (e. g. , radiances with the calibration equations applied). No resampling. Level 1 B Irreversibly transformed (e. g. , resampled, remapped, calibrated) values of the instrument measurements (e. g. , magnetic field strength). Higher levels Geophysical parameters mapped into uniform space time grids. 4/25/07 13

Mars Scout 2006 AO Data Rights Policy “Data must be made fully public through the PDS, in a usable form, as soon as practical but no later than six months following its collection. Mars Scout teams will be responsible for collecting the scientific, engineering, and ancillary information necessary to validate and calibrate the scientific data prior to delivery to the PDS. Archival data products shall include low-level (raw) data, high-level (processed) data, and derived data products such as maps, ancillary data, calibration data (ground and inflight), documentation, and related software or other tools necessary to interpret the data. All data products shall be documented, validated, and calibrated in physical units usable by the scientific community at large. ” (Sec. 6. 2. 4) 4/25/07 14

Cassini as an Example of Complexity Cassini Instruments CASSINI PLASMA SPECTROMETER (CAPS) - SWRI/San Antonio COSMIC DUST ANALYZER (CDA) - Max Planck/Heidelberg Univ of Chicago COMPOSITE INFRARED SPECTROMETER (CIRS) - GSFC/Greenbelt ION AND NEUTRAL MASS SPECTROMETER (INMS) - SWRI/San Antonio IMAGING SCIENCE SUBSYSTEM (ISS) -SSI/Boulder MAGNETOMETER (MAG) - Univ. College/London MAGNETOSPHERIC IMAGING INSTRUMENT (MIMI) - APL/Baltimore RADAR - JPL/Pasadena ALTIMETER -ASI/Rome-CORISTA/Naples RADIO AND PLASMA WAVE SCIENCE (RPWS) - Univ. of Iowa RADIO SCIENCE SUBSYSTEM (RSS) - JPL/ Pasadena NAIF SPICE FILES - JPL/Pasadena ULTRAVIOLET IMAGING SPECTROGRAPH (UVIS) - Univ of Colo/Boulder VISIBLE AND INFRARED MAPPING SPECTROMETER (VIMS) - Univ of Ariz/Tucson Huygens Instruments HUYGENS ATMOSPHERIC STRUCTURE INSTRUMENT (HASI) -Obs. de Paris-Meudon DOPPLER WIND EXPERIMENT (DWE) University of Bonn, Germany DESCENT IMAGER/SPECTRAL RADIOMETER (DISR) Univ of Ariz, Tucson GAS CHROMATOGRAPH MASS SPECTROMETER (GCMS) GSFC, Greenbelt, AEROSOL COLLECTOR AND PYROLYSER (ACP) SA/CNRS, Verrieres-le-Buisson, France SURFACE-SCIENCE PACKAGE (SSP) Open University. Milton Keynes, UK 4/25/07 15

Cassini as an Example of Complexity (cont. ) Cassini - 12 instruments with CDA & RADAR having 2 separate components Huygens - 6 instruments International participation and multiple funding agencies involved in both teams Cassini is an “old” mission -the AO did not require data planning and budgeting. 3 Years into primary mission - delivery of level 1 a data has been exemplary - but few higher order data products were included in the Data Management Plan The announcement concerning an 2 -year extended mission is scheduled for early May 4/25/07 16

Active or Planned Missions 4/25/07 17

Basic Problem - How Do We Get Higher-Order Products? With the range of instruments, level of maturity of instruments and range of user needs - the answer is that they should be planned into the missions and produced by the instrument teams. How? See P 7/Guinness. The role of the PDS should be that of maintaining standards and providing assistance across Planetary Science. In this framework the PDS in involved in the International Planetary Data Alliance (IPDA) to develop a core of standards, a data model, and tools that are used across the international planetary community. See P 4/ Crichton. 4/25/07 18

How do we make Products accessible? New Horizons (NH) has chosen to use FITS files - this is a PDS option. According to the “FITS Myth” this would solve all our problems and make PDS data easily accessible to our users. NH has a plasma package consisting of both the SWAP highsensitivity solar wind monitor to address Pluto atmospheric escape objectives and the PEPSSI energetic particle spectrometer. PEPSSI seems to be a simple instrument - flying by Jupiter, reading out its detector at specified times and storing the resulting parameters in a table, generating level 1 data that will be stored in the PDS for open user access. 4/25/07 19

New Horizons PEPSSI FITS Header SIMPLE = T / conforms to FITS standard BITPIX = 8 / array data type NAXIS = 1 / number of array dimensions NAXIS 1 = 112948 EXTEND = T BZERO = 0 / no offset BSCALE = 1 / default scaling factor MISSION = 'New Horizons' / Mission name HOSTNAME= 'NEW HORIZONS' / Host name (PDS terminology) HOSTID = 'NH ' / Host ID (PDS terminology) INSTRU = 'pep ' / Instrument APID = '0 x 691 ' / Application ID of science data MET = 30347555 / First packet MET (from instrument or HS bus) METEND = 30410623 / Last packet MET (from instrument or HS bus) MET_HK = 30347555 / MET from housekeeping used in header HSCOMPR = 'N/A ' / High-speed compression mode STARTMET= 30347555. 0 / Actual start time (in MET seconds) STOPMET = 30410623. 0 / Actual stop time (in MET seconds) EXPTIME = 63068. 0 / Observation duration (in MET seconds) METSRC = 'CCSDS_Header' / Source of above three times ARCHDATE= '2007/006' / Date of MOC archive file GRT = 17902. 653745551 / Ground receipt time from STP DATE = '2007 -03 -14 T 06: 15: 04' / Time file was created by SOC SOCVER = 1. 0 / SOC pipeline software version SOCLOC = 'TSOC ' / SOC location where processed (TSOC or CSOC) REQID = '--- ' / Request ID TARGET = 'EARTH ' / Target object TARGTYPE= 'Not defined' / Target object type CB 1 LOAD = '--- ' / Central Body 1 loaded CB 2 LOAD = '-- ' / Central Body 2 loaded CB 3 LOAD = '--- ' / Central Body 3 loaded REQDESC = '--- ' / Sequence description / notes REQCOMM = '--- ' / Sequence Comments SPCSEP 4/25/07 20

'***GEOMETRY SECTION*******************' SPCQUAL = 'RECONSTRUCTED' / QUALITY: PREDICT (poor); RECONSTRUCTED SPCSTAT = 'OK ' / SPICE status [OK or INCOMPLETE. . . ] SPCINST 0= 'NH_PEPSSI' / Starting SPICE Instrument or FRAME SPCINSTR= 'NH_PEPSSI' / Final SPICE Instrument or FRAME SPCMET 0 = 30347555. 0 / RAW MET timestamp SPCMETDL= 31534. 0 / [s] delta, (Mid-obs time) - (RAW MET) SPCCBTNM= 'EARTH ' / [text] Target input name SPCCB 1 NM= '--- ' / [text] CB 1 input name SPCCB 2 NM= '--- ' / [text] CB 2 input name SPCCB 3 NM= '--- ' / [text] CB 3 input name SPCCBTID= 399 / [SPICE ID] Target SPCCB 1 ID= -99999 / [SPICE ID] CB 1 SPCCB 2 ID= -99999 / [SPICE ID] CB 2 SPCCB 3 ID= 99999 / [SPICE ID] CB 3 SPCSCLK 0= '1/0030347555: 00000' / Spacecraft CLoc. K timestamp SPCINSID= -98400 / [SPICE ID] Instrument SPCSCID = -98 / [SPICE ID] Spacecraft SPCSCNAM= 'NH_SPACECRAFT' / [SPICE Name] Spacecraft SPCSCET = 221345236. 5662582 / [s past J 2000] Spacecraft mid-obs time, TDB SPCSCLK = '1/0030379088: 49998' / Mid-obs Spacecraft CLoc. K SPCSCDP = 1518954449998. 0 / [SCLK milli-ticks] Spacecraft mid-obs time SPCUTCID= '2007006 T 08: 46: 11. 382' / [ISO DOY] Spacecraft mid-obs time, UTC SPCUTCAL= '2007 -0106 T 08: 46: 11. 382' / [Cal d] Spacecraft mid-obs time, UTC SPCUTCJD= 'JD 2454106. 8654095' / [Julian d] Spacecraft mid-obs time, UTC SPCPSEP = 4/25/07 21

'******INSTRUMENT POINTING****************' SPCBRRA = 148. 8434045968733 / [degrees] Boresight RA, EME J 2000 SPCBRDEC= 58. 32115900534507 / [degrees] Boresight DEC, EME J 2000 SPCEMEN = 253. 4712691301747 / [degrees] EME J 2 k North Clk Angle, CW from UP SPCQA = 0. 879929725273648 / cos(theta/2) - Quaternion to transform SPCQX = 0. 03474712520028299 / sin(theta/2) * X - instrument vectors SPCQY = 0. 2707214153760393 / sin(theta/2) * Y - to EME J 2000 vectors SPCQZ = 0. 3888781700313765 / sin(theta/2) * Z - ***N. B. SPICE FORMAT SPCTSEP 0= '******Target: Target->S/C**************' SPCTCB = 'EARTH ' / [SPICE name] Target name SPCTSCX = -274841199. 710429 / [km] S/C vec wrt Target, X, EMEJ 2000 SPCTSCY = -726009069. 7018574 / [km] S/C vec wrt Target, Y SPCTSCZ = -304911211. 1260501 / [km] S/C vec wrt Target, Z SPCTSCVX= 29. 19172368431725 / [km/s] S/C vel vec wrt Target, X SPCTSCVY= 11. 01629447158524 / [km/s] S/C vel vec wrt Target, Y SPCTSCVZ= 4. 611396857053522 / [km/s] S/C vel vec wrt Target, Z SPCTRANG= 834025000. 235592 / [km] S/C range to Target center SPCTTGJD= 'JD 2454106. 8332104' / [Julian d] Time at Target, UTC SPCTSEP 1= '******Target: Target ->Sun**************' SPCTSOX = 39332569. 83228773 / [km] Sun vec wrt Target, X, EMEJ 2000 SPCTSOY = -130045351. 0295347 / [km] Sun vec wrt Target, Y SPCTSOZ = -56378947. 90190811 / [km] Sun vec wrt Target, Z SPCTSOVX= 29. 17975073615336 / [km/s] Sun vel vec wrt Target, X SPCTSOVY= 7. 406028350392652 / [km/s] Sun vel vec wrt Target, Y SPCTSOVZ= 3. 209743656588055 / [km/s] Sun vel vec wrt Target, Z SPCTSORN= 147096669. 3726706 / [km] Sun range to Target center SPCTSEP 2= '******Target: 4/25/07 22

Target->Earth. Observer**************' SPCTEOX = 0. 0 / [km] Earth observer vec wrt Target, X, EMEJ 2000 SPCTEOY = 0. 0 / [km] Earth obs vec wrt Target, Y SPCTEOZ = 0. 0 / [km] Earth obs vec wrt Target, Z SPCTEOVX= 0. 0 / [km/s] Earth obs vel vec wrt Target, X SPCTEOVY= 0. 0 / [km/s] Earth obs vel vec wrt Target, Y SPCTEOVZ= 0. 0 / [km/s] Earth obs vel vec wrt Target, Z SPCTEORN= 0. 0 / [km] Earth observer range to Target center SPCTEOJD= 'JD 2454106. 8332104' / [Julian d] Time at Earth observer SPCTSEPB= '******Target: Body-fixed info**************' SPCTSCLA= 21. 45769603204148 / [degrees] planetocentric Sub-S/C latitude SPCTSCLO= 23. 94635263603901 / [degrees] planetocentric Sub-S/C EAST longitude. SPCTSOLA= 22. 5255463654812 / [degrees] planetocentric Sub-Solar latitude SPCTSOLO= 61. 51046699593731 / [degrees] planetocentric Sub-Solar EAST long. SPCTNAZ = 253. 4712691301747 / [degrees] Target North Azimuth, CW from UP SPC 1 SEP 0= '******CB 1: CB 1 ->S/C**************' SPC 1 CB = 'UNKNOWN ' / [SPICE name] CB 1 name SPC 1 SCX = -1 E+32 / [km] S/C vec wrt CB 1, X, EMEJ 2000 SPC 1 SCY = -1 E+32 / [km] S/C vec wrt CB 1, Y SPC 1 SCZ = 1 E+32 / [km] S/C vec wrt CB 1, Z SPC 1 SCVX= -1 E+32 / [km/s] S/C vel vec wrt CB 1, X SPC 1 SCVY= -1 E+32 / [km/s] S/C vel vec wrt CB 1, Y SPC 1 SCVZ= -1 E+32 / [km/s] S/C vel vec wrt CB 1, Z SPC 1 RANG= 1 E+32 / [km] S/C range to CB 1 center SPC 1 TGJD= 'JD 2454106. 8654095' / [Julian d] Time at CB 1, UTC SPC 1 SEP 1= '******CB 1: CB 1 ->Sun**************' SPC 1 SOX = -1 E+32 / [km] Sun vec wrt CB 1, X, EMEJ 2000 SPC 1 SOY = -1 E+32 / [km] Sun vec wrt CB 1, Y SPC 1 SOZ = -1 E+32 / [km] Sun vec wrt CB 1, Z SPC 1 SOVX= -1 E+32 / [km/s] Sun vel vec wrt CB 1, X SPC 1 SOVY= -1 E+32 / [km/s] Sun vel vec wrt CB 1, Y SPC 1 SOVZ= -1 E+32 / [km/s] Sun vel vec wrt CB 1, Z SPC 1 SORN= -1 E+32 / [km] Sun range to CB 1 center SPC 1 SEP 2= '******CB 1: CB 1 4/25/07 23

Earth. Observer**************' SPC 1 EOX = -1 E+32 / [km] Earth observer vec wrt CB 1, X, EMEJ 2000 SPC 1 EOY = -1 E+32 / [km] Earth obs vec wrt CB 1, Y SPC 1 EOZ = -1 E+32 / [km] Earth obs vec wrt CB 1, Z SPC 1 EOVX= -1 E+32 / [km/s] Earth obs vel vec wrt CB 1, X SPC 1 EOVY= -1 E+32 / [km/s] Earth obs vel vec wrt CB 1, Y SPC 1 EOVZ= -1 E+32 / [km/s] Earth obs vel vec wrt CB 1, Z SPC 1 EORN= -1 E+32 / [km] Earth observer range to CB 1 center SPC 1 EOJD= 'JD 2454106. 8654095' / [Julian d] Time at Earth observer SPC 1 SEPB= '******CB 1: Body-fixed info**************' SPC 1 SCLA= -1 E+32 / [degrees] planetocentric Sub-S/C latitude SPC 1 SCLO= -1 E+32 / [degrees] planetocentric Sub-S/C EAST longitude. SPC 1 SOLA= -1 E+32 / [degrees] planetocentric Sub-Solar latitude SPC 1 SOLO= -1 E+32 / [degrees] planetocentric Sub-Solar EAST long. SPC 1 NAZ = -1 E+32 / [degrees] CB 1 North Azimuth, CW from UP SPC 2 SEP 0= '******CB 2: CB 2 ->S/C**************' SPC 2 CB = 'UNKNOWN ' / [SPICE name] CB 2 name SPC 2 SCX = -1 E+32 / [km] S/C vec wrt CB 2, X, EMEJ 2000 SPC 2 SCY = -1 E+32 / [km] S/C vec wrt CB 2, Y SPC 2 SCZ = -1 E+32 / [km] S/C vec wrt CB 2, Z SPC 2 SCVX= -1 E+32 / [km/s] S/C vel vec wrt CB 2, X SPC 2 SCVY= 1 E+32 / [km/s] S/C vel vec wrt CB 2, Y SPC 2 SCVZ= -1 E+32 / [km/s] S/C vel vec wrt CB 2, Z SPC 2 RANG= -1 E+32 / [km] S/C range to CB 2 center SPC 2 TGJD= 'JD 2454106. 8654095' / [Julian d] Time at CB 2, UTC SPC 2 SEP 1= '******CB 2: CB 2 ->Sun**************' SPC 2 SOX = -1 E+32 / [km] Sun vec wrt CB 2, X, EMEJ 2000 SPC 2 SOY = -1 E+32 / [km] Sun vec wrt CB 2, Y SPC 2 SOZ = -1 E+32 / [km] Sun vec wrt CB 2, Z SPC 2 SOVX= 1 E+32 / [km/s] Sun vel vec wrt CB 2, X SPC 2 SOVY= -1 E+32 / [km/s] Sun vel vec wrt CB 2, Y SPC 2 SOVZ= -1 E+32 / [km/s] Sun vel vec wrt CB 2, Z SPC 2 SORN= -1 E+32 / [km] Sun range to CB 2 center SPC 2 SEP 2= 4/25/07 24

'******CB 2: CB 2 ->Earth. Observer**************' SPC 2 EOX = -1 E+32 / [km] Earth observer vec wrt CB 2, X, EMEJ 2000 SPC 2 EOY = -1 E+32 / [km] Earth obs vec wrt CB 2, Y SPC 2 EOZ = -1 E+32 / [km] Earth obs vec wrt CB 2, Z SPC 2 EOVX= -1 E+32 / [km/s] Earth obs vel vec wrt CB 2, X SPC 2 EOVY= -1 E+32 / [km/s] Earth obs vel vec wrt CB 2, Y SPC 2 EOVZ= -1 E+32 / [km/s] Earth obs vel vec wrt CB 2, Z SPC 2 EORN= -1 E+32 / [km] Earth observer range to CB 2 center SPC 2 EOJD= 'JD 2454106. 8654095' / [Julian d] Time at Earth observer SPC 2 SEPB= '******CB 2: Body-fixed info**************' SPC 2 SCLA= -1 E+32 / [degrees] planetocentric Sub-S/C latitude SPC 2 SCLO= -1 E+32 / [degrees] planetocentric Sub-S/C EAST longitude. SPC 2 SOLA= -1 E+32 / [degrees] planetocentric Sub-Solar latitude SPC 2 SOLO= -1 E+32 / [degrees] planetocentric Sub-Solar EAST long. SPC 2 NAZ = -1 E+32 / [degrees] CB 2 North Azimuth, CW from UP SPC 3 SEP 0= '******CB 3: CB 3 ->S/C**************' SPC 3 CB = 'UNKNOWN ' / [SPICE name] CB 3 name SPC 3 SCX = -1 E+32 / [km] S/C vec wrt CB 3, X, EMEJ 2000 SPC 3 SCY = -1 E+32 / [km] S/C vec wrt CB 3, Y SPC 3 SCZ = -1 E+32 / [km] S/C vec wrt CB 3, Z SPC 3 SCVX= -1 E+32 / [km/s] S/C vel vec wrt CB 3, X SPC 3 SCVY= 1 E+32 / [km/s] S/C vel vec wrt CB 3, Y SPC 3 SCVZ= -1 E+32 / [km/s] S/C vel vec wrt CB 3, Z SPC 3 RANG= -1 E+32 / [km] S/C range to CB 3 center SPC 3 TGJD= 'JD 2454106. 8654095' / [Julian d] Time at CB 3, UTC SPC 3 SEP 1= '******CB 3: CB 3 ->Sun**************' SPC 3 SOX = -1 E+32 / [km] Sun vec wrt CB 3, X, EMEJ 2000 SPC 3 SOY = -1 E+32 / [km] Sun vec wrt CB 3, Y SPC 3 SOZ = -1 E+32 / [km] Sun vec wrt CB 3, Z SPC 3 SOVX= 1 E+32 / [km/s] Sun vel vec wrt CB 3, X SPC 3 SOVY= -1 E+32 / [km/s] Sun vel vec wrt CB 3, Y SPC 3 SOVZ= -1 E+32 / [km/s] Sun vel vec wrt CB 3, Z SPC 3 SORN= -1 E+32 / [km] Sun range to CB 3 center SPC 3 SEP 2= ' 4/25/07 25

''******CB 3: CB 3 ->Earth. Observer**************' SPC 3 EOX = -1 E+32 / [km] Earth observer vec wrt CB 3, X, EMEJ 2000 SPC 3 EOY = -1 E+32 / [km] Earth obs vec wrt CB 3, Y SPC 3 EOZ = -1 E+32 / [km] Earth obs vec wrt CB 3, Z SPC 3 EOVX= -1 E+32 / [km/s] Earth obs vel vec wrt CB 3, X SPC 3 EOVY= -1 E+32 / [km/s] Earth obs vel vec wrt CB 3, Y SPC 3 EOVZ= -1 E+32 / [km/s] Earth obs vel vec wrt CB 3, Z SPC 3 EORN= -1 E+32 / [km] Earth observer range to CB 3 center SPC 3 EOJD= 'JD 2454106. 8654095' / [Julian d] Time at Earth observer SPC 3 SEPB= '******CB 3: Body-fixed info**************' SPC 3 SCLA= -1 E+32 / [degrees] planetocentric Sub-S/C latitude SPC 3 SCLO= -1 E+32 / [degrees] planetocentric Sub-S/C EAST longitude. SPC 3 SOLA= -1 E+32 / [degrees] planetocentric Sub-Solar latitude SPC 3 SOLO= -1 E+32 / [degrees] planetocentric Sub-Solar EAST long. SPC 3 NAZ = -1 E+32 / [degrees] CB 3 North Azimuth, CW from UP SPCSEPS = '******S/C->SUN********************' SPCSSCX = 314170760. 42838 / [km] Sun vec wrt S/C observer, X, EMEJ 2000 SPCSSCY = 595972862. 4004619 / [km] Sun vec wrt S/C obs, Y SPCSSCZ = 248536385. 7896157 / [km] Sun vec wrt S/C obs, Z SPCSSCVX= 0. 01197328187009267 / [km/s] Sun obs vel vec wrt S/C obs, X SPCSSCVY= 18. 42232355282074 / [km/s] Sun vel vec wrt S/C obs, Y SPCSSCVZ= 7. 821140831297835 / [km/s] Sun vel vec wrt S/C obs, Z SPCSSCRN= 718092789. 6082171 / [km] S/C observer range to sun center SPCSSCJD= 'JD 2454106. 8376861' / [Julian d] Time at Sun SPCSEPE = '******EARTH>S/C********************' SPCESCX = -274823876. 7416071 / [km] S/C observer vec wrt earth, X, EMEJ 2000 SPCESCY = -726014560. 7946305 / [km] S/C obs vec wrt earth, Y SPCESCZ = -304913750. 5998584 / [km] S/C obs vec wrt earth, Z SPCESCVX= 29. 19172368431725 / [km/s] S/C obs vel vec wrt earth, X SPCESCVY= -11. 01629447158524 / [km/s] S/C obs vel vec wrt earth, Y SPCESCVZ= 4. 611396857053522 / [km/s] S/C obs vel vec wrt earth, Z SPCESCRN= 834025000. 2355919 / [km] S/C observer range to earth center SPCESCJD= 'JD 2454106. 8332104' / [Julian d] Time at Earth SPCKSEP = '******SPICE 4/25/07 26

KERNELS*******************' SPCKNUM = 37 / COUNT OF LOADED SPICE KERNELS: SPCK 0001= 'naif 0008. tls' / SPICE kernel 0001 SPCK 0002= 'new-horizons_194. tsc' / SPICE kernel 0002 SPCK 0003= 'pck 00008. tpc' / SPICE kernel 0003 SPCK 0004= 'nh_v 004. tf' / SPICE kernel 0004 SPCK 0005= 'nh_allinstruments_v 000. ti' / SPICE kernel 0005 SPCK 0006= 'nh_alice_v 002. ti' / SPICE kernel 0006 SPCK 0007= 'nh_lorri_v 002. ti' / SPICE kernel 0007 SPCK 0008= 'nh_ralph_v 002. ti' / SPICE kernel 0008 SPCK 0009= 'nh_rex_v 000. ti' / SPICE kernel 0009 SPCK 0010= 'nh_sdc_v 000. ti' / SPICE kernel 0010 SPCK 0011= 'nh_swap_v 002. ti' / SPICE kernel 0011 SPCK 0012= 'sb-2002 jf 56 -2. bsp' / SPICE kernel 0012 SPCK 0013= 'jup 204. bsp' / SPICE kernel 0013 SPCK 0014= 'plu 013. bsp' / SPICE kernel 0014 SPCK 0015= 'nh_nep_ura_000. bsp' / SPICE kernel 0015 SPCK 0016= 'de 413. bsp' / SPICE kernel 0016 SPCK 0017= 'nh_pred_20060119_20070401_od 020. bsp' / SPICE kernel 0017 SPCK 0018= 'nh_pred_20060119_20070101_od 021. bsp' / SPICE kernel 0018 SPCK 0019= 'nh_pred_20060119_20100601_od 022. bsp' / SPICE kernel 0019 SPCK 0020= 'nh_pred_20060119_20100101_od 032. bsp' / SPICE kernel 0020 SPCK 0021= 'nh_pred_20061001_20100101_od 040. bsp' / SPICE kernel 0021 SPCK 0022= 'nh_pred_20070307_20100101_od 041. bsp' / SPICE kernel 0022 SPCK 0023= 'merged_nhpc_2006_v 011. bc' / SPICE kernel 0023 SPCK 0024= 'merged_nhpc_2007_01_v 006. bc' / SPICE kernel 0024 SPCK 0025= 'merged_nhpc_2007_02_v 007. bc' / SPICE kernel 0025 SPCK 0026= 'nhpc_2007_060_07. bc' / SPICE kernel 0026 SPCK 0027= 'nhpc_2007_061_07. bc' / SPICE kernel 0027 SPCK 0028= 'nhpc_2007_062_07. bc' / SPICE kernel 0028 SPCK 0029= 'nhpc_2007_063_07. bc' / SPICE kernel 0029 SPCK 0030= 'nhpc_2007_064_07. bc' / SPICE kernel 0030 SPCK 0031= 'nhpc_2007_065_07. bc' / SPICE kernel 0031 SPCK 0032= 4/25/07 27

'nhpc_2007_065_07. bc' / SPICE kernel 0031 SPCK 0032= 'nhpc_2007_066_06. bc' / SPICE kernel 0032 SPCK 0033= 'nhpc_2007_067_05. bc' / SPICE kernel 0033 SPCK 0034= 'nhpc_2007_068_04. bc' / SPICE kernel 0034 SPCK 0035= 'nhpc_2007_069_03. bc' / SPICE kernel 0035 SPCK 0036= 'nhpc_2007_070_02. bc' / SPICE kernel 0036 SPCK 0037= 'nhpc_2007_071_01. bc' / SPICE kernel 0037 INSTSSEP= '****************************' BLOCKCNT= 187 / Number of data blocks BLOCKSIZ= 604 / Size of each data block PHACNT = 1790 / Number of PHAs PHASIZ = 14 / Size of each PHA STATINT = 1 / Status interval (seconds) MACBLCKS= 1679 / Number of macro blocks free TLMVOL = 0 / Telemetry volume produced (KB) WTCHADDR= 0 / Memory watch address WTCHMEM = 0 / Watched memory (pg. no) WTCHDATA= 48644 / Watched memory PEPSWVER= 3 / Software version number ALARMID = 0 / Latest Alarm Id ALARMTYP= 0 / Latest alarm type ALARMCNT= 0 / Count of alarms CMDEXEC = 1 / Commands executed CMDREJCT= 0 / Commands rejected MACEXEC = 0 / Macro commands executed MACREJCT= 0 / Macro commands rejected MACROID = 0 / Id of most recent macro executed MACROLRN= 0 / Macro learn mode MONRESP = 0 / Monitor response WRITEENB= 0 / Memory write enable HVPSCURR= 0 / Expansion Bus address 0 x 006 HVPSVOLT= 0 / Expansion Bus address 0 x 008 BIASCURR= 0 / Expansion Bus address 0 x 00 A BIASVOLT= 0 / Expansion Bus address 0 x 00 C 4/25/07 28

PEPSTAT = 15 / Expansion Bus address 0 x 000 DVOLTP 5 = 668 / +5 V digital volt. / LVPS ADC (mux sub-addr 0) AVOLTN 5 = 666 / -5 V analog volt. / LVPS ADC (mux sub-addr 1) VOLTP 2 = 654 / +2. 5 V volt. / LVPS ADC (mux sub-addr 2) VOLTN 5 = 605 / -5 V volt. / LVPS ADC (mux sub-addr 3) VOLTP 15 = 789 / +15 V volt. / LVPS ADC (mux sub-addr 4) VOLTN 15 = 723 / -15 V volt. / LVPS ADC (mux sub-addr 5) DCURRP 5 = 217 / +5 V digital curr. / LVPS ADC (mux sub-addr 6) ACURRP 5 = 193 / +5 V analog curr. / LVPS ADC (mux sub-addr 7) CURRP 2 = 403 / +2. 5 volt curr. / LVPS ADC (mux sub-addr 8) CURRN 5 = 582 / -5 V curr. / LVPS ADC (mux sub-addr 9) CURRP 15 = 75 / +15 V curr. / LVPS ADC (mux sub-addr 10) CURRN 15 = 481 / -15 V curr. / LVPS ADC (mux sub-addr 11) PRIMCURR= 401 / LVPS ADC (mux sub-addr 12) LVPSTEMP= 441 / LVPS ADC (mux sub-addr 13) ENGYTEMP= 112 / LVPS ADC (mux sub-addr 14) HVPSTEMP= 464 / LVPS ADC (mux sub-addr 15) ADDR 12 C = 0 / Software read address RSLT 12 C = 0 / Software read value END 4/25/07 29

Imbedding PDS Personnel With the increase in the Mars Program and smaller missions, it has become apparent that imbedding PDS personnel within a mission is an effective way to insure that an efficient data pipeline is developed, but this does not assure higher order products. Mission Data Management requires expert input to size and cost the data to ensure an adequate archiving budget. PIs recognize this and many include a PDS-based individual, assigned with this task. Other missions negotiate this involvement. Development of a data management plan during Phase A to scope the data management task should be a required component. 4/25/07 30

Ongoing Challenges Respond to an increasing spectrum of demands from a diverse and growing community of users Interface with more than 20 missions at a time in various development phases Ingest data from increasingly complex instruments Educate data providers Add non-mission data from individuals, laboratories and observatories Provide useful links to related national and international data Incorporate new storage/distribution technologies into preservation planning Adapt to new modes of data access for users (animation formats? ) 4/25/07 31

Ongoing Challenges Although many of these challenges are planetary oriented and efforts to face them are underway, the last two, in the form of reliability of archive media and an appropriate format for science animations, are topics that involve many of you. I would propose that a valuable function of this group would be to identify mutual problems, define finite projects with a project leader, a working group and defined period for addressing the problem and reporting back to the participating group. In other words -- go for specific, identifiable accomplishments. 4/25/07 32

4/25/07 33

Altimeter Participants The algorithm/software development is being done by CORISTA, Viale Kennedy 5, 80125 Naples, Italy, CORISTA = Consorzio Di Ricerca Su Sistemi Di Telesensori Avanzati This software has been built into a processing and archiving facility by Alcatel Alenia Space-Italy in Rome and was funded by ASI (Agenzia Spaziale Italiana, 00198 Rome). Dr. Philip S. Callahan/JPL philip. s. callahan@jpl. nasa. gov 4/25/07 34