10
Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Embed Size (px)

Citation preview

Page 1: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Rings Node Migration Plan

Mark & MitchPDSMC, UCLA

November 28-29, 2012

Page 2: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

PDS4 Migration Overview

• In addition to several rings specific PDS3 data sets, we maintain a number of secondary data sets including:• Atmospheres• Cassini CIRS and Cassini UVIS

• Imaging• Cassini ISS and Cassini VIMS• Voyager ISS

• SBN• New Horizons Jupiter - LORRI

• We plan to take the lead in the data migration for Cassini CIRS & Voyager ISS.

Page 3: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

• FY13 & FY14• Derived Astrometric Data• Derived Ring Radial Profiles – three Cassini instruments• Cassini CIRS • Voyager ISS• Derived Ring Radial Profiles – six ground based data sets

PDS4 Migration Overview (3)

Page 4: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Migration Plan FY13/FY14

• Astrometry• ASTROM_0101 – April 2013 (build 3b).• This is the data set we've been using for prototyping.• Currently updating the prototype for build 3a.

• ASTROM_0001 – Low hanging fruit• Similar to ASTROM_0101 so software will support with

minimum modification.• Plan to add this PDS3 data set as a new collection to the

bundle we developed for ASTROM_0101.

Page 5: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Migration Plan FY13/FY14 (2)

• Cassini derived ring occultation profiles• UVIS, VIMS and RSS teams have generated ~ 200 ring

profiles using similar formats.• All were designed with PDS4 in mind.• Migration will require developing Rings Node Data

Dictionary.• Peer review with PDS3 & PDS4 labels and organization.• Start in FY13; finish in FY14.

Page 6: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Migration Plan FY13/FY14 (3)

• Cassini CIRS• Reformatting pipeline extension (1)• The team delivers volumes in the “Vanilla” variable

length record format. – Detectors, targets, modes are all mixed together.

• Our pipeline breaks apart data files by detector & observation using fixed-length records.• All efforts were tabled last year when the version 3.1

delivery broke our pipeline.• Version 3.2 will be stable ~ January 2013 – we hope.

Page 7: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Migration Plan FY13/FY14 (3)

• Cassini CIRS (2)

FY13 plan: • Update the PDS3 reformatting pipeline and begin

producing reformatted PDS3 volumes.• Begin PDS4 migration pipeline development.• Automated PDS4 migration pipeline in place in FY14.

Page 8: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Migration Plan FY14/FY15 (1)

• Voyager ISS processed data sets• Original PDS3 data in one, 38 volume, data set. • New data in four data sets (Jupiter, Saturn, Uranus,

Neptune).• Uncompressed raw, calibrated, and geometrically

corrected images.• Will begin migration development in FY14; finish in FY15.

Page 9: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

Migration Plan FY14/FY15 (1)

• 28 Sgr Occultations of Saturn's rings• Six data sets of ground based observations.• Combine aspects of the astrometry and occultation data

sets previously migrated.• Will begin and finish in FY14.

Page 10: Rings Node Migration Plan Mark & Mitch PDSMC, UCLA November 28-29, 2012

ASTROM_0101

ASTROM_0001

Cassini Occultations

Cassini CIRS

Reformatting Pipeline

PDS4 Migration Pipeline

Voyager ISS

Earthbased Occultations

FY13 FY14 FY15

Summary

Questions?