So is the endpoint evaluation in chess programs. This isn't a difference between Go and the other games. (In fact, pretty much nothing in your original post is)
So is the endpoint evaluation in chess programs. This isn't a difference between Go and the other games. (In fact, pretty much nothing in your original post is)
There are extensive wikipedia articles on what constitutes a winning endgame in chess, as the board simplifies towards the end of the game:
https://en.wikipedia.org/wiki/Endgame_tablebase says "All chess positions with up to 6 pieces have been solved"
So, I disagree. Even if you don't count this as a theoretical difference, it is a practical difference.
The exact same thing can be done in go, scoring a finished game is trivial. The strength of the program simply isn't determined much by correctly identifying and scoring terminal positions, but the intermediate ones. And for both chess and go, one very much uses heuristics which are often wrong.
If the heuristics were never wrong, you wouldn't have to do the tree search part at all.
Endgame databases only have a tiny effect on the strength of chess programs (a common misunderstanding!) just because it's not very common for the game to be still "flippable" by the time they become relevant. In all the other positions, you need the heuristics.
The situation for checkers on the other hand, is very different. There the endgame databases were critical for solving the game, but due to mandatory capturing rules the search space reduces much faster.
Edit: Not sure why HN won't let me reply. But anyway: the error that you're both making is assuming that the positions in which humans stop and score are "endgame" or "finished" positions. That's not at all the case! A game is finished if there are no more legal moves besides filling one's own eyes. Counting at that point is trivial because all the life & death situations are "resolved". Monte Carlo programs play until those positions, not the ones where a human would stop the game.
(if you now bring up seki, you get half a cookie)
AGA Rules: 9) Ending the Game: Two consecutive passes signal the end of the game.
New Zealand rules: The game is finished when both players agree that there are no more worthwhile moves.
Humans agreeing on a score and outcome has little to do with what a program has to do to calculate this score.
I still don't see your argument. Humans and humans are capable of agreeing on a score with those rulesets. Computers are also capable of following the ruleset and agreeing on the score. Computer vs. human games are not playing by a different ruleset. By that ruleset, the game is over when both sides pass.
I've also encountered this bug. Please bring it up with dang.
Click the [link] link to get a reply box quicker.