,
,
,
,
some time profiles of NTBs discovered by the different SWTCs are shown.
In tab.
the main characteristics of the same NTBs
are reported. All these events have been also detected
by BATSE (the corresponding trigger numbers are reported, as well).
In order to better understand why these bursts did not trigger the
GRBM on-board logic, the values of the on-board threshold
parameters
In particular, NTB 960723 (fig.
),
whose BATSE direction is
11
off-axis with respect to unit 2, did not trigger the OBTCs,
because it had
(on-board
threshold) and
;
therefore, while it just triggered SWTC2, it matched no OBTC
in any unit.
The NTB 980421 (fig.
), just a little brighter
than the previous, did match the OBTC, but only in unit 1,
therefore, not enough to trigger the on-board logic;
however, it satisfied SWTC2 and SWTC3.
The case of NTB 960913 (fig.
) is an example
of a burst, that did not trigger
on board, only because it happened during the dead time due to
a previous event (caused by a high-energy particle), that already
started the HTR mode: actually, the burst occurred just
3
10
after the previous event; since the minimum dead
time is
7 min (tab.
), HTR counts could not
have been acquired; nevertheless, the on-board flag indicating the
occurrence of a new trigger was set to positive.
This bright NTB triggered all the SWTCs.
| GRB | SW Trg | BATSE | GRBM Peak( |
AC Peak( |
On-board | ||
| UT | trigger | (SW thr |
(SW thr |
thr ( |
( |
( |
|
| 960723 | 04:46:06 | 5551 | 6 (2) | 3 (2) | 8 | 350 | +4 |
| 960802 | 22:07:01 | 5559 | 7 (1) | 5 (1) | 8 | 283 | +12 |
| 980421 | 22:44:02 | 6698 | 8 (1) | 4 (1) | 4 | 238 | +47 |
| 960913 | 23:05:20 | 5604 | 9 (2) | 9 (2) | 8 | 23 | -23 |
| 12 (3) | 13 (3) | 8 |
![]() |
![]() |
![]() |