Skip to content

Reduce trigger control aggression

Timothy Davies requested to merge tdavies__reduce_trigger_control_aggression into spiir-O4-EW-development

Trigger control is too aggressive, and has been a barrier to !172 (merged).

This change removes the 0.5x far requirement, and reduce the window around the last upload from +- 100s to +- 5s.

Trigger control itself was shown to be reasonably inactive in MDC.

It has two main purposes, which it solves quite naively:

  1. Prevent gracedb spam for the same signal, which is already a non-issue due to clustering and limited overlap in template banks.
  2. Prevent spam due to glitches. This is a legitimate concern, but 0.5x far and 100s are extremely aggressive. By requiring far to be continually improving we should significantly limit uploads in the worst case scenario, without hurting our science case for multiple uploads on the same signal.

This change will be included in a branch off spiir-O4-review-v3 as a patch.

Merge request reports