02-13-2021, 04:38 AM
(This post was last modified: 02-13-2021, 08:38 AM by dale walton.)
Hi. I regret that there is a mistake in the script for the options: option for leaving 3 spaces clear has the value 2 instead of 3. meaning that the default game is playing incorrectly.
Re the AI
Alpha-Beta found a proven loss at depth 14.
UCT made move after 4929 iterations (selected child visits = 4559, value = 0.9350734810265409).
Alpha-Beta found a proven loss at depth 11.
UCT made move after 7942 iterations (selected child visits = 2411, value = 0.9908751555371216).
This means the AI search was not exhaustive at 14, right? - so you are not doing strictly level first searches with regards to losses. Sorry, I didn't save the game.
But I did save this one:
Alpha-Beta completed search of depth 14.
UCT made move after 4034 iterations (selected child visits = 3133, value = 0.3258857325247367).
Alpha-Beta found a proven win at depth 13.
UCT made move after 3260 iterations (selected child visits = 2727, value = 0.014301430143014302).
Alpha-Beta found a proven win at depth 11.
UCT made move after 3171 iterations (selected child visits = 3061, value = 0.020581509310682783).
Alpha-Beta found a proven win at depth 11.
UCT made move after 3020 iterations (selected child visits = 2887, value = -0.025978524419812955).
Alpha-Beta completed search of depth 12.
UCT made move after 3975 iterations (selected child visits = 2799, value = -0.22186495176848875).
Alpha-Beta completed search of depth 14.
UCT made move after 990 iterations (selected child visits = 989, value = -0.25783619817997977).
Alpha-Beta completed search of depth 16.
UCT made move after 5482 iterations (selected child visits = 5397, value = -0.024272744117102094).
AB finds a "proven win" on move 53, but somehow it isn't....at move 57 AB still thinks it is winning, but there is a removal...
(This game was after I corrected the above option to 3 and recompiled)
------
If they are held over from previous turns, the removals that occur can be unrelated to which pieces moved in the turn, only to the fact that a piece moved in the turn.
I have now added the corrected script. (I also changed the default board to the next size bigger)
I've seen more cases: proven win 15, then 7, then back up to 15, and toward the end switching to even numbers... Just pop the board size up and run a few times and you should be able to see these.
But the point I wanted to add is that the turn register does not note the removals in its listing. You need the move full listing option to see them under moves, as well. is this related to the problem? Is the fact that removals can happen to pieces not related to the moved pieces a factor?
Re the AI
Alpha-Beta found a proven loss at depth 14.
UCT made move after 4929 iterations (selected child visits = 4559, value = 0.9350734810265409).
Alpha-Beta found a proven loss at depth 11.
UCT made move after 7942 iterations (selected child visits = 2411, value = 0.9908751555371216).
This means the AI search was not exhaustive at 14, right? - so you are not doing strictly level first searches with regards to losses. Sorry, I didn't save the game.
But I did save this one:
Alpha-Beta completed search of depth 14.
UCT made move after 4034 iterations (selected child visits = 3133, value = 0.3258857325247367).
Alpha-Beta found a proven win at depth 13.
UCT made move after 3260 iterations (selected child visits = 2727, value = 0.014301430143014302).
Alpha-Beta found a proven win at depth 11.
UCT made move after 3171 iterations (selected child visits = 3061, value = 0.020581509310682783).
Alpha-Beta found a proven win at depth 11.
UCT made move after 3020 iterations (selected child visits = 2887, value = -0.025978524419812955).
Alpha-Beta completed search of depth 12.
UCT made move after 3975 iterations (selected child visits = 2799, value = -0.22186495176848875).
Alpha-Beta completed search of depth 14.
UCT made move after 990 iterations (selected child visits = 989, value = -0.25783619817997977).
Alpha-Beta completed search of depth 16.
UCT made move after 5482 iterations (selected child visits = 5397, value = -0.024272744117102094).
AB finds a "proven win" on move 53, but somehow it isn't....at move 57 AB still thinks it is winning, but there is a removal...
(This game was after I corrected the above option to 3 and recompiled)
------
If they are held over from previous turns, the removals that occur can be unrelated to which pieces moved in the turn, only to the fact that a piece moved in the turn.
I have now added the corrected script. (I also changed the default board to the next size bigger)
I've seen more cases: proven win 15, then 7, then back up to 15, and toward the end switching to even numbers... Just pop the board size up and run a few times and you should be able to see these.
But the point I wanted to add is that the turn register does not note the removals in its listing. You need the move full listing option to see them under moves, as well. is this related to the problem? Is the fact that removals can happen to pieces not related to the moved pieces a factor?