fix(prs): fit time decay curve through subnet-reported multiplier#1359
Merged
Conversation
The repo config API only publishes emission shares, so repos that override scoring.time_decay hyperparameters drew the curve with global defaults while the Now marker used the subnet-reported multiplier, splicing a V-notch into the line. On mismatch, re-solve the sigmoid midpoint so the drawn curve passes through the reported point and clamp the grace period below the merge age. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
anderdc
approved these changes
Jul 13, 2026
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
2 participants
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.
Problem
On PRs in repos that override
scoring.time_decayhyperparameters, the time decay chart drew a V-notch: the curve was rendered from the global config params (sigmoid midpoint 10 days), while the Now marker used the subnet-reported multiplier, and the marker point was spliced into the line.Example: james-cuda/gittensor-tinyrouter #240 — subnet reports 0.71× at 0.9 days since merge, but the default curve says ~0.97× there.
The UI can't resolve the repo's real decay params because
/repos/{name}only publishesemissionShareandissueDiscoveryShare— noscoring.time_decay— so the per-repo override never reaches the chart.Fix
When the subnet-reported multiplier contradicts the resolved curve (beyond the existing 0.05 tolerance), re-solve the sigmoid midpoint so the drawn curve passes through the reported (days since merge, multiplier) point, and clamp the grace period below the merge age. The
50% @ midpointmark line follows the fitted midpoint, and the subline now reads "curve fitted to subnet-reported multiplier (repo overrides decay params)".Repos without overrides are unaffected: the fit only activates on mismatch, and if the API later publishes per-repo
scoring.time_decay, the resolved params win again with no fit needed.Before
After