Development Report

Engineering Node

August 2006http://pds.nasa.gov

3 August 2006 Development Report 2

Topics

• Validation Tool

• Cassini Archive Tracking System (CATS)

• NSSDC Interface

• IPDA Cross-Catalog Search Prototype

Validation Tool

3 August 2006 Development Report 4

Accomplishments

• Requirements Review (Feb 2006)– Reviewed version 1.1 of the Requirements Document resulting in 66

Requests for Action.

• Reported status and plan to MC (Mar 2006)– Approval to move forward with level 3 requirement 1.5.3 approved.

• Released version 1.2 of the Requirements Document (Apr 2006)– Resulted in 22 more RFAs.

• Requirements Status and Preliminary Design Telecon (Jun 2006)– Issues involving the requirements were presented.– The meeting resulted in 11 action items.

• External Code Walk-through (Jun 2006)– Several general comments and suggestions were offered by the review

board as well as over 50 specific comments regarding the source code.

• Status and Beta-Test Process Telecon (Jul 2006)– Presented the test approach and plan for the renamed Alpha Test.– The meeting resulted in 8 action items.

• Released version 1.3 of the Requirements Document (Jul 2006)– Waiting for comments.

3 August 2006 Development Report 5

Requirements Status

• Version 1.3 of the Validation Tool Requirements document was distributed to the PDS Tech Staff on July 25, 2006.

• RFA Status Summary (88 Total)– 16 Open Related to data object validation.– 39 Addressed Incorporated into version 1.3 of the

document.– 03 Tabled Issues to be addressed at a later date.– 30 Closed Finally put to bed.

• Status Legend– Open An action has yet to be defined.– Addressed An action for the RFA has been defined but

not yet accepted by the author.– Tabled Waiting on some other milestone before the

RFA can be addressed.– Closed The action defined for the RFA was accepted

by the author.

3 August 2006 Development Report 6

Outstanding Action Items

• June 1 Telecon (Requirements Status and Preliminary Design)• 5. Command-Line Options (All Node Tech Leads; due 21-Jul-2006)

Nodes will send comments on the command-line options and their preferred default state. EN will distribute the summary.

• 7. Release Matrix (Hardman; due 28-Jul-2006)

EN will prepare a matrix detailing the requirements/capabilities targeted for the first release of the Validation Tool.

• 8. Label Specific Rules (Hardman; due 21-Jul-2006)

EN will send a list of label specific rules to the nodes defining the rules that are included in releases of the validation tool.

• 9. Sample Reports (Hardman; due 28-Jul-2006)

EN will send out sample reports to the nodes for review.• 11. Data Object Validation (Hardman; due 28-Jul-2006)

EN will provide a list of initial data objects that will be supported by the validation tool.

• July 13 Telecon (Status and Beta-Test Process)– All action items have been completed except for #1, which addresses

the action items from the previous telecon (listed above).

3 August 2006 Development Report 7

Alpha Test Release

• Release 0.2.0 of the Validation Tool was made available to the Atmospheres, Geosciences and PPI Nodes for alpha testing.

• Intent of the alpha and beta testing phases– Get the tool in the hands of the users early on in development– Validate tool direction and testing strategy– Provide opportunity for the Nodes to submit test cases for the tool

• In conjunction with this release is the release of the Next Generation Tools web page.

– http://pds-engineering.jpl.nasa.gov/index.cfm?pid=4&cid=71– This web page contains links to all of the documentation pertaining to

the definition, design, development and test of the Validation Tool to date.

3 August 2006 Development Report 8

3 August 2006 Development Report 9

Plan

• Alpha Test (Aug 1 - Aug 18, 2006)– Atmospheres, Geosciences and PPI

• Alpha Test Status Telecon (The week of Aug 21, 2006)– Present the results of the first phase of testing.

• Beta Test (Aug 28 - Sept 15, 2006)– Imaging, Rings and Small Bodies

• Post-Beta Test Telecon (The week of Sept 18, 2006)– Present the results of the second phase of testing.

