Repository navigation
feat(ci): Let strength.yml take its sequential test in normalized elo - #26
Merged
Merged
Conversation
v0.6.0 gave summarise-match an sprt_model input, and the reusable workflows could not pass it until a release held it. strength.yml now takes sprt_model and hands it through batch.yml to the summary, so a caller of the workflow can state its bounds in normalized elo. The model is checked before anything is built: it is logistic or normalized, and normalized bounds lie within 100 either side of nought. The summary refuses both too, but only after the batch has been played. batch.yml's manifest recorded model=logistic whatever the test was, and now records the model the summary used. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018ccJFsmZ4jAKYmFNgNBh9u
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.
What changed
v0.6.0 gave
actions/summarise-matchansprt_modelinput. The reusable workflows pin their actions at a release, so they could not pass it until a release held it. Now one does.strength.ymltakessprt_model,logisticby default, and hands it to each stage of the batch ladder.batch.ymltakes it and passes it tosummarise-match.strength.ymlchecks that the model islogisticornormalizedand that normalized bounds lie within 100 either side of nought. The summary refuses both as well, but only after the batch has been played.batch.yml's manifest recordedmodel=logisticwhatever the test was. It now records the model the summary used..github/workflows/README.mdsay thatstrength.ymltakes the model, and that a test carried on in a second run should be given the same one. Nothing checks that.calibrate.ymlruns no sequential test and is unchanged.How it was checked
v0.6.0tag and pass, sosummarise-matchat that tag does declaresprt_model.logistic 0 10,normalized 0 5,normalized -3 100andlogistic 0 500, and refusednormalized 0 150and a misspellednormalised.🤖 Generated with Claude Code
https://claude.ai/code/session_018ccJFsmZ4jAKYmFNgNBh9u
Generated by Claude Code