Triggering mixup for GRBS 240805A and 240805B

[PaulHancock]

The following two GRB occurred on the same day but were not handled well by the TraceT app:

The first GRB (second row) occurred in a location where the XRT telescope couldn't be used (close to the sun or moon?) so the XRT position wasn't sent until about 12h after the event. When the new position was received TraceT thought it would be a good idea to trigger on the new position since it was more than 10deg from the original. However, the new position was a mistake (some human at the Swift ops centre maybe pasted the position from the "B" event to the "A" info feed). This shouldn't have been a problem, however there is an implicit assumption that the events we recieve are within seconds of the events occuring, so TraceT compared the event times and decided that the new info was within our 2h observing window, and sent the trigger. What should have happened is that TraceT looked at the current time and compared it to the initial event time and saw that it was outside the observing window and not sent any trigger.

Separate to the above, Gemma didn't receive all the correct emails for the two events.

Finally, it seems that the ATCA was actually triggered for both events under the ATCA_long_grb proposal, despite what is reported in the table.

These three things may be related to each other but more likely they all have the same root cause.

Investigation continues....