Repository navigation
feat(action): Give play-shard an optional clock for the candidate alone - #35
Merged
Merged
Conversation
A time odds match plays the same build on both sides with one given more of the clock, which prices the time rather than a change. play-shard had one time control and put it in -each, which reaches both engines. With candidate_time_control set, each side's tc goes on its own -engine line and none goes in -each, since a tc in -each takes precedence over an engine's own. That was the fault a hand-built time odds match once hit: both sides played the shorter clock and it read -3 for a clock later measured at +66. Unset, the fastchess command line is unchanged, and a test holds it to that. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013vnTSb5N6JEKfqkQHAgevq
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.
Adds
candidate_time_controlto play-shard, for a time odds match: the same build both sides, one given more of the clock.When it is set, each side's
tcgoes on its own-engineline and none goes in-each. Atcin-eachreaches both engines and takes precedence over theirs, which is how a hand-built time odds match once played both sides at the shorter clock. When it is unset, the fastchess command line is unchanged. A new test holds that.The reusable
strength.ymlhere does not expose the input yet. The engine calls the action directly, and that is the caller that needs it now.Tests:
pytest tests(476 passed),pre-commit run --all-filesclean.🤖 Generated with Claude Code
https://claude.ai/code/session_013vnTSb5N6JEKfqkQHAgevq
Generated by Claude Code