Validate probability and outcome domains - #341
Merged
Merged
Conversation
Contributor
|
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
1 participant
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.
Summary
[0, 1]before binary or time-dependent binning{0, 1}{0, 1, 2}*_timespathsR parity
The R package explicitly validates probability ranges and binary outcome codes before calculation. This brings the Python performance-data APIs in line with that contract and gives the time-dependent path an equivalent event-code check.
Audit classification
Input-validation / correctness issue: invalid values could reach NumPy/Polars binning or mapping internals and fail inconsistently or misleadingly.
No valid-input calculations, cutoff semantics, estimators, plotting behavior, or dependencies are changed.