Document curve API constraints and troubleshooting - #289
Merged
Conversation
Contributor
|
uriahf
marked this pull request as ready for review
August 12, 2026 06:15
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.
What changed
fixed_time_horizonssupport introduced by Normalize integer fixed time horizons #292skills/rtichoke/SKILL.mdso Great Docs can publish package-specific agent guidance alongsidellms.txt/llms-full.txtWhy
Recent integration work exposed several places where similarly named rtichoke functions have different behavioral contracts. The docs should emphasize the conventions the curve families share and make the real remaining asymmetries discoverable without overstating differences.
After #291, matching-key Train/Test populations may have different sample sizes. After #292, integer and floating-point fixed time horizons are equivalent. After #293, unsupported calibration heuristics fail early with an actionable error. The main remaining API asymmetry documented here is that
create_calibration_curve_times()requires an explicitheuristics_setsargument and accepts a narrower set of heuristics than its sibling curve families.Great Docs integration
The new user-guide pages flow into
llms-full.txt; the curated skill captures high-value gotchas in a compact agent-oriented form; and the changelog is sourced from GitHub Releases rather than maintained as duplicate history.Scope
Documentation only. This PR does not change calibration defaults or statistical behavior.