– Address and determine the readiness for operational delivery.

• Operational Delivery of version 1.0 (Oct 2006)

Cassini Archive Tracking System (CATS)

3 August 2006 Development Report 11

Accomplishments

• Installed a test instance of CATS at the EN. (Apr 2006)– The same version utilized by Cassini was installed.

• Configured the test instance with Phoenix policy. (May 2006)– Policy for the Phoenix mission was provided by S. Slavney.

• Members of Geosciences and the Phoenix Mission have performed testing. (Jun - Jul 2006)

– Comments were provided by G. Furr and S. Slavney.– Minor issues with regard to the available reports and their content.– A couple of other minor nits were found.

• The impression is that the functionality currently provided by CATS is sufficient for use by the Phoenix Mission.

3 August 2006 Development Report 12

Plan

• Short-Term (Dec 2006)– Deploy an instance of CATS for Phoenix with minimal changes.

• Long-Term (?)– Evaluate CATS functionality and how it fits into PDS .– Map that functionality to PDS requirements (Level 3 and 4).– Consider expanding functionality to include tracking deliveries to

NSSDC.

NSSDC Interface

3 August 2006 Development Report 14

Accomplishments

• Coordination Teleconferences (Jun, Jul, Aug, Sep, Oct 2005, Feb,

Jul 2006)

• Initial version of the NSSDC MPGA software delivered, installed

and tested at EN. (Aug 2005 - Jan 2006)

– Completed Test Plan tailored to award fee item.

– Completed Test Phases I, II and III limited to 2-gigabyte volumes.

– Completed test result capture and documentation.

• Follow on version of the MPGA software delivered, installed and

tested at EN. (May 2006)

– AIP packages of roughly 4 and 50 gigabytes in size were created

verifying that the 2-gigabyte limit had been exceeded.

• Paper presented at the 2006 IEEE Mass Storage Systems and

Technologies (MSST2006) conference. (May 2006)

– “A Classification and Evaluation of Data Movement Technologies for

the Delivery of Highly Voluminous Scientific Data Products”

3 August 2006 Development Report 15

Recent Telecon (Jul 2006)

• NSSDC MPGA Software Status– Not much progress since May since the main developer had been

temporarily reassigned.– Work still needed for the attribute map, NSSDC ID determination and

the pipeline.

• Action Items– Provide information to NSSDC regarding a scenario for how the PDS

will utilize the MPGA software in an operational environment. (EN)– NSSDC and PDS EN will coordinate schedules in the next couple of

weeks before the PDS MC meeting. (NSSDC and EN)– NSSDC will provide PDS EN with some information regarding Don

Sawyer’s work on the attribute mapping. (NSSDC)

3 August 2006 Development Report 16

Plan

• Deliver a production ready version of the MPGA software (NSSDC - Oct 2006)

– Incorporate PDS specific attributes in AIP generation

– Incorporate determination of unique NSSDC storage identifiers

– Simplify and/or provide interface for MPGA configuration and execution

– Support DVD-sized (4 GB) and up to 50 gigabyte volumes.

• Receive and test the production ready version of the MPGA software (EN - Oct 2006)

• Test data transfers directly from Discipline Nodes to NSSDC (Nodes - Nov 2006)

– Geosciences, Rings and Small Bodies have shown interest in participating.

• Prepare documentation for Distribution of Data to the NSSDC from PDS nodes (EN - Oct-Dec 2006)

– Policy for electronic delivery to NSSDC.

– PDS specific procedures for using the MPGA software.

• Obtain MC approval for release

IPDA Cross-CatalogSearch Prototype

3 August 2006 Development Report 18

Background

• Simple prototype demonstrating a query capability across the PDS and ESA PSA catalogs.

• Leverage ongoing work with the PDAP prototype.

– Reuse code for converting VOTables to Profiles.

• Data Set View not well suited for this prototype, but it’s workable.

3 August 2006 Development Report 19

3 August 2006 Development Report 20