Skip to content

Add features to lalapps_spec_avg_long for computing persistency

Evan Goetz requested to merge evan-goetz/lalsuite:more-persistency into master

Description

This merge request modifies lalapps_spec_avg_long so that the persistency calculation is calculated by averaging over "epochs" of data. The epoch can be a specified number of GPS seconds, 1 UTC day, 1 calendar week, or 1 calendar month. This enables weaker features to be observed because more SFTs are averaged together. This is a change from previous where the persistency calculation is made on a per-SFT basis, potentially missing weaker features.

In addition, a new "auto tracking" line tracker is added so that any frequency that has a persistency above a user-specified threshold will be added to the list of tracked frequencies. This makes it so that we don't have to know which frequencies are problematic a priori.

API Changes and Justification

Backwards Compatible Changes

  • This change introduces no API changes
  • This change adds new API calls

Backwards Incompatible Changes

  • This change modifies an existing API
  • This change removes an existing API

If any of the Backwards Incompatible check boxes are ticked please provide a justification why this change is necessary and why it needs to be done in a backwards incompatible way.

Review Status

This code is used for data quality and DetChar activities in the CW group. I suggest that @ansel-neunzert should have a look, and perhaps @karl-wette or @david-keitel

Merge request reports