Up to this point each subsystem - DADS, OPUS/OTFC, CDBS, and the KET and DET databases- has performed its own unit testing. There has been a limited interface test of the entire end-to-end OTFC system. With DADS 7.80, OPUS/OTFC 1.0 and a new version of StarView, further end-to-end OTFC system testing will be possible. The goal of this meeting was to sketch out the steps required to get OTFC available for STScI internal testing.
Three software releases will provide the capability to run OTFC system tests - DADS 7.80, OPUS/OTFC 1.0, and a new version of StarView with an OTFC button. OPUS/OTFC and the new StarView will be installed on STOSC within the next few days. The individual OTFC tester will be able to change their STOSC StarView environment to use the new OTFC button. DADS 7.80 will be installed in operations to support OTFC testing.
Since the getref/upref utility is not yet built on Digital UNIX, we will use artichoke, a Sun SparcUltra 60 running Solaris, for the initial OTFC tests. Steve Slowinski and Herb Kennedy will perform this initial testing.
All OTFC testing will be performed with the operational version of DADS using a local version of StarView with an OTFC interface. Artichoke will be set up to poll the DADS request directories for OTFC requests. In addition, artichoke needs to set up an 'OTFC availability' file for DADS to recognize that the system is ready to accept calibration requests. All necessary calibration reference files for WFPC2 are already on artichoke's local disks.
Steve and Herb will configure the OPUS/OTFC pipeline after the release of OTFC 1.0. During the entire configuration and test process, Herb will be developing operation procedures for the operational installation and monitoring of the OTFC pipeline in DADS.
The current WFPC2 OTFC regression test consists of ~70 dataset that are known to successfully process. Some of these datasets test the OTFC ability to bypass calibration. Steve and Herb will generate additional error tests. These will include simulating a missing reference file, attempting to process a mission schedule (filename format of 9 characters beginning with U) through the OTFC pipeline, and more error conditions derived from Sid Parsons' list of WFPC2 problems observed in OPUS operations. They will also test the case of mixed instrument retrieval requests that include WFPC2, and will be sure that the OTFC reference files used agree with the off-line version of bestref.
Initially, the STOSC testing will use the dadsotfc database table on the zeppo server. Eventually, zeppo will become the OTFC operational database, and a test version of dadsotfc will be replicated to the robbie server.
It is estimated that these system tests will take about three weeks after the release of DADS 7.80. At this time, the system could be available for internal STScI testing.
After the Digital UNIX version of the OTFC pipeline is running, WHALER can be used for OTFC testing. Initially, we may be able to use the two-path capability in DADS to simultaneously perform OTFC tests on both artichoke and whaler. StarView can be configured to select either the Digital UNIX (whaler) or Solaris (artichoke) path.