Second EOSDIS Science Software Integration and Test Workshop

-- Steve Kempler (steven.kempler@gsfc.nasa.gov),ESDIS Project, Code 505, NASA Goddard Space Flight Center

On August 7-8, 1996, the Second EOSDIS Science
Software Integration and Test (SSIT) Workshop was hosted by NASA's Langley Research Center (LaRC) Distributed Active Archive Center (DAAC). The purpose of this workshop was to:

  1. Share lessons learned and experiences of DAAC and Instrument Team (IT) personnel that resulted from the integration and test of the Beta version of Science Software into the EOSDIS Core System (ECS).

  2. Understand the ECS implementation and plan for the SSIT of the Engineering Version (Version 1) of Science Software.

The workshop was attended by representatives from all the AM-1 platform ITs, SAGE III, the LaRC DAAC, GSFC DAAC, JPL DAAC, HAIS (ECS contractor), and GSFC's Mission To Planet Earth (MTPE, Code 170) and Earth Science Data and Information System (ESDIS, Code 505) Project. All teams contributed towards satisfying the purpose of the workshop.

For the AM-1 ITs, delivery of their Science Software to the DAACs is coupled with releases of the ECS (and, therefore, the bigger EOSDIS Ground System, which includes ECS, EOS Data and Operations System [EDOS], institutional facilities, etc.). SAGE III, SeaWinds, and other future ITs have similar associations of their Science Software with ECS deliveries. The science software deliveries for AM-1 instruments, and the associated ECS Releases are threefold: Beta Science Software and ECS IR-1 Release; Engineering (Version 1) Science Software and ECS Release A; and Operational (Version 2) Science Software and ECS Release B.

Generally, the content and purpose of each Science Software delivery are:

  1. Beta Version: To demonstrate the delivery, integration, and test procedures, as well as test the software environment and resource estimation. Science Software is mostly stand-alone (i.e., not an integrated production system).

  2. Engineering Version: To demonstrate the functionality of `not final' production science software and science software/ECS interfaces.

  3. Operational Version: To demonstrate the total production science software/ECS integrated system, ready for end-to-end prelaunch system testing and operational use.

It is expected that delta Science Software deliveries will be made after Operational Versions are delivered in order to fine-tune algorithms, include last-minute processing parameters, and execute final bug fixes.

After the experience and interactions encountered from the Beta SSIT, participants presented and discussed the following information:

A detailed list of these lessons learned was also provided in the form of a document entitled ECS IR-1 Lessons Learned (see e-mail address provided below to obtain a copy.).

The remainder (and bulk) of the workshop was devoted to the preparation for, and better understanding of, the Engineering Version SSIT requirements, IT needs, and community expectations at ECS Release A. The major accomplishment of this workshop was to provide information and discussion, ensuring that all questions and concerns were addressed in the following relevant areas:

The session on Engineering Version SSIT success criteria allowed an individual from each group to describe his/her team's success criteria for SSIT of that science software delivery (i.e., goals, measure of success, etc.). In the last session, a common format for the Data Set User's Guide was suggested. It was pointed out that this is needed for general data users and EOS Interdisciplinary Investigators. Examples of existing guides were mentioned such as the one at "http://seawifs.gsfc.nasa.gov." This topic raises the importance of producing a good set of documentation to go along with software deliveries.

Several Action Items were captured. For Workshop session summaries and action items, Workshop hand-outs, or a copy of the ECS IR-1 Lessons Learned docu-ment, please contact Steve Kempler (steven.kempler @gsfc.nasa.gov).