-----------------------------------------------------
Starview & DADS (Allen Farris & Warren King) -
The operational DADS system is now available for OTFC and appears to be working OK.
Dads 7.8.3 is on schedule for testing on March 15 and delivery on March 30. It contains the following fixes for OTFC
DADS support for the two destination pipes: otfc and nonotfc needs to be supported by the time OTFC is released externally. The reason is that we need to maintain two separate otfc pipelines: a test and an operational system. Code is in place to do this, but is untested. Some enhancements are needed to the front-end of DADS. This capability will first be tested on the DADS test system.
Action Item: Allen and Joel will work this out for a future DADS release.
-----------------------------------------------------
OPUS (Mike Swam) - The calibration pipeline is working on artichoke.
Mike is to develop the common rules system for OTFC. This will be in 2 to 3 weeks.
Action Item: Mike and Steve S. to develop a draft of procedures for operators. -----------------------------------------------------
getref/upref (Bernie Simon) - Some fixes have been made to change SKIPPED to PERFORM for WFPC2 and a change for WAVECALS. These fixes are not yet installed. Some additional software changes are needed to handle database changes in DADS 7.8.3. A new getref/upref will be installed for that release.
ACTION ITEM: Bernie will check with Phil Hodge about the meaning of SKIPPED for STIS.
ACTION ITEM: Bernie will investigate getref/upref for time-tagged data.
ACTION ITEM: Bernie will investigate keyword placement for switches.
-----------------------------------------------------
Change System (Lisa Gardner, Steve Lubow, & Bernie Shiao) -
Scripts are handling the updating of the internal test system on ZEPPO to emulate the automated change system.
The automatic change system needs further development.
Action Item: Lisa is to develop support for the pending datasets table.
Melissa said that the last_catalog_date and last_software_date can be initialized for STIS to some recent past date.
ACTION ITEM: Lisa will set these dates for STIS as part of DADS 7.8.3.
Sylvia has provided an algorithm for determining the last_catalog_date and last_software_date for WFPC2. Steve L. has a script that determines the database updates that are required for the last_catalog_date. ACTION ITEM: Lisa will set these dates in DADS release 7.8.3.
-----------------------------------------------------
STIS (Bernie Shiao, Ed Hopkins, Melissa McGrath) - Ed and Bernie Shiao are working on the list of proposed modifications to the headers (via the otfc_keyword_repair table). The keyword repair entries are done.
Action Item: These changes need to be reviewed by the STIS team
Action Item: Bernie Shiao will investigate the level of effort required to retrieve the 2700 or so WAVECAL datasets. Lisa will determine the effort required to make the database changes and the ingest process changes for WAVCALs. Since there is no short-term need to change these values, this effort is of low priority.
-----------------------------------------------------
Testing (Melissa McGrath, Steve Lubow, Steve Slowinski) - This system now appears to work correctly. Little testing was done last week.
Action Item: Steve Slowinski will carry out stress tests, including the case of requesting corrupted data.
Action Item: Mike Swam will investigate the cause of the FTP problems and try to develop an automatic recovery mechanism.
Action Item: Steve will work with the WFPC2 team to determine that the data are correct, based on their set of regression data. We need to have a standard set of results to compare against in an automated manner.
Sylvia and Faith will test the consistency of newly calibrated data between the initial pipeline and OTFC. Faith is out for weeks.
Melissa is identifying a set of STIS data for a regression test (about 50 - 100 datasets.) This is about 3/4 done. It will be completed in the next one or two weeks.
Ed is working on a tool to detect differences between the initial pipeline and OTFC data.
-----------------------------------------------------
Operational Support
We discussed some possible procedures for operators to follow. These need to be written down for review (see above Action Item for OPUS).