Atmosphere SIPS Software Archive and Delivery

This project has commands: archive and queue

Archive Command

creates tarballs of software for products we are actively delivering to LAADS. There are 3 files for each product which we will deliver per the agreement:

• software tarball
• test data tarball
• summary PDF

In addition, the archive for each product includes a summary JSON file and a dependencies sub-directory which links to the tarballs for all software dependencies.

Queue Command

Use this to queue up the files generated by archive for delivery to LAADS. Messages are sent to rivet to make available via our SDTP server. The command queues all 3 files listed above.

Excerpt of Agreement:

Atmosphere SIPS Science Team Software Delivery to LAADS

21 July 2020

This document outlines the content and parameters for Atmosphere SIPS delivery of Science Team software to the LAADS DAAC according to the EOSDIS data policy as stipulated under NASA contract NNG15HZ38C. The Atmosphere SIPS will provide data production software and documentation sufficient to explain the method of implementation of the algorithm and implementation of the software for each product collection. This will include delivery of science data product software documentation appropriate for post-mission data preservation as indicated in NASA Earth Science Data Preservation Content Specification (423-SPEC-001).

The Atmosphere SIPS will deliver a software package for each Science Team product version (collection) within three months after the product is publicly released by LAADS. The contents of the software delivery to LAADS will utilize the Atmosphere SIPS science code delivery system that was implemented to provide a consistent traceable method for science team code delivery and long-term record keeping (Table 1). The SIPS will deliver two tarballs and a summary PDF file. The “source code” tarball will contain source code, driver scripts, lookup tables, ancillary data information, a README file, version information, etc. The README file will also reference the A-SIPS system architecture for compilation. The “test data” tarball will include inputs and outputs needed to test and verify that the package is running correctly. The method of delivery for the tarballs will be secure HTTP download. When LAADS acknowledges that the tarballs have been downloaded successfully the delivery shall be considered complete. If LAADS decides to build the delivered software, the Atmosphere SIPS can provide only limited support under the terms of the Atmosphere SIPS contract.