Latest revision 14 March 2000 TJD 11616 = 13 March 2000 TTE, TTS, MER data, Trigger Number 8035 The data in the TTE, TTS, and MER files for trigger number 8035 at TJD/SoD = 11616/76384 seem to be corrupted. The reason is not understood but may be a hardware problem. This has happened before. Start Time = (5AC1,2A60,0E5B) = 11616/76384.0574 Load Time = (5AC1,2A60,1440) = 11616/76384.0810 The data in the TTS and MER files seem to be for the preceding event (no. 8034). The TTS and MER files for no. 8035 are less complete than those for no. 8034. The TTE data seem to change from the trigger detectors to another detector. The trigger detectors (DSELB) were 4 and 6. The first board of TTE (Packet ID 33hex, Packet Sequence Numbers 1-64), pre-load time, has all detectors as it should. The first two packets (Packet ID 33hex, Packet Sequence Numbers 65-66) and part of the third packet (Packet Sequence Number 67, first 17 words) of the second TTE board, post-load time, have detectors 4 and 6 as they should. However, part of the way through the third packet (Packet Sequence Number 67, beginning at the 18th word) and for almost all of the remainder of the TTE file (Packet ID 33hex, Packet Sequence Numbers 68-128; and Packet ID 34hex, Packet Sequence Numbers 1-128, except for the last word of Packet Sequence Number 128), only detector 5 appears. The very last TTE word (128th word of Packet ID 34hex, Packet Sequence Number 128) has detector 2, channel 4. Detector 5 is not one of the trigger detectors for number 8035 or even for the preceding event, number 8034, whose trigger detectors were 1 and 3.