FCT1: Houdini 4 STD B x64 will be start in the evening!

Discussion of computer chess matches and engine tournaments.

Moderator: Ras

Frank Quisinsky
Posts: 7228
Joined: Wed Nov 18, 2009 7:16 pm
Location: Gutweiler, Germany
Full name: Frank Quisinsky

Re: FCT1: Houdini 4 STD B x64 will be start in the evening!

Post by Frank Quisinsky »

Hi Bram,

if I am looking in the middlegame / Transposition into endgame / endgame stats ... I create to many of such stats ... all is allways the same. We can see which engines are aggressive with many pieces on board, engines stronger in endgames, stronger in middlegames and so on.

I am not a fan of endgames.
But if an engines made the most of Points in very Long endgames ... really ... it's boring to follow the games if I am looking at home. I like more engines which try to search faster a way to win a game.

Rybka do nothing in the beginning of a game.
Houdini avoid draw with the results more very Long boring endgames.
Houdini have move average from 102 ... the next engine on place 2 in longest move average have 95.

Each Houdini game in average ... 7 moves more as the engine here with the second place.

Or ...
Stockfish = 81 moves ... Houdini = 102 moves ... Each Houdini games will run in average 21 moves longer ... and this boring ... really!

Sorry Bram ... but in each of the stats ... I can't see that Houdini is in tactic one of the TOP-10 engines (beginning of the game, or with many pieces on board).

I can't understand people have fun in looking Houdini and Rybka games ... so many other engines produced more interesting chess. Ok, Houdini produced a high rating ... but to look on a rating only is wrong. You see nothing as a stat result to 1:0, 0:1 and 1/2:1/2. You can't see all the great styles engines have.

But let us not discuss about such things. Perhaps it's wrong what I do there, to find out more about a style. Not all what I find out ... People like because the own World in opinion about engines is in danger.

I know that many people like boring endgame chess ... fans of Houdini and Rybka ... the commercials do here a good job. Fritz is also an engine ... draw king ... do nothing in try to win a game in the beginning if I am looking on game results vs. other TOP engines.

Replay Hakkapeliitta games ... and have fun.
Compare the good moves from Hakkapeliitta with Houdini analyzes and you know what I mean ... Hakkapeliitta is only one example.

Best
Frank

The complete database can be download.
If you like make your own stats ... more proofs I can't give.
If you build an other opinion about a style of an engine, fully OK for me. But I can't build an other opinion after I am looking in the stats with the games every one can download.
Frank Quisinsky
Posts: 7228
Joined: Wed Nov 18, 2009 7:16 pm
Location: Gutweiler, Germany
Full name: Frank Quisinsky

Re: FCT1: Houdini 4 STD B x64 will be start in the evening!

Post by Frank Quisinsky »

Fritz:
Means the latest Version from Frans Morsch.
With each new Fritz Version ... draw quote is higher ... move average is higher, Elo is higher ... but in the beginning of the game I can't see aggressive chess ... the enigne from Frans Morsch lost here face ... because older Fritz Versions are much more aggressive in the beginning of the games!

I am thinking that engine programmers should try that engines are more aggressive in the beginning of the game. In the latest years more in focus are endgame databases and improvements to transposition into endgames with the results that engines like Houdini are with lesser pieces on board around 300 Elo stronger as grandmasters.

Interesting is that grandmasters have an advantage in the beginning of the game vs. engines (engines are to passiv). And in engine development is this in my opinion the bad point in computer chess.

Improvements are to search with many pieces on board and Computer chess will be much more interesting for looking ... at the Moment more interesting for looking are gm games (beginning of the games).

But with engines like Alfil, Hakkapeliitta, Junior, Spark, Komodo, Stockfish, Cheng, EXchess so many others ... we are on the way.

Best
Frank
beram
Posts: 1187
Joined: Wed Jan 06, 2010 3:11 pm

Re: Komodo, Houdini stats, great Hakkapeliitta game!

Post by beram »

Vinvin wrote:
Frank Quisinsky wrote: Here an example:
What Hakkapeliitta made with Houdini ...

