Add named SelectionPolicy definitions and exact numeric replay - #446
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Named selection settings previously had to be reconstructed by each consumer, and CSV/TSV parsing could change the binary float value at a filter boundary. Add a public
SelectionPolicymapping contract and exact float reload so a saved policy can reproduce candidate scores and selections.rank_with_policydelegates to the existing candidate ranker and records the definition, caller-supplied derivation provenance and separate execution/input facts. It adds no scientific defaults or predictor execution.This is the policy-definition foundation. Occurrence-level evaluation and named criterion audit records remain #444 and #445; the representative ranking wrapper does not replace those interfaces.
Validation:
./lint.shpassed; the full./test.shpassed with one worker (4,934 tests, zero skips/warnings, 94% coverage). The released Vaxrank compatibility job passed all 18 construction cases. All GitHub CI checks are green, including Python 3.10–3.12 and the isolated optional integrations. Released to PyPI as 5.89.0 after green master CI and the complete clean-master deploy gate. Both public artifact SHA-256 hashes match the local build; tagv5.89.0points to merge commit72c62b3eca7cc1fd0578dc5672763948987b42b9.Closes #441
Closes #442
Closes #443
Refs #366, #444, #445, #288