< Earlier Kibitzing · PAGE 240 OF 240 ·
|Oct-09-12|| ||AylerKupp: <jepflast> You and the rest of your ragtag brand of amateurs (you forgot "and unpaid") should not feel too badly about somehow missing 25...0-0-0. After all, you got the first part of the move right, 25...Rd8. You just forgot the second part of the move which I will describe as 25...Kc8. This is more easily visualized if you write the move as "25...Rd8/Kc8". :-)|
|Oct-09-12|| ||AylerKupp: <<jepflast> Still, I wonder why Rd8 never gained a following. AK's requests for more analysis seem to have been ignored.>|
By this point in the game (or probably much earlier), most of the team, with the notable exception of <RandomVisitor> who humored me often, had correctly decided that any of my requests for further analysis should be ignored as just a source of distraction. And, of course, any move that I suggest should be rightly viewed with skepticism.
I guess the moral of the story is that if you have sufficient computing power, you can afford to do some foolish and time consuming things . . . :-)
My reason for preferring 25...Rd8 over 25...0-0-0 (although I finally did vote for 25...0-0-0) was simple; we already had our knight pinned against our queen and I had hoped to avoid double-pinning it against both our queen and our king. This would make it harder to unpin it and have it return to e3 where it could once more squeal with glee.
With respect to the 25...c5 26.Nh2 question we had 71 analyses with 25...c5 26.Nh2 with an average eval of [+0.30] when both all analyses or only those analyses for PV=1 were considered, mostly as a result of <YouRang>'s efforts.
In contrast, we had 273 analyses with 25...c6 26.bxc6 from several analysts' efforts with an average eval of [+0.41] if all analyses were considered and an average eval of [+0.43] if only analyses for PV=1 were considered. So we (at least I) were pretty confident that if we played 25...c5 that your response would have been 26.bxc6, even if this would eventually also peter out to a draw.
|Oct-12-12|| ||jepflast: My narrative is in the middle of a little break here because <jepflast jr.> was just born a couple of days ago! I'll finish the annotation soon though!|
|Oct-12-12|| ||whiteshark: Congrats <jepflast>, strictly speaking <jepflast sr.> now. :))|
|Oct-14-12|| ||chesstoplay: < jepflast > Re: <<< h5 >>>|
I finally found the post I was looking for:
PinnedPiece: Just curious...how bad a move is h5? Does that put black's hackles up? or easily defended?
click for larger view
Seems to me it causes black some serious decision -making. ....Rh8 is not much of an answer, I don't think. ...Qb7 seems to be ignoring our intent. >
Does this tie into your lack of h5 posts?
|Oct-15-12|| ||jepflast: <chesstoplay> That comment by PinnedPiece was about move 35, not move 26, so we're not quite there yet....|
|Oct-15-12|| ||parmetd: Congrats!|
|Oct-15-12|| ||OhioChessFan: <AK: Although if you have been lurking on The World vs. Akobian game in progress I both think and hope that you do indeed stand corrected.>|
Can't argue that.
|Oct-16-12|| ||benjinathan: <jepflast> great news- congratualtions dad.|
|Oct-16-12|| ||AylerKupp: <jepflast> How soon before you start teaching him chess moves?|
|Oct-16-12|| ||rapidcitychess: <jepflast>
Wonderful news! Perhaps you can make him start regulating the tree! That's what kids are for, making the work easier around the house. You just got to get past the first 3 years or so.
|Oct-18-12|| ||jepflast: Thanks, all!|
|Oct-18-12|| ||jepflast: <Part 13: Move 26-29>|
After the train wreck, I did a good job publicly of not freaking out, and privately of not throwing my man-cave appliances into one another. So the rebuilding process began with my computers still intact.
<26…h5 27. xg4 hxg4 28. g2> There was no other way for White to untie the position. 27. Kg2 would have transposed at best.
Black had a laundry list of computer options here, but they were all pointless or led to Qxe5 anyway, so it wasn’t long before we were planning exclusively for:
<28…xe5 29. hf1> At long last! Black regains the gambit pawn and White activates the last piece.
Here was another greatly annoying list of options for Black. To me, that will always be the scariest thing in these Challenges. The most obvious move was again best, though.
Probably the most interesting sideline here was 29…b6 (or even 28…b6, which transposed). I found that White would probably win with 30. Rxf7 & 31. Rd1, and it looks like Team Black knew this as well.
<29…e6> Opting to return the queen to the best square rather than invite trouble.
After that relatively tunnelistic series of recent moves, the game opened up here again somewhat, and this is where Team White had to find the win.
click for larger view
This position was long expected before it arrived, which gave us plenty of time to catch up to Black in analysis and find a win. During this stretch I gave the game everything I had, and it was clear that several others were working very hard too, at least <hms123>, <cro777>, and <isemeria>. I remember this time very well; we struggled to find positions where White retained winning chances.
|Oct-18-12|| ||jepflast: (The above was written before the baby break but not posted because it wasn't long enough. Now, it seems like a good stopping point....)|
|Oct-18-12|| ||jepflast: <Part 14: Move 30>
It was a dark and stormy night….
Team White worked frantically, as mentioned, for this move that was White’s last, best shot to dictate the course of the game. Ranking Team White’s most dramatic votes, this was number one because of a last-minute switch from Rc2 to Rf4. If nothing else, it was encouraging that the lead analysts were able to pull the switch—influencing enough silent voters—on very short notice.
The obvious moves are, indeed, Rf4 and Rc2, but frustration kept driving us back to try weirder things. Qf5 and a4 were two of them, but they didn’t work.
In this position, both sides are limited to scant few productive moves, so I tried to use that to our advantage with the idea 30. Rf2. Black was ready to reposition the knight with b6 and Nb7, followed by Nc5 or Nd6, but if White could safely give away a tempo, Black would have had to choose the wrong one. I believe this idea worked for 31…b6—temporary elation, but after more analysis I saw that 31…c5 was a problem. I managed to produce an ending where White had a small but disappointing advantage; this was rejected because in other lines we had more such endings to choose from.
30. Rc2 was looking like our best shot for a while on the strength of (at least) these two endings, both starting 30…c5 31. Qf5 b6 32. Qxe6+ fxe6 33. Rf4 e5:
1) 34. Rxg4 Nb7 35. Rc1 Nd6 36. Rxg8 Rxg8 37. g4 Kd7
2) 34. Re4 Nb7 35. Rxe5 Nd6 36. a4
White is up a pawn in both, but in the time allotted we could not find wins.
Still, it was leading the vote against the most promising Rf4 line, discovered independently by me and <galumph>. That line was longer but also looked drawn until, once again, <karpkasp> swooped in and extended it to another win! We knew that the variations had not been checked very well, but, being good sports, we again chose to strike forth into the unknown. Besides, Rf4 just feels right, doesn’t it?
<30. f4 b6> Moves that cut to the chase in a big hurry.
Black had worthy contenders in Rde8 and c5, but they didn’t get the knight involved soon enough.
In the nick of time, Team White had established a new main line on which to ride to victory, but there would be one more surprise….
(Don’t look in the kibitzing to spoil it!)
|Oct-18-12|| ||jepflast: I should mention that in the case of 30...c5, we had not quite worked out a win either, after several promising attempts. The result of that line remains a mystery, but I think it's not a stretch to say Black had a good chance of drawing in that line too.|
|Oct-22-12|| ||jepflast: <Part 15: Moves 31-34>|
On move 31 there’s another batch of tempting options, but we had already shown them to fail. Qf5 quickly draws; a4 and Nf1 provided no way to maintain the advantage in the computer’s eyes.
31. Rc2 was the most interesting. After 31…Nb7, the computers like 32. Qf5 with a very good score, but here again was an ending we couldn’t solve after the queen trade. Our cleverest idea was instead 32. Rd2, where the computer favorite …Nd6 gives White new life. But the simple …Na5 invites a repetition or a return to the 32. Qf5 line. The only escape route was 33. Re4, which we examined thoroughly, but we found a difficult ending yet again after 33…Qxc4 34. Rxg4 Rxg4 35. Qf5+ Kb8 36. Nxg4 Qb3 37. Rd3 Qb2 38. Qf6 Qxe2+ 39. Nf2.
That left only one plan that seemed to keep the game alive.
<31. e4 d7 32. d1>
White’s move 32 options Re5 and e3 were quickly tossed out.
Here it seems Team Black always had their eyes on 32…c5, but 32…Nb7 was plausible too, or maybe we just hoped that it was; it certainly sucked up lots of our time. Black definitely made the right call, though. 32…Nb7 33. Qxd4 Nd6 34. Rxg4 Qe6 35. Rxg8 Rxg8 36. e4 Nxc4, then some choices, such as 37. a4 Kb8 38. Rf1 Nd6 39. Rf4 f5 40. e5 Ne4 41. Rxe4 fxe4 42. Qxe4 made for a too-interesting game from Black’s perspective. White had several earlier choices besides, and therefore we came to expect:
<32…c5 33. bxc6 xc6>
We looked at 33…Qxc6, just in case; White gets a sizeable advantage back in several lines. Even if it had been a good move, Team Black probably couldn’t have tolerated leaving the knight on the rim any longer.
Arriving at a landscape of uncertainty. A fitting place for the game’s last dramatic scene and the final chapter to this story, thank Zeus & Co.
|Oct-22-12|| ||jepflast: <Part 16: The End of Analysis>|
Rde8, Qe6, Rg7, Rg6, or Kb8, if we can limit it to five possibilities. The top move could be anything, depending on which engine you ask and at which search ply. Or which person.
The two Teams approached this move from completely different angles. Perhaps it was a matter of Rybka vs. Houdini; perhaps it was engines vs. intuitions or some other combination of factors. But somehow, Team Black had been mostly planning for Kb8 since the dawn of time, and the other moves only got attention as the day approached. Team White had been mostly planning for Rde8 and only started looked hard at alternatives when the move was staring us in the face.
Well. That’s not such a big deal, in retrospect. We didn’t have a forced win anymore in Rde8 or any other line anyway. After 34…Rde8, there was a pretty good line for White that at least would have extended the game to torturous lengths where we might have been able to eventually find a good ending: 35. Rd2 Rg6 36. Qf5 Rge6 37. Nxg4 Rxe2+ 38. Rxe2 Rxe2+ 39. Kf1 Re7 40. Qd3 Qe6, etc. 37. e3 may also have provided something.
34…Qe6 offers White several options and is too complex to address here. (It seems <Golden Executive> is the person to ask about this.) I for one thought it was as good as anything else.
The resilience of 34…Kb8 also became known to us reasonably beforehand, so by the time Black’s 34th rolled in, we knew to expect anything.
And yet, this was still something of a surprise. For one thing, I thought this gave White too many good options, too many ways to find a good continuation. Apparently, Team Black had had time to prepare for all of them… or had they? Okay, don’t panic.
Of course, it was well known before Kb8 showed up that 35. Qf5 leads to a simple draw. Sadly, the line I’m referring to is what actually happened in the game. The only branch worthy of search, in my opinion, was 37. Rc1, but we had already taken care of that too. I saw that Team Black was prancing about their “magical” 40…Nc2 in the kibitzing, but we hit upon this right away. Not that we needed to; most of us felt it was hopelessly equal after 39…Nxa3 and a string of apathetic et ceteras.
Well, no problem. I was planning a nifty line with 35. c5!
But alas!—and I guess this is at least in part what led to the ensuing chaos—I forgot to mention this to my teammates before we saw Kb8. Now, I don’t have to claim to be a good analyst for this point to take: if nothing else, I was on the ball (as were scarce few others at this point) and everybody knew it. In that situation, I have found (but who knows—this isn’t an exact science) that warning your team beforehand what to play in every case is a very good idea, especially if you back it up with a good line. Well, I didn’t do that. So before I could even say “c5 or Rd2”, Qf5 had piled up an alarming stack of votes, no doubt because it’s the engine move at any search depth one could achieve in a few hours without quantum computing. Once Kb8 was played, even after stating my case for c5, I wasn’t really affecting the vote the way I felt I should have. I thought, gee, I guess that goes to show the influence I have on my team. But, of course, in a two-day period, the latest improvements of all variations do not ripple through to all voters, as we all know.
|Oct-22-12|| ||jepflast: <Part 16 continued>|
I’ll get back to c5, but meanwhile, other analysis was taking place, rather diligently. Rd2 and e3, the third reasonable option, surfaced in short order. We also did some work on Kg1 and—as a last-second desperation—Qc2, but I’ll summarize them with “didn’t pan out” and get on to the main variations.
Team White’s most frantic search in the entire game was going on now. For me and most others, it was also the last.
35. Rd2 seems hopeful at first, or at least complicated, after 35…Qe6 36. Qh7 f6, long lines thence. However (duh!) 35…Ne5! forces the same dismal ending that happens after 35. Qf5, and that’s that. I remember that some Rd2 votes stubbornly remained after this was discovered.
35. e3 was reasonable, and not…quite…dead…after 35…Qb7 36. exd4 Ne5+ 37. Qe4 Qxe4+ 38. Rxe4 Nxc4 39. d5 Nxa3 40. Rxg4 a5 41. Rf4.
35. c5 has a story of its own—the game’s final subplot.
Before Kb8, I was thinking 35. c5 Ne5. At first, Black seems to be okay with 36. Qe4 Ng6 37. Rf5, etc., but the hard move to spot is 37. Rxg4!!, which doesn’t register in the engines. Long line, then White ends up one healthy pawn ahead and sitting pretty. Glory and ululation!
But there was still 35…Qd5+ 36. Qe4, etc. and the line looks fairly dead. I think this is as far as Team Black ever got, which increases the pseudo-drama of the story!
But there’s more. 35. c5 Qd5+ 36. Kf2! is the next improvement. 36…Qxc5 37. Nxg4 Rg6 38. Kf1 is best, and several options emerge for Black. 38…Qd6 is most prominent (most others don’t work), and I discovered after 39. h5 Rg5 40. Nf6 Qe6 41. g4 Re5, White is back with a vengeance. This is the line I was trying to sell the team on. Still playing for a win, I said.
Then, who should show up out of the blue but <karpkasp>, who swooped in once again to say that I had missed 38…f5, which is very drawish, but that he would vote for 35. c5 and hope we could find a way around the problem—he wouldn’t be back before the vote closed.
It didn’t take long for me to find that there was no way around it. We had a draw in all variations, all moves, everywhere. Our best chance—slim though it may be—was, and still is, officially 35. e3, but it was too late—most votes were Qf5 or c5, and the former was still leading, against all reason.
We all knew that Team Black would see the proper way to handle c5 in short order, if they hadn’t seen it already. I appealed to the team to vote for c5 for poetic reasons and offer a draw after 35…Qd5+ (and because we could probably retain the dignity of a pawn-up but unwinnable rook ending), since it was too late for e3. At the last minute, <isemeria> switched to c5, probably feeling sorry for me, to create a tie between the top two moves.
The winner of the meaningless coin-flip, and the end of the story.
I’m proud of what we were able to accomplish with our limited resources on Team White. We were ready to pounce on any number of Black mistakes, but with lots of hard work and a little bit of luck they always managed to find the right path.
No doubt the move of the game was 5…g6. I hope the professionals take note! OTB this would cause White serious headaches!
In the Biggest What-If department, I wonder if we could have defeated 5…Nge7. Our analysis was pointing towards yes.
So long, everyone. I'll see you in the next Team Challenge!
|Oct-22-12|| ||isemeria: Great report. And a great team player.
Thank you, <jepflast>.
|Oct-22-12|| ||hms123: <jepflast>
Thanks. That was an exciting report.
|Oct-22-12|| ||kutztown46: <jepflast> Awesome job. It would make a great magazine article.|
|Oct-26-12|| ||blue wave: <jepfast> Great story telling. Thanks!|
|Oct-26-12|| ||Check It Out: Very nice, <jepflast>.|
|Jul-22-14|| ||OhioChessFan: That was fantastic.|
< Earlier Kibitzing · PAGE 240 OF 240 ·