-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another criterion of settledness #215
Comments
Yes it is very early testing, your idea is interesting, but it doesn't seem like a very 'strong' criterion since if the only effect is on the last stone played, the difference will be quite small. https://online-go.com/player/768720/katrain-balanced has some experiments with 'berserker' mode and it is scary. |
thx! Expecting a berserker or a chaos lover, I built katago b9ce89c3 in the master branch, modified katrain/core/constants.py in 2bf1846 as
and tried ai:settle on settled_weight=-5, opponent_fac=1, attachment_penalty=0, tenuki_penalty=0 with max_points_lost=5, min_visits=3, wide_root_noise=0.1. But AI's moves seemed quite regular. I may need to increase max_time as my machine is slow. |
Note that you don't need to edit constants.py to go outside the range, the text box accepts pretty much anything. Low visits could be an issue, yes. |
This is what happens for me on those settings: https://gokibitz.com/kifu/ByB0QAWwD |
Deprecated due to lack of feedback |
I post this comment since I noticed the new AI strategy "Simple Style" in v1.5.1 branch.
As an indicator of the board atmosphere in lizgoban, I have been using
U = \sum (1 - abs(ownership(i,j)))
over all coordinates (i,j) of "existing stones" on the board. The red dots in the screenshot indicate progress of U through a game. In my impression, this U well matches my feeling of unsettledness.How about using this criterion instead of the current definition of settledness in "Simple Style"? I am also interested in a berserker style that tries to maximize U.
The text was updated successfully, but these errors were encountered: