History

Checks in SKIM1 Processing at Vanderbilt

  Here is a description of the checks we are making at SKIM1:

1)  spooling from tape->disk

	o  check the tape/run correspondence against WHYME
	o  if tape/run doesn't match WHYME (hasn't happened yet)
	   then notify the appropriate authorities (FBI, CIA, and SKIM1
           crew), but continue if run hasn't been processed yet.
	o  check to be sure the run hasn't been processed before
	o  check number of events spooled to disk against FACTOIDS
           database.  If events doesn't match, check PASS1 completion
           flag.  If completion>1 or but SKIM1 events>pass1
           events==>o.k.  If number of events spooled to disk is less than
           PASS1 events...abort job.
	o  check for read errors in tape->disk logfile.  If they occur,
           notify the appropriate authorities, but use PASS1/SKIM1 events
           comparison for the real decision.

2)  disk->tape

        o  events analyzed by SKIM1 must match the events spooled to disk
	o  bytes written to tape must match bytes on disk for each file,
           if not (hasn't happened yet), then proper authorities are
           notified and they must take corrective action.
	o  skimmed events must match the number of events written to tape
           for each file.
        o  in the event of write errors, the data is to be relogged to 
           a different tape

Checks in SKIM1 Processing at Colorado

Last updated on 5/5/98

Send comments to: Harry Cheung