Skip to content

Allow Fscan programs to check for "nosfts" file

Evan Goetz requested to merge evan-goetz/lalsuite:use-nosfts into master

Description

This MR lets the Fscan programs check for the nosfts file if the SFT catalog length is zero length. If the file exists, then the program exits gracefully. If not present, then the program exits with an error.

It is preferable to merge !2232 (merged) first since that's the primary way the nosfts file gets created, though it could be manually created for some specific use cases.

API Changes and Justification

Backwards Compatible Changes

  • This change does not modify any class/function/struct/type definitions in a public C header file or any Python class/function definitions
  • This change adds new classes/functions/structs/types to a public C header file or Python module

Backwards Incompatible Changes

  • This change modifies an existing class/function/struct/type definition in a public C header file or Python module
  • This change removes an existing class/function/struct/type from a public C header file or Python module

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

@david-keitel or @karl-wette should have a look. CC @ansel-neunzert who may also want to comment

I have tested these changes work in an Fscan pipeline

Edited by Evan Goetz

Merge request reports