Skip to content

test: allow one unit of published precision when re-deriving weights - #56

Merged
hobbyistz merged 1 commit into
mainfrom
test/live-weight-rounding-tolerance
Sep 22, 2026
Merged

hobbyistz merged 1 commit into
mainfrom
test/live-weight-rounding-tolerance

Conversation

@hobbyistz

@hobbyistz hobbyistz commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

The scheduled live gate re-derives each published seat weight from the published liveness score and attendance factor and required exact equality at six decimals. Those inputs are published rounded to nine decimals while the producer rounded its own unrounded result, so a re-derived weight can land a hair across a six-decimal boundary. Today's H100 07:15Z observation did exactly that for one seat: published 0.062529, re-derived 0.0625284999768938.

A scan of 6,992 published seat weights over the last two days across all four SKUs found that single disagreement, at 5e-7. The check now tolerates one unit of the published precision; a formula or input error is orders of magnitude larger and still fails it.

Validation: ruff passes; the test passes locally against the public front for all four SKUs, including the day with the boundary case.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

The live weight check re-derives each published weight from the published
scores and attendance factors and demanded exact equality at six decimals.
Those inputs are themselves published rounded to nine decimals, while the
producer rounded its own unrounded result, so a re-derived weight can land
a hair across a six-decimal boundary. Tolerate one unit of the published
precision; a formula or input error is orders of magnitude larger.

Signed-off-by: hobbyistz <293619914+hobbyistz@users.noreply.github.com>
@hobbyistz
hobbyistz merged commit 0530437 into main Sep 22, 2026
5 checks passed
@hobbyistz
hobbyistz deleted the test/live-weight-rounding-tolerance branch September 22, 2026 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant