Add require_any keyword argument to source selection #400
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.
Complementing the earlier support to match data during a selection, this PR adds a
require_any
keyword argument as a weaker version ofrequire_all
. Rather than requiring all source to have data for each train, it only requires one source to have data for each train. The use cases for this are definitely smaller, but it seemed trivial to add to the existingrequire_all
code by tweaking the logic only slightly.Also used the opportunity to fix an oversight from #367 with
require_all
not actually being forwarded fromrun.alias.select()
torun.select()
.An open question is whether this should be ported to
run.trains()
as well.