[pgn][Event "FCP, 40/10, p=off, i7-4770k-5930k, 4GHz"]
[Site "Trier"]
[Date "2015.07.26"]
[Round "25.16"]
[White "Hakkapeliitta 3.0 x64"]
[Black "Houdini 4 STD B x64"]
[Result "1-0"]
[ECO "B11"]
[PlyCount "93"]
[EventDate "2015.??.??"]
[EventType "rapid"]
[EventRounds "50"]
[EventCountry "GER"]
[Source "Frank Quisinsky"]
[SourceDate "2015.07.26"]

1. e4 {[%eval 0,0] [%emt 0:00:00]} c6 {[%eval 0,0] [%emt 0:00:00]} 2. Nc3 {
[%eval 0,0] [%emt 0:00:00]} d5 {[%eval 0,0] [%emt 0:00:00]} 3. Nf3 {[%eval 0,0]
[%emt 0:00:00]} Bg4 {[%eval 0,0] [%emt 0:00:00]} 4. d3 {[%eval 0,0] [%emt 0:00:
00]} e6 {[%eval 0,0] [%emt 0:00:00]} 5. Be2 {[%eval 0,0] [%emt 0:00:00]} Nd7 {
[%eval 0,0] [%emt 0:00:00]} 6. O-O {[%eval 0,0] [%emt 0:00:00]} Bd6 {[%eval 0,
0] [%emt 0:00:00]} 7. d4 {[%eval 0,0] [%emt 0:00:00]} Ne7 {[%eval 0,0] [%emt 0:
00:00]} 8. h3 {[%eval 0,0] [%emt 0:00:00]} Bh5 {[%eval 0,0] [%emt 0:00:00]} 9.
Bd3 {[%eval 0,0] [%emt 0:00:00]} h6 {[%eval 0,0] [%emt 0:00:00]} 10. Qe2 {
[%eval 0,0] [%emt 0:00:00]} O-O {[%eval 0,0] [%emt 0:00:00]} 11. Re1 {[%eval
16,24] [%emt 0:00:24]} Qb6 {[%eval -2,20] [%emt 0:00:31] (Te8)} 12. e5 {[%eval
27,22] [%emt 0:00:22] (Le3)} Bb4 {[%eval -20,20] [%emt 0:00:16] (Lc7)} 13. Rd1
{[%eval 11,23] [%emt 0:00:24]} Rac8 {[%eval -25,21] [%emt 0:00:23] (Lxc3)} 14.
Na4 {[%eval 12,26] [%emt 0:00:21] (Le3)} Qa5 {[%eval -32,20] [%emt 0:00:17]}
15. a3 {[%eval 14,27] [%emt 0:00:20] (b3)} Qxa4 {[%eval -50,19] [%emt 0:00:18]}
16. b3 {[%eval 12,28] [%emt 0:00:19] (Le3)} Qa5 {[%eval -58,21] [%emt 0:00:13]}
17. Bb2 {[%eval 0,28] [%emt 0:00:23]} Bc3 {[%eval -42,21] [%emt 0:00:17] (Lc5)}
18. b4 {[%eval -9,28] [%emt 0:00:17]} Bxb4 {[%eval -49,21] [%emt 0:00:11] (Dc7)
} 19. axb4 {[%eval 0,25] [%emt 0:00:17]} Qb6 {[%eval -50,20] [%emt 0:00:00]}
20. Bc3 {[%eval -15,24] [%emt 0:01:28] (De3)} a6 {[%eval -63,22] [%emt 0:00:16]
(f6)} 21. g4 {[%eval 7,24] [%emt 0:00:14] (Te1)} Bg6 {[%eval -85,21] [%emt 0:
00:07]} 22. h4 {[%eval -5,26] [%emt 0:00:14] (Ld2)} Bxd3 {[%eval -74,22] [%emt
0:00:32]} 23. Rxd3 {[%eval 0,26] [%emt 0:00:14]} Qc7 {[%eval -56,24] [%emt 0:
01:02]} 24. h5 {[%eval 0,23] [%emt 0:00:14]} Rce8 {[%eval -42,22] [%emt 0:01:
29] (Ta8)} 25. Bd2 {[%eval 17,22] [%emt 0:00:14]} Qd8 {[%eval -35,22] [%emt 0:
00:28] (Kh7)} 26. Nh4 {[%eval 28,23] [%emt 0:00:14] (Kg2)} Nc8 {[%eval -63,21]
[%emt 0:00:09]} 27. Rh3 {[%eval 33,24] [%emt 0:00:14] (Sf3)} f6 {[%eval -32,21]
[%emt 0:00:37] (Db6)} 28. Ng6 {[%eval 43,22] [%emt 0:00:14]} Rf7 {[%eval -32,
19] [%emt 0:00:00]} 29. f4 {[%eval 42,22] [%emt 0:00:14] (Taa3)} Qb6 {[%eval
-15,20] [%emt 0:00:45] (Sf8)} 30. c3 {[%eval 86,23] [%emt 0:00:14] (Td3)} fxe5
{[%eval 35,19] [%emt 0:00:33] (Sa7)} 31. fxe5 {[%eval 113,26] [%emt 0:00:15]}
Ne7 {[%eval 24,17] [%emt 0:00:11]} 32. Nxe7+ {[%eval 127,27] [%emt 0:00:26]
(Sf4)} Rexe7 {[%eval 56,18] [%emt 0:00:10]} 33. g5 {[%eval 133,26] [%emt 0:00:
13]} Qb5 {[%eval 96,19] [%emt 0:00:19]} 34. Qg2 {[%eval 168,26] [%emt 0:00:13]}
c5 {[%eval 85,19] [%emt 0:00:06] (hxg5)} 35. gxh6 {[%eval 220,26] [%emt 0:00:
13] (bxc5)} cxd4 {[%eval 51,15] [%emt 0:00:09] (cxb4)} 36. Bg5 {[%eval 233,27]
[%emt 0:00:13]} Re8 {[%eval 51,14] [%emt 0:00:00]} 37. Bf6 {[%eval 221,28]
[%emt 0:00:21] (Tg3)} Nxf6 {[%eval 403,16] [%emt 0:00:11]} 38. exf6 {[%eval
210,29] [%emt 0:00:12]} Qd7 {[%eval 426,17] [%emt 0:00:07] (dxc3)} 39. Rf1 {
[%eval 553,25] [%emt 0:00:22]} e5 {[%eval 478,17] [%emt 0:00:10]} 40. Rg3 {
[%eval 992,24] [%emt 0:00:07] (cxd4)} a5 {[%eval 524,13] [%emt 0:00:03] (dxc3)}
41. Rxg7+ {[%eval 32754,67] [%emt 0:00:25] (cxd4)} Rxg7 {[%eval 1519,12] [%emt
0:00:00]} 42. fxg7 {[%eval 32756,127] [%emt 0:00:10]} Qf7 {[%eval 32758,20]
[%emt 0:00:02]} 43. Qg6 {[%eval 32758,127] [%emt 0:00:00]} Qxf1+ {[%eval 32760,
18] [%emt 0:00:00]} 44. Kxf1 {[%eval 32760,127] [%emt 0:00:00]} Rf8+ {[%eval
32762,16] [%emt 0:00:00]} 45. Kg2 {[%eval 32762,127] [%emt 0:00:00] (Kg1)} Rf2+
{[%eval 32764,14] [%emt 0:00:00]} 46. Kxf2 {[%eval 32764,127] [%emt 0:00:00]}
axb4 {[%eval 32766,12] [%emt 0:00:00] (dxc3)} 47. h7# {[%eval 32766,127] [%emt
0:00:00]} 1-0
[/pgn]
Whow ! Great game ! It's look like white is a GM playing against an amateur 8-)
When taking a closer look at this game I conclude
After 18 moves white has lost a pawn without much compensation.
After white pushed his pawns forward in an all or nothing attack at black kingside, his only chance, things became critical. One slip by Houdini 29 - Qb6? was enough to tilt the game in favor for white. After 29 - Ncb6 whites attack just leads to a draw
Frank Quisinsky
Posts: 7228
Joined: Wed Nov 18, 2009 7:16 pm
Location: Gutweiler, Germany
Full name: Frank Quisinsky

Re: Komodo, Houdini stats, great Hakkapeliitta game!

Post by Frank Quisinsky »

Hi Bram,

thanks for your comments to this very nice game.
We should have a look on Hakkapeliitta. A lot of such games are in my database. A very fine engine, with problems in endgame only.

Best
Frank