Normalize integer fixed time horizons - #292
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.
What changed
fixed_time_horizonsto floats at the sharedprepare_binned_classification_data_times()entry point[3, 6, 9]equivalent to[3.0, 6.0, 9.0]Why
Integer horizons could previously propagate as
i64while downstream time/AJ data usedf64, leaking an opaque Polars join-key datatype mismatch. The public API should treat integer and floating-point representations of the same time horizon identically.Scope
This PR only addresses horizon normalization in the shared time-dependent performance-data path. It does not change calibration heuristic behavior or defaults.