The strange moves (start with 234th move) could be caused a deep search together with the misrecognition of the seki (described in previous post).
With one-shot testing, Zen always chose H14 instead of R18 (actual 234th move), which looks normal. (Time setting was 2 min for a move.) An important difference from actual game is the search tree, which is very big in real, long-time setting game. One possible interpretation is, Zen read in deep and found the (wrong) seki, which would lead W a sure win and so, played R18 toward this (again wrong!) winning position. Hideki Hideki Kato: <58d26196.6952%[email protected]>: >We have set komi to 5.5 today. This looks worked fine. > >The strange yose moves were caused by unknown reason. We are >seeking the cause(s). Observed fact: The upper left center >three black stones cannot be captured but Zen looks evaluated >them as dead. When Zen noticed the truth, horizen effect forced >several miserable moves in upper side white territory. Then, >upper left white stones together with many short-liberty stones >forced the value network misrecognized them as >living by seki, because the shape looked seki (for VN) and many >moves were required to capture them in rollout. > >Hideki > >Pawe Morawiecki: ><caksbshogyyn8wk2htv0xczavggem4jj-vpsz_fmqqczq7l8...@mail.gmail.com>: >>> >>> >>> RATHER OFTEN the outcome was a score where both sides thought >>> to have won. In the 5.5/7.5 komi example from Go this means that >>> outcomes with +6 or +7 points for Black on the board would occur >>> often. >>> >>> >>It looks like this issue is serious again was a factor in today's game >>against Park 9p. Zen was winning and in the endgame starts giving away >>points and the game was reversed. >>Hideki, was that the case? >> >>Too bad it's 6.5 komi as it seems Zen has potential to win both games :-( >> >>Regards, >>Pawel >> >> >> >> >>> Of course, this is not welcome for zero-sum games. But it is a hint >>> that in reallife scenarios (with non-zero-sum payoffs) Monte Carlo >>> heuristics (with their tendency to produce narrow wi0ns) might be >>> helpful in finding good compromises. >>> >>> Ingo. >>> _______________________________________________ >>> Computer-go mailing list >>> [email protected] >>> http://computer-go.org/mailman/listinfo/computer-go >>---- inline file >>_______________________________________________ >>Computer-go mailing list >>[email protected] >>http://computer-go.org/mailman/listinfo/computer-go >-- >Hideki Kato <mailto:[email protected]> >_______________________________________________ >Computer-go mailing list >[email protected] >http://computer-go.org/mailman/listinfo/computer-go -- Hideki Kato <mailto:[email protected]> _______________________________________________ Computer-go mailing list [email protected] http://computer-go.org/mailman/listinfo/computer-go
