![[Welcome to Sensei's Library!]](../../images/stone-hello.png)
StartingPoints
ReferenceSection
About
Referenced by SomeEndgameProblem1
|
Some Endgame Problem Solution 1
Difficulty: Expert
Keywords: EndGame, Life & Death
![[Diagram]](../../diagrams/36/864bf886541191906198d9e5902d5270.png) | the problem |
This is the position that was put forward in Some Endgame Problem 1.
![[Diagram]](../../diagrams/40/25b52412fe4ccd59fb84bc11e5b19a88.png) | The cut does not work |
The cut does not work in this case. Because her string is one stone longer, White can give atari at , and after Black has achieved nothing.
![[Diagram]](../../diagrams/49/983f12dc06f79544096b23d7b666936b.png) | TuRen?'s variation |
As TuRen? correctly stated, the above is wrong. Black can cut at , provided is answered at . If White answers at , Black plays at and gets a ko. If White answers at or , this variation occurs. Black captures two stones in sente, exactly the same result as in the 'correct' variation below. In fact, this variation is even better than the one below because White's corner is worth 4, rather than 5, points.
![[Diagram]](../../diagrams/42/2b7a9ea4eeb4ff8c5f211255e27cf6f0.png) | Not a vital point |
here also does not work. Again, Black does not get much for his trouble.
![[Diagram]](../../diagrams/3/dad169a0978273f55ff0467d156ea556.png) | Tesuji |
The cut at is tesuji. If White answers at , the moves to give Black a ko.
![[Diagram]](../../diagrams/9/120ba4c7a4052031265a635ad8af57ce.png) | Even worse |
If White connects after , she is unconditionally dead.
![[Diagram]](../../diagrams/16/fa29468bf5285aa2dca6401ab4494b64.png) | White connects |
If White connects at , she is dead too.
![[Diagram]](../../diagrams/49/4d83c00d5b5a95516eea52389551fe9f.png) | Atari |
And if White plays atari with , it is ko again (White a is a ko threat, forcing Black b).
![[Diagram]](../../diagrams/8/28a636376cdbe6793b9891c8176b8324.png) | White's best move. |
White's best move is . After this, White is unconditionally alive, but Black can capture two stones in sente with . ( is necessary because a black stone at the same point would kill the white group with a snapback).
![[Diagram]](../../diagrams/2/bb2904d4fba22f9e882ca0771385e4d7.png) | My blunder |
Unfortunately, in the game where this position occurred (it was in the last round of the preliminaries for the 2001 Dutch Championships, against Marcel Bloemena), I did find , and my opponent did find , but I missed the black move at in the previous diagram, and thus thought it would be gote. To avoid this result, I played the terrible move at , expected White a, Black b and White c (which would be 1 point better than the previous diagram), but of course my opponent answered at , after which I could not capture the two stones at all - not even in gote.
![[Diagram]](../../diagrams/45/c99c734c9d1796bf703aa90703e79dfe.png) | Not as good |
Instead of in the last two diagrams, the atari here is also possible, but it is not as good. As shown before, Black plays at , but White avoids the ko with . Now White has only 4, rather than 5, points.
![[Diagram]](../../diagrams/20/c2674a61520612f15655bd929b3a6d6e.png) | Reference diagram |
After , White will have to to play inside because Black threatens a double snap-back.
Charles I've added this diagram to make it clear that Black threatens an atari, leading rather to a combination of snapback and a connect-and-die.
![[Diagram]](../../diagrams/3/7f22da9c085c4749d8ec502d202ca545.png) | Furthermore... |
Furthermore, Black can decide to play on this side. Now White saves the two stones, but loses the other two. Furthermore, her territory has shrunk to 3 points only.
![[Diagram]](../../diagrams/50/b3c51da3e3739dec16532e8e97e51078.png) | Also incorrect |
For Black to play at , which might look like a vital point, directly, without playing either cut first, also does not work. White connects at , and Black can still capture the stones: but only in gote.
-- Andre Engels
This is a copy of the living page
"Some Endgame Problem Solution 1" at
Sensei's Library.
2003 the Authors, published under the OpenContent License V1.0.
|