Add option to drop filtered modes #3055
Draft
+462
−27
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.
drop_modesboolean, ifTrue, just drop modes that don't make the filtering threshold. The caveat here is that the number of modes might depend on the frequency. The choice that was made was to do the dropping after the tracking, and then just do the intersection and keep the smallest number of modes that meet the filtering criterion at every frequency.fill_fraction_boxas a filtering key which then requires abounding_boxto be passed to thesort_spec. Also afill_fraction(box)method to the mode solver data, as well as a propertyfill_fraction_boxthat uses the box defined in the storedmode_spec.sort_spec.