Page 1 of 2
Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 2:16 am
by Quicksort
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 2:22 am
by zullil
[D] 1K1n2q1/1p4pR/1prPPpPn/1RB1p1rP/8/1B2p3/2p2b2/1k2N3 w - - 0 1
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 2:27 am
by Quicksort
OK, Louis. I should have posted the position. Too happy...Robert rules.
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 3:07 am
by tmokonen
Many different versions of Fruit and Toga also crash and burn when given this position.
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 3:13 am
by Quicksort
Too bad... Booh !
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 5:14 am
by Dirt
zullil wrote:[D] 1K1n2q1/1p4pR/1prPPpPn/1RB1p1rP/8/1B2p3/2p2b2/1k2N3 w - - 0 1
I had to follow Houdini's line for 31 plies, until the knight on h6 was taken and the king moved to e1, before Stockfish 2.0 saw an advantage for white. Crazy position.
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 5:32 am
by Albert Silver
Doesn't crash here. Just says mate in 75 after 36 seconds.
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Ba3+ Kd2[] 5.Bb4+[] Kc1[] 6.Ba3+ Kd2[] 7.Bb4+[] Kc1[] 8.Ba3+ Kd2[] 9.Bb4+[] Kc1[] 10.Ba3+ Kd2[] 11.Bb4+[] Kc1[] 12.Ba3+ Kd2[] 13.Bb4+[] Kc1[] 14.Ba3+ Kd2[] 15.Bb4+[] Kc1[] 16.Ba3+
+- (12.67 ++) Depth: 13 00:00:10 1602kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+ exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (14.74) Depth: 13 00:00:31 4732kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+ exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 14 00:00:36 5465kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+[] exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 15 00:00:42 6047kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+[] exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 16 00:00:52 8024kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+[] exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 17 00:01:10 12731kN
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 8:06 am
by Mincho Georgiev
Awesome position, Louis, thanks for sharing it!
This one can show (as in my case) how improperly handled triple repetition detection can mix up the 'go-further' search for a particular position.
I have to reconsider it in my implementation helping myself with positions like this one. I think that a lot of engines will suffer too with it.
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 1:24 pm
by Paloma
4.1 beta ?
Re: Houdini finds mate where R4 crashes and SF sees a draw.
Posted: Sat Feb 12, 2011 1:28 pm
by Damir
Albert Silver wrote:
Doesn't crash here. Just says mate in 75 after 36 seconds.
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Ba3+ Kd2[] 5.Bb4+[] Kc1[] 6.Ba3+ Kd2[] 7.Bb4+[] Kc1[] 8.Ba3+ Kd2[] 9.Bb4+[] Kc1[] 10.Ba3+ Kd2[] 11.Bb4+[] Kc1[] 12.Ba3+ Kd2[] 13.Bb4+[] Kc1[] 14.Ba3+ Kd2[] 15.Bb4+[] Kc1[] 16.Ba3+
+- (12.67 ++) Depth: 13 00:00:10 1602kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+ exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (14.74) Depth: 13 00:00:31 4732kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+ exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 14 00:00:36 5465kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+[] exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 15 00:00:42 6047kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+[] exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 16 00:00:52 8024kN
1.Bc4+ Kc1[] 2.Ba3+[] Kd2[] 3.Bb4+[] Kc1[] 4.Nd3+[] Kd1[] 5.Nxf2+[] exf2[] 6.Rd5+[] Kc1[] 7.Ba3+[] Kb1[] 8.Rb5+[] Ka1[] 9.Bb2+[] Kb1[] 10.Bd4+[] Kc1[] 11.Be3+[] Kd1 12.Rd5+[] Ke1 13.Bd2+[] Kd1 14.Bxg5+[] Ke1 15.Bd2+[] Kd1 16.Bb4+[]
+- (#75) Depth: 17 00:01:10 12731kN
Does not crash ?? Why don't you show the name of the engine that has
been used ? It might as well be any.
Hmm let's see some people here posted a position where Rybka crashes.
And all you did was post analysis which shows no engine name...