Applications¶
Likelihood Ratio Tests¶
If we believe reasonable pipelines can phrase their predictions in terms of a likelihood ratio test, then we expect them to currently compute
which is based on information from
Formally, both the
There may be correlations between
With this in hand, we can write
and obtain a multiplicative factor to the current likelihood ratio.
If this factorization holds, we simply have to measure
Within canonical machine learning contexts, this could be thought of as a regression problem, in which we attempt to estimate
We note that this approach will likely work well for short-duration signals with timescales comparable to typical glitches. If there are searches with longer timescales than typical glitches, in which only part of the data may be polluted by glitches, more complex approaches may be needed.
Filtering¶
If we assume the time-domain can be broken into a set of consecutive independent trials, or noise realizations, we can apply the likelihood ratio test on each segment separately. Therefore, the overall glitch likelihood for the entire duration of the signal would just be a product of the likelihoods over each segment separately. This would answer the question, “was there a glitch at any time during the signal’s duration?” and ignores when that glitch occured, which is differen than, “did a glitch cause the apparent signal?”
A possible way to include when the glitch occured is to define modified matched filters and/or detection statistics.
Some possibilities assuming an optimal filter in Gaussian noise
Searches could then define a likelihood ratio incorporating all these detection statistics instead of just
Similarly, one could define integrals of the amount of time within the signal’s duration associated with glitchy and clean times.
Again, it is not know whether these heuristics are actually useful.