Latest revision  17 July 2000

  TJD 9026 = 8 February 1993

 Bad DSELB and NSCALE in STTE data, Trigger Number 2175

The DSELB value (triggered detectors) and the NSCALE value (related to TTS)
in the auxiliary data in the STTE file of trigger number 2175 but which
really contains the data for trigger number 2174 because of overwriting
(both triggers occurred in the same gap) is different from the values in
the other burst-type files of trigger number 2175 which presumably have
the correct value.  The reason is not understood.

Some of the times in the STTE file of number 2175 are
  start time = SCTIME(3,2,1) = (4684,A42E,F468)
             = TJD/SoD = 9026/42030.9776
   load time = SCTIME(3,2,1) = (4684,A42F,0089)
             = TJD/SoD = 9026/42031.0021
   aux. time in first STTE packet  (obviously from earlier trigger)
             = SCTIME(3,2,1) = (4684,A1BB,EA95)
             = TJD/SoD = 9026/41403.9383

The incorrect DSELB value in the STTE file for trigger number 
2175 is "76543210" = "11111111" which becomes the hex value FF.
The correct DSELB value in the other files for trigger number 2175
is "--543---" = "00111000" which becomes the hex value 38.

The incorrect NSCALE value in the STTE file for 
trigger number 2175 is 0.  The correct value is 2.

In the auxiliary data in the telemetry, DSELB and NSCALE are one-byte
words which occupy the two halves of the same two-byte word.

The DSELH1,2,3,4 values in all files are  3,4,5,6.

Trigger number 2175 was an electron event.
Trigger number 2174 was an unknown event.