Skip to content

Conversation

@KvanTTT
Copy link
Contributor

@KvanTTT KvanTTT commented Dec 13, 2025

No description provided.

KvanTTT and others added 30 commits December 13, 2025 19:55
…d macOS (OpenCL)

Also, it runs `runtests` and publishes build artifacts

fix lightvector#1124
It allows handling field sizes for accurately that are actual for Dots game
because its default size is not a square.
It makes them consistent to current rules (Go or Go Game) and
allows getting rid of unnecessary allocations
Introduce `whiteScoreIfGroundingAlive`, `isGroundingWinsGame`

Remove `getAreaNow` because it's unused
…ayMoveRecordedDots`

It works much faster than `playMoveRecordedDots` although it leads to some code duplication

Introduce some other minor Dots field optimizations
Fill app info (katago) during writing SGF
… game always can be finished by grounding

And it's unclear how to calculate the resulting score if the game is not finished by grounding,
but the winner is already known
…lculateCapturesAndBases`

Refine `Rules` constructor for Go and Dots
Because the hash depends on MAX_SIZE, and it's inconvenient on the experimental stage because the value might vary quite often
It significantly decreases game duration because typically it doesn't make sense to play until the very end in case of zero komi and when all dots are grounded.
Rename `numLegalMoves` to `numLegalMovesIfSuiAllowed`
because it's an expensive operation to calculate the number if sui is on
Commands for field setup (size, rules), handicap placement

fix #4

Dottify the engine:

* Use numbers instead of latin numbers in field output
* Player1, Player2 instead of Black and White
* Tidy up default for Dots game (39*32 default size)
However, it should be restored later when NN is unified with Go models (22 for spatial and 19 for global)
Fix `set_position` to recognize start position

Fix start pos recognizer

Remove `START_POS_CUSTOM` because now all unrecognized moves are accessible via passed `remainingMoves`
@KvanTTT KvanTTT closed this Dec 13, 2025
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