Last revision October 5, 2000

TJD 9075 = March 29, 1993

The data crashed (garbage in BATSE packets) twice.

The first time that it happened was after
   TJD/sec = 9075/57503.362 (time of last good packet)


The problem was cleared before 
   TJD/sec = 9075/62797.442 (time of first good packet)


The second time that it happened was after
   TJD/sec = 9075/79431.298 (time of last good packet)

The problem was cleared before 
   TJD/sec = 9076/09796.226 (time of first good packet)


(The daily datasets were remade for both TJDs 9075 and 9076,
excluding both the times of the bad data but also the interval
between TJD/sec = 9075/62797.442 and 9075/79431.298.)


A trigger no. 2275 occurred at TJD/SoD = 9075/46314 which was during
a long reorientation gap.  The only burst-type file from that trigger
which survived was a partial STTE file.  When the flight software was
restarted (crash problem cleared), the wrong number was loaded onboard
for the last trigger number.  Thus, another trigger no. 2275 occurred
at TJD/SoD = 9076/37547 with a larger readout of burst-type files.
It was decided to ignore the first trigger no. 2275, i.e., to pretend
that it never happened because so little data were available.  This
is also discussed in another file.