TITLE:   GCN CIRCULAR
NUMBER:  7213
SUBJECT: Two non-burst Swift SubThreshold triggers
DATE:    08/01/24 16:08:03 GMT
FROM:    Scott Barthelmy at NASA/GSFC  <scott@lheamail.gsfc.nasa.gov>

S. D. Barthelmy (GSFC), D. N. Burrows (PSU), M. M. Chester (PSU),
P. A. Evans (U Leicester), C. Guidorzi (Univ Bicocca&INAF-OAB),
S. T. Holland (CRESST/USRA/GSFC), E. A. Hoversten (PSU),
J. A. Kennea (PSU), V. La Parola (INAF-IASFPA),
V. Mangano (INAF-IASFPA), D. Perez (U Leicester),
P. Romano (INAF-IASFPA), T. Sakamoto (NASA/UMBC),
B. Sbarufatti (INAF-IASFPA), P. Schady (MSSL-UCL),
M. Stamatikos (NASA/ORAU), R. L. C. Starling (U Leicester),
E. Troja (INAF-IASFPA), T. N. Ukwatta (GSFC/GWU),
D. E. Vanden Berk (PSU) and P. A. Ward (MSSL-UCL) report on behalf of
the Swift Team:

Swift-BAT triggered at 15:27:41.15 UT (trigger=301687). 
This is the first occurrance of the new (so called)
SubThreshold triggers within the the BAT flight ops system. 
This is NOT a real burst.  It is a noise trigger
that occurred while Swift was entering the SAA. 

Swift-BAT triggered a second time at 15:44:56.54 UT (trigger 301689). 
This is also not a real burst. 

Please note that some of the regular GCN Notices
were distributed to the world because of (a) an error
in the filtering code in the GCN, and (b) the second
SubThreshold trigger disrupts the filtering process
from the Notices that continue to come out from the first trigger.