I invite you to leave some comments about this exemplary game:
GridGinkgo vs The Baron, Stockholm (World Computer Chess Championship 2018).
GridGinkgo vs The Baron, Stockholm (World Computer Chess Championship 2018).
Computer making an exchange sacrifice?
A knight in the center that cannot be chased by pawns is no weaker than a rook.
The first 2/3 of the game was quite interesting. The Baron held up well against GridGinkgo.
Seems that The Baron's 45th move was the beginning of the end. It never seemed to recover after that.
I'm really surprised by The Baron's blunders. I wonder what the underlying cause for them were. I can understand an engine making moves that are inaccuracies, and even an occassional mistake, but an engine making blunders seems very strange indeed...
Perhaps it had to do with time pressure. I see The Baron was under 20 secs at that fateful 45th move while GridGinkgo had almost 55 secs left.
http://view.livechesscloud.com/7c104c94-c119-441e-a444-b0f22a1880d0
Seems that The Baron's 45th move was the beginning of the end. It never seemed to recover after that.
I'm really surprised by The Baron's blunders. I wonder what the underlying cause for them were. I can understand an engine making moves that are inaccuracies, and even an occassional mistake, but an engine making blunders seems very strange indeed...
Perhaps it had to do with time pressure. I see The Baron was under 20 secs at that fateful 45th move while GridGinkgo had almost 55 secs left.
http://view.livechesscloud.com/7c104c94-c119-441e-a444-b0f22a1880d0
@SGMMCOOL #2
Yes, computers have been sacrificing the exchange since Deep Blue's era.
Yes, computers have been sacrificing the exchange since Deep Blue's era.
@tpr #3
Good point. The other option was to protect the rook on c7 and to resist the pressure on the open file.
Good point. The other option was to protect the rook on c7 and to resist the pressure on the open file.
@FoxKing #4
It would seem like it's impossible for an engine to make an obvious blunder that an average human player would spot. But there are plenty of cases of bugs in programs. On the other hand, possibly, as you say, the blunder made by The Baron had to do with time pressure.
It would seem like it's impossible for an engine to make an obvious blunder that an average human player would spot. But there are plenty of cases of bugs in programs. On the other hand, possibly, as you say, the blunder made by The Baron had to do with time pressure.
nice
I wonder if Black's knight was forced to take the rook.
@Nick20 #9
Maybe yes because the pressure on the c-file has a very strong effect on opponent's piece coordination. In fact, GridGinkgo could increase it by placing the other rook on c1. Even after taking the c5-rook with a rook, White would have a passed pawn. In short, it is a difficult situation.
Maybe yes because the pressure on the c-file has a very strong effect on opponent's piece coordination. In fact, GridGinkgo could increase it by placing the other rook on c1. Even after taking the c5-rook with a rook, White would have a passed pawn. In short, it is a difficult situation.
This topic has been archived and can no longer be replied to.