In the bottom diagram we see that the black moves are swinging between Rd8 and Rde8 start from move 95 th. And swinging between Qe7 and Qd7 start from move 125 th.
Curious if the engine could propose a draw.
In the bottom diagram we see that the black moves are swinging between Rd8 and Rde8 start from move 95 th. And swinging between Qe7 and Qd7 start from move 125 th.
Curious if the engine could propose a draw.
I watched Nakamura force Stockfish (It might have been Komodo?) into a draw in a live chess.com match in a very similar fashion a few years ago. It was a "locked position" that Naka forced the engine to toggle between shuffle moves. It was funny actually. The best part about it is that Naka was commenting on his own position and explaining that this was indeed what was happening.
It was the cracked version of stock fish. Somebody please tell them before it's too late. Computers never resign. Not literally, and not figuratively.
If you're wondering why someone would crack stock fish, it was because of the overwhelming requests to have a computer resign in lost positions, especially with blitz games.
I watched Nakamura force Stockfish (It might have been Komodo?) into a draw in a live chess.com match in a very similar fashion a few years ago. It was a "locked position" that Naka forced the engine to toggle between shuffle moves. It was funny actually. The best part about it is that Naka was commenting on his own position and explaining that this was indeed what was happening.
Yeah I think I remember that actually. Tricking the engine into a blockaded position is one of the only ways humans have a chance against them.
I watched Nakamura force Stockfish (It might have been Komodo?) into a draw in a live chess.com match in a very similar fashion a few years ago. It was a "locked position" that Naka forced the engine to toggle between shuffle moves. It was funny actually. The best part about it is that Naka was commenting on his own position and explaining that this was indeed what was happening.
I remember as far back as Deep Blue times that engines have had trouble with blockades. I wonder why that is.
I believe it's due to the "Horizon Effect".
https://en.wikipedia.org/wiki/Horizon_effect
I watched Nakamura force Stockfish (It might have been Komodo?) into a draw in a live chess.com match in a very similar fashion a few years ago. It was a "locked position" that Naka forced the engine to toggle between shuffle moves. It was funny actually. The best part about it is that Naka was commenting on his own position and explaining that this was indeed what was happening.
I remember as far back as Deep Blue times that engines have had trouble with blockades. I wonder why that is.
I believe it's due to the "Horizon Effect".
Yeah. The horizon effect would make chess as if chess is an infinite board game.
We should thank for it if that is true.
I watched Nakamura force Stockfish (It might have been Komodo?) into a draw in a live chess.com match in a very similar fashion a few years ago. It was a "locked position" that Naka forced the engine to toggle between shuffle moves. It was funny actually. The best part about it is that Naka was commenting on his own position and explaining that this was indeed what was happening.
I remember as far back as Deep Blue times that engines have had trouble with blockades. I wonder why that is.
I believe it's due to the "Horizon Effect".
I had heard about that in the past now that you mention it, though to me it doesn't explain why engines have problems with blockade positions in particular. Anyway, after reading that wikipedia article, there seems to be a possible solution to most problems of this nature:
"Rewriting the evaluation function for leaf nodes and/or analyzing more nodes will solve many horizon effect problems."
Yeah to be honest I don't completely understand it myself. Maybe someone else can explain it in more detail.
I think the problem here with the OP's post is a misunderstanding of the computer's evaluation. When I plug it into Stockfish 10 on my Ryzen 7 2700X, it doesn't have anything to do with the computer 'thinking it is winning', but rather a positional/material score count (which by the way on my Ryzen 7 2700X scores it as +1.59 on zero contempt and stays that way). In this case, it scores the space advantage to white. You can tell the computer doesn't think anything more than that, because the evaluation sticks to the same score no matter how deep you let the ply go (within human limits).
Now consider if we refuse to play a6. At ply 40 with no contempt, SF10 evals the position at +0.36 and dropping due to black being able to open the queenside to activate his heavy pieces in order to equalize. So can you really blame the computer here? It KNOWS allowing black to open the queenside leads to an easily seen drop in eval to a draw. On the flip-side, the positional score never drops after playing a6 until such time as a 3-fold is inevitable.
Conclusion: Stockfish didn't miss anything. The game is a draw if a6 isn't played. The game is a MUCH longer draw if it is played. Therefore, it plays a6.
I think the problem here with the OP's post is a misunderstanding of the computer's evaluation. When I plug it into Stockfish 10 on my Ryzen 7 2700X, it doesn't have anything to do with the computer 'thinking it is winning', but rather a positional/material score count (which by the way on my Ryzen 7 2700X scores it as +1.59 on zero contempt and stays that way). In this case, it scores the space advantage to white. You can tell the computer doesn't think anything more than that, because the evaluation sticks to the same score no matter how deep you let the ply go (within human limits).
Now consider if we refuse to play a6. At ply 40 with no contempt, SF10 evals the position at +0.36 and dropping due to black being able to open the queenside to activate his heavy pieces in order to equalize. So can you really blame the computer here? It KNOWS allowing black to open the queenside leads to an easily seen drop in eval to a draw. On the flip-side, the positional score never drops after playing a6 until such time as a 3-fold is inevitable.
Conclusion: Stockfish didn't miss anything. The game is a draw if a6 isn't played. The game is a MUCH longer draw if it is played. Therefore, it plays a6.
If the computer sees that the position will be a draw with best play then it would evaluate the position as equal. Since it evaluates the position as +1.59 (according to your engine) it must assess that the position is a win for White. I've heard masters say that even a 1.4 evaluation advantage is supposed to be winning.
If the computer sees that the position will be a draw with best play then it would evaluate the position as equal. Since it evaluates the position as +1.59 (according to your engine) it must assess that the position is a win for White. I've heard masters say that even a 1.4 evaluation advantage is supposed to be winning.
Negative. That's not how computer eval scores work, ESPECIALLY when the eval gets stuck on the same score no matter how deep the ply goes. Only novices think the eval score = winning. You have to have experience with both human chess and engine chess to know the difference in a given position. Like I said before, the computer does not 'think it is winning' unless it spies a forced mating sequence. Everything else before that has to be interpreted correctly by the human.
And before you start arguing with me, consider that experienced ICCF players and centaur chess players know exactly what I'm talking about, AND they know I'm spot-on correct.
An engine like stockfish, as opposed to Leela or Alpha Zero, can't give this a zero because the things it scores when evaluating a position as advantageous persist throughout its search depth. Things like mobility, control of the center, piece activity, space and other things that *normally* provide lasting advantages (not saying all are at issue here). You seem to be positing that because the evaluation isn't changing as Stockfish goes deeper it should recognize this is a draw. And indeed, that is normally a pretty good marker of a drawn position. But is it always the case that a position is drawn if Stockfish's eval doesn't change as it goes from X to Y depth? How else would it spot a draw, absent the traditional methods like 3 fold repetition in its horizon, tablebases, etc. Its not Leela or Alpha Zero after all.
I admit that I don't really know how engines evaluate positions. I only know what I've heard from other people, which may not be accurate. I've never really looked into it on my own. You guys seem to know more about it than I do so I'll take your word for it.
I'm no expert. Like you guys, I've noticed that an unchanging score as the engine goes deeper usually means a drawn. I just don't know if that always means a draw. I assume this is not actually a reliable method, or Stockfish would use that in choosing moves, and chose the also favorable move that is not a draw, or not as clearly a draw. Someone that plays in "centaur" (machine assisted) tournaments could tell us better -- just saying if there was a reliable method for it to detect a drawn position, Stockfish would certainly use it since its in constant competition for the top spot. And being able to detect a draw through another method would be very useful. Although, I suppose, Stockfish could select the draw line if it the developers thought process was something like, "we have the #1 enginge, Stockfish is more likely to win if we select the top eval, even if it might be a theoretical draw."
@drmrboss
Interesting, thanks!