iDQ workflow code shouldn't look for ifos that aren't there #5077
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The all-sky workflow code is setup so that the
workflow-ifos
section of the config should be the only place that decides what ifos are active. If (for example) that section lists h1 and v1, then sections labelledl1
elsewhere in the config file should be ignored ... They should also not break anything (ie. havingl1
sections should be fine, they just won't be used). This then means that if I want to swap to a L1 V1 analysis I just turn L1 on and remove h1 fromworkflow-ifos
.At the moment the iDQ workflow code breaks this, by searching for section names (and not checking if they are actually being used). The fix is trivial, just do an "AND" operation, with
workflow-ifos
when iDQ figures out which ifos are present. This still allows the functionality that if there is not a "workflow-iDQ-v1" section, we will not try to do V1 iDQ things, even if V1 is active.