Skip to content

clarify SFT timestamps convention in CW executables --help

David Keitel requested to merge david-keitel/lalsuite:lalapps-pulsar-startTime-clarifications into master

Description

Resolve #334 (closed) by amending the help strings of various CW executables to explicitly mention the half-open interval convention. I may not have caught every single executable, especially if they neither call XLALSFTdataFind() nor use a standard user var name, but this should be enough to close that issue. A good bunch such as HSGCT already have equivalently clear help strings, I didn't change those just for the sake of it.

The two extra commits resolve things I noticed along the way:

  1. synthesizeTransientStats referred to the wrong uservar names in some error messages
  2. spec_avg_long had Windows line breaks making for ugly diffs

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

for @karl-wette

Merge request reports