Komodo 3 release

Discussion of anything and everything relating to chess playing software and machines.

Moderators: hgm, Rebel, chrisw

Robert Flesher
Posts: 1280
Joined: Tue Aug 18, 2009 3:06 am

Re: Komodo 3 release

Post by Robert Flesher »

Don wrote:
Thomas Lagershausen wrote:
Don wrote:
perejaslav wrote:Komodo is VERY weak in tactics. Do you plan to change this state of things?
Komodo is only weak in tactics if you compare it to other chess programs - but realistically that is not an issue for any good program. The reason programs lose chess games is almost solely because of bad positional or strategic decisions, not because of tactics. And we are much more interested in distinguishing Komodo by its positional play and not for tactics.

It would be ok with me of course if Komodo were stronger tactically as long as it was still a good chess player but it's not really where our focus is right now.
This statement give me reason furthermore to be interested in computerchess. 8-)

I have waited so long to hear this words from an programmer.

Now the party can be started. :D
It's my belief that positional play is the next breakthrough in computer chess. We have studied many games of Komodo and and tried to determine why it wins and loses. That was the basis of some of the improvements in Komodo 3. You never win a game due to a flashy combination - it has to be because the opponent made an error that allowed you to win. Of course you can lose a won or drawn game by failing to see a tactic and thus making the wrong move that loses tactically, but that is actually extremely rare. In most of the tactics where you win for tactical reasons you win anyway even if you miss the tactics because you have a won position. Or you play the right move even though you do not yet see the tactics. Of course from time to time you can throw the win away - but again - that's not the big problem in computer chess.

When I did the similarity tester last year it was an eye opener for me. Not because of the clone issues or anything like that, but because it showed that a lot of decisions a program makes are "baked in" to each chess program. You can call it a stylistic preference and there is nothing wrong with that, but comparing any program against itself at a much deeper level doesn't change it's playing style and it's "baked in" preferences.

That is all well and good, but a percentage of those preferences can be considered biases that hurt the program and cause bad strategic decisions. In one case that we identified, Komodo plays a "weak" move and a super deep search does not correct it because it's not a tactical issue and it does not reveal anything that changes Komodo's mind. It might not have been a losing move technically but it turns the game from a possible win to a sure (and perhaps even difficult) draw.

That's why I believe this will be the next big thing that we must learn how to deal with and improve upon. Systematic error and misconceptions if you want to call it that. Of course knowing that and fixing it are two different things - but we are trying to attack the problem.

It's a little tricky because sometimes you see the odd move that no human would make that looks rather ugly - but the more you analyze it the more you see that it may not be so bad or even that it's good and YOU are the one that is wrong - the computer was not as stupid as you thought. But every program will occasionally plays the odd move that constitutes a bad decision point.

Another way to see this, and something that is along the same lines, is trying to win more games when you have an advantage. As programs get stronger you see more and more draws and that is how it should be. However, it's my belief that in some cases the advantage may have been enough for a win but it required an understanding of the position that the program did not possess. So we are looking into that too.

This post is extremely interesting to me! I have posted the question here many times over many years, "will tactics eventually refute positional play?" Although I cannot decide, it is an interesting thing to ponder.

However, regarding engine strength, what is it that makes Houndini still noticeably stronger than all the other engines. Is it the better positional player? Or is Houdini's strength based on a great tactical search and some positional knowledge?
Wolfgang
Posts: 895
Joined: Sat May 13, 2006 1:08 am

Re: Komodo 3 release

Post by Wolfgang »

Don wrote:We are working on the next Komodo release now.

Already available are Komodo 3 for Android and Komodo 3 for 64 bit Linux. Hopefully we will have Komodo 3 for windows in the next day or two.

You can get it here:

http://komodochess.com


We believe we have approximately 30 ELO of improvement and more at non-fischer time controls which we were deficient in. However it's difficult to say for sure how much we have gained as this depends on how it scales to time controls we don't test at.

The majority of the gain has come from evaluation improvements.
Hi,

thanks for the new version. Will it be "MP" too?

Best
Wolfgang
CEGT-Team
User avatar
Don
Posts: 5106
Joined: Tue Apr 29, 2008 4:27 pm

Re: Komodo 3 release

Post by Don »

Wolfgang wrote:
Don wrote:We are working on the next Komodo release now.

Already available are Komodo 3 for Android and Komodo 3 for 64 bit Linux. Hopefully we will have Komodo 3 for windows in the next day or two.

You can get it here:

http://komodochess.com


We believe we have approximately 30 ELO of improvement and more at non-fischer time controls which we were deficient in. However it's difficult to say for sure how much we have gained as this depends on how it scales to time controls we don't test at.

The majority of the gain has come from evaluation improvements.
Hi,

thanks for the new version. Will it be "MP" too?

Best
Wolfgang
CEGT-Team
This is the last non-MP release. The next Komodo will have more improvements and also have an MP version - probably a separate binary.
Frank Quisinsky
Posts: 6808
Joined: Wed Nov 18, 2009 7:16 pm
Location: Gutweiler, Germany
Full name: Frank Quisinsky

Re: Komodo 3 release

Post by Frank Quisinsky »

Hi there,

in my opinion its the pawn structur and the extrem good balance between Rocks and Queen in combination with pawns in the late middlegame, early endgame. Houdini is fighting here, will not give games early remis. It seems the same do Komodo since version 2.0.

I try in the latest week to find out the strength from Komodo and made some analyzes in the late middlegame. A short advantage to Houdini in the game analyzes (moves 60 - 90). Remis quote is very small. Komodo hold the own figures on the board, try to reach better positions every time and have an excellant pawn structur. After all I saw Komodo have an advantage to all other engines here, to Houdini too.

Houdini have the advantage that in the early middlegame the results in "search a fast advantage" is clearly better. Komodo is looking more of better positions on the own site in the early middlegame as to search with tactical combination for an fast advantage.

Not sure, wrote in CSS Forum today about my analyzes. For me and all the games played on my computers it's very complicated to try to find out the reasons, without to know the program in detail and without more own chess knowledge. So, never I am sure with my own impessions but I have fun to try to find out more about engines.

For late middlegame analyzes you need a lot of time, fantasy in create statistics and chess knowledge ... a big database :-)

Best
Frank

Very interesting what the Don wrote here.
Thanks for it too!
Robert Flesher
Posts: 1280
Joined: Tue Aug 18, 2009 3:06 am

Re: Komodo 3 release

Post by Robert Flesher »

Frank Quisinsky wrote:Hi there,

in my opinion its the pawn structur and the extrem good balance between Rocks and Queen in combination with pawns in the late middlegame, early endgame. Houdini is fighting here, will not give games early remis. It seems the same do Komodo since version 2.0.

I try in the latest week to find out the strength from Komodo and made some analyzes in the late middlegame. A short advantage to Houdini in the game analyzes (moves 60 - 90). Remis quote is very small. Komodo hold the own figures on the board, try to reach better positions every time and have an excellant pawn structur. After all I saw Komodo have an advantage to all other engines here, to Houdini too.

Houdini have the advantage that in the early middlegame the results in "search a fast advantage" is clearly better. Komodo is looking more of better positions on the own site in the early middlegame as to search with tactical combination for an fast advantage.

Not sure, wrote in CSS Forum today about my analyzes. For me and all my games is it very complicated to try to find out the reasons, without to know the program in detail and without more own chess knowledge. So, never I am sure with my own impessions but I have fun to do that or to try to find out more about engines.

Best
Frank

Very interesting what the Don wrote here.
Thanks for it too!

Thanks Frank! Interesting, and this observation confirms some of my thoughts about Houdini.
Frank Quisinsky
Posts: 6808
Joined: Wed Nov 18, 2009 7:16 pm
Location: Gutweiler, Germany
Full name: Frank Quisinsky

Re: Komodo 3 release

Post by Frank Quisinsky »

Hi Robert,

thanks!
I correct my bad English in my latest message.
Better to read know, think so ...

Best
Frank

PS: Before I start the own Komodo analyzes I am a bit disappointed about the weaknesses in tactic too. But after the SWCR statistics and own different analyzes to the late middlegame, Komodo is my absolute number 1 here in my selection of engines for this playing phase. Tactical monster we have enough but the strengths from Komodo are a "Special".
bhlangonijr
Posts: 482
Joined: Thu Oct 16, 2008 4:23 am
Location: Milky Way

Re: Komodo 3 release

Post by bhlangonijr »

Don wrote: It's my belief that positional play is the next breakthrough in computer chess. We have studied many games of Komodo and and tried to determine why it wins and loses. That was the basis of some of the improvements in Komodo 3. You never win a game due to a flashy combination - it has to be because the opponent made an error that allowed you to win. Of course you can lose a won or drawn game by failing to see a tactic and thus making the wrong move that loses tactically, but that is actually extremely rare. In most of the tactics where you win for tactical reasons you win anyway even if you miss the tactics because you have a won position. Or you play the right move even though you do not yet see the tactics. Of course from time to time you can throw the win away - but again - that's not the big problem in computer chess.

When I did the similarity tester last year it was an eye opener for me. Not because of the clone issues or anything like that, but because it showed that a lot of decisions a program makes are "baked in" to each chess program. You can call it a stylistic preference and there is nothing wrong with that, but comparing any program against itself at a much deeper level doesn't change it's playing style and it's "baked in" preferences.

That is all well and good, but a percentage of those preferences can be considered biases that hurt the program and cause bad strategic decisions. In one case that we identified, Komodo plays a "weak" move and a super deep search does not correct it because it's not a tactical issue and it does not reveal anything that changes Komodo's mind. It might not have been a losing move technically but it turns the game from a possible win to a sure (and perhaps even difficult) draw.

That's why I believe this will be the next big thing that we must learn how to deal with and improve upon. Systematic error and misconceptions if you want to call it that. Of course knowing that and fixing it are two different things - but we are trying to attack the problem.

It's a little tricky because sometimes you see the odd move that no human would make that looks rather ugly - but the more you analyze it the more you see that it may not be so bad or even that it's good and YOU are the one that is wrong - the computer was not as stupid as you thought. But every program will occasionally plays the odd move that constitutes a bad decision point.

Another way to see this, and something that is along the same lines, is trying to win more games when you have an advantage. As programs get stronger you see more and more draws and that is how it should be. However, it's my belief that in some cases the advantage may have been enough for a win but it required an understanding of the position that the program did not possess. So we are looking into that too.
Hi Don, very good post!

It is refreshing after so many trashing posts about the Rybka-Fruit-Craifty affair.

Are you planning to use different techniques to accomplish it?
IMO, the efficiency of the high selectivity and aggressive pruning in top chess programs suggests that chess itself has some essential properties that can be better explored by using less brute-force.

Looking forward to the new Komodo "Botvinnik" personality. :)

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

Re: Perhaps a good example ...

Post by Frank Quisinsky »

Code: Select all

[Event "40 Züge in 10 min"]
[Site "swcr-32-2, A3"]
[Date "2011.08.16"]
[Round "19.17"]
[White "Houdini 1.5 w32"]
[Black "GullChess 1.2 w32"]
[Result "1-0"]
[PlyCount "67"]
[EventDate "2011.??.??"]

1. e4 {[%eval 0,0] [%emt 0:00:00]} e6 {[%eval 0,0] [%emt 0:00:00]} 2. d4 {
[%eval 0,0] [%emt 0:00:00]} d5 {[%eval 0,0] [%emt 0:00:00]} 3. Nd2 {[%eval 0,0]
[%emt 0:00:00]} Nc6 {[%eval 0,0] [%emt 0:00:00]} 4. Ngf3 {[%eval 0,0] [%emt 0:
00:00]} Nf6 {[%eval 0,0] [%emt 0:00:00]} 5. e5 {[%eval 0,0] [%emt 0:00:00]} Nd7
{[%eval 0,0] [%emt 0:00:00]} 6. Bd3 {[%eval 0,0] [%emt 0:00:00]} Nb4 {[%eval 0,
0] [%emt 0:00:00]} 7. Be2 {[%eval 0,0] [%emt 0:00:00]} c5 {[%eval 0,0] [%emt 0:
00:00]} 8. c3 {[%eval 0,0] [%emt 0:00:00]} Nc6 {[%eval 0,0] [%emt 0:00:00]} 9.
O-O {[%eval 19,18] [%emt 0:01:17]} Be7 {[%eval 7,18] [%emt 0:00:19]} 10. a3 {
[%eval 16,18] [%emt 0:00:05] (Sb3)} Qb6 {[%eval -1,17] [%emt 0:00:15] (a5)} 11.
Nb3 {[%eval 27,19] [%emt 0:00:13]} O-O {[%eval 7,17] [%emt 0:00:06] (c4)} 12.
Nxc5 {[%eval 33,19] [%emt 0:00:14]} Nxc5 {[%eval 15,17] [%emt 0:00:08]} 13.
dxc5 {[%eval 38,18] [%emt 0:00:00]} Qc7 {[%eval 10,17] [%emt 0:00:21]} 14. Bf4
{[%eval 44,19] [%emt 0:00:00]} Bxc5 {[%eval 9,17] [%emt 0:00:16]} 15. Rc1 {
[%eval 38,19] [%emt 0:01:11]} a5 {[%eval 8,18] [%emt 0:00:00] (Td8)} 16. b4 {
[%eval 44,19] [%emt 0:00:12] (Dd2)} Ba7 {[%eval 14,17] [%emt 0:00:26]} 17. Qd2
{[%eval 44,18] [%emt 0:00:00] (b5)} axb4 {[%eval 17,16] [%emt 0:00:46] (Td8)}
18. cxb4 {[%eval 48,17] [%emt 0:00:22]} Qb6 {[%eval 21,17] [%emt 0:01:17] (Dd7)
} 19. Bd3 {[%eval 55,17] [%emt 0:00:14]} Re8 {[%eval 18,16] [%emt 0:00:09]} 20.
Bg5 {[%eval 99,18] [%emt 0:00:38] (Tfd1)} Bd7 {[%eval 15,15] [%emt 0:00:19] 
(Se7)} 21. Qf4 {[%eval 446,15] [%emt 0:00:14] (b5)} Nd4 {[%eval 117,14] [%emt
0:00:25] (Tec8)} 22. Bf6 {[%eval 1584,15] [%emt 0:00:12] (Lxh7+)} Ne2+ {[%eval
1271,14] [%emt 0:01:25] (h6)} 23. Bxe2 {[%eval 1806,16] [%emt 0:00:04]} h6 {
[%eval 1565,15] [%emt 0:01:02]} 24. Qg3 {[%eval 2003,19] [%emt 0:00:00] (Dg4)}
g6 {[%eval 1072,14] [%emt 0:00:52]} 25. Qf4 {[%eval 2789,19] [%emt 0:00:57]}
Qe3 {[%emt 0:00:00] +M-1370/16  (Kh7)} 26. fxe3 {[%eval 2774,8] [%emt 0:00:00]}
Kh7 {[%emt 0:00:09] +M-1371/14  (Tec8)} 27. Ng5+ {[%eval 32752,21] [%emt 0:00:
04] (Sd4)} Kg8 {[%emt 0:00:06] +M-1372/14} 28. Nxf7 {[%eval 32754,21] [%emt 0:
00:00]} Rf8 {[%emt 0:00:05] +M-1373/15  (Tac8)} 29. Qxh6 {[%eval 32756,21] 
[%emt 0:00:02]} Bxe3+ {[%emt 0:00:01] +M-1374/23} 30. Qxe3 {[%eval 32758,23] 
[%emt 0:00:00]} Rxf7 {[%emt 0:00:04] +M-1375/40  (Kxf7)} 31. Qh6 {[%eval 32760,
17] [%emt 0:00:00]} Rh7 {[%emt 0:00:00] +M-1376/55} 32. Qxg6+ {[%eval 32762,99]
[%emt 0:00:00]} Kf8 {[%emt 0:00:00] +M-1377/55} 33. Bh4+ {[%eval 32764,99] 
[%emt 0:00:00] (Lg5+)} Rf7 {[%emt 0:00:00] +M-1378/6} 34. Qxf7# {[%eval 32766,
1] [%emt 0:00:00]} 1-0
Hi Robert,

what I would do in the evening :-)
One of the latest SWCR games from today. Here move 20. black is interesting. Gullchess is very weak in tactic, not the attacker compare to Komodo.

Houdini found the right move very fast and that is the different in openings. In this case a very fast and big advantage Houdini found. Not sure, but I believe Komodo cann't see the problem in this position too. On the other hand Komodo is good in king safty. I will analyze the postion in the evening.

Test it:
Question 1: Found Komodo the a better move as GullChess.
Question 2: Found Komodo the move Houdini plays.

I think, Question 1 yes
I think, Question 2 no

without to test it.
:-)

Best
Frank
User avatar
Don
Posts: 5106
Joined: Tue Apr 29, 2008 4:27 pm

Re: Komodo 3 release

Post by Don »

Robert Flesher wrote:
Don wrote:
Thomas Lagershausen wrote:
Don wrote:
perejaslav wrote:Komodo is VERY weak in tactics. Do you plan to change this state of things?
Komodo is only weak in tactics if you compare it to other chess programs - but realistically that is not an issue for any good program. The reason programs lose chess games is almost solely because of bad positional or strategic decisions, not because of tactics. And we are much more interested in distinguishing Komodo by its positional play and not for tactics.

It would be ok with me of course if Komodo were stronger tactically as long as it was still a good chess player but it's not really where our focus is right now.
This statement give me reason furthermore to be interested in computerchess. 8-)

I have waited so long to hear this words from an programmer.

Now the party can be started. :D
It's my belief that positional play is the next breakthrough in computer chess. We have studied many games of Komodo and and tried to determine why it wins and loses. That was the basis of some of the improvements in Komodo 3. You never win a game due to a flashy combination - it has to be because the opponent made an error that allowed you to win. Of course you can lose a won or drawn game by failing to see a tactic and thus making the wrong move that loses tactically, but that is actually extremely rare. In most of the tactics where you win for tactical reasons you win anyway even if you miss the tactics because you have a won position. Or you play the right move even though you do not yet see the tactics. Of course from time to time you can throw the win away - but again - that's not the big problem in computer chess.

When I did the similarity tester last year it was an eye opener for me. Not because of the clone issues or anything like that, but because it showed that a lot of decisions a program makes are "baked in" to each chess program. You can call it a stylistic preference and there is nothing wrong with that, but comparing any program against itself at a much deeper level doesn't change it's playing style and it's "baked in" preferences.

That is all well and good, but a percentage of those preferences can be considered biases that hurt the program and cause bad strategic decisions. In one case that we identified, Komodo plays a "weak" move and a super deep search does not correct it because it's not a tactical issue and it does not reveal anything that changes Komodo's mind. It might not have been a losing move technically but it turns the game from a possible win to a sure (and perhaps even difficult) draw.

That's why I believe this will be the next big thing that we must learn how to deal with and improve upon. Systematic error and misconceptions if you want to call it that. Of course knowing that and fixing it are two different things - but we are trying to attack the problem.

It's a little tricky because sometimes you see the odd move that no human would make that looks rather ugly - but the more you analyze it the more you see that it may not be so bad or even that it's good and YOU are the one that is wrong - the computer was not as stupid as you thought. But every program will occasionally plays the odd move that constitutes a bad decision point.

Another way to see this, and something that is along the same lines, is trying to win more games when you have an advantage. As programs get stronger you see more and more draws and that is how it should be. However, it's my belief that in some cases the advantage may have been enough for a win but it required an understanding of the position that the program did not possess. So we are looking into that too.

This post is extremely interesting to me! I have posted the question here many times over many years, "will tactics eventually refute positional play?" Although I cannot decide, it is an interesting thing to ponder.
Given enough depth, the game could be solved technically with no need for an evaluation function other than win/loss/draw information.

However, in the real world a deep search is a like a magnifying glass - it magnifies the power of the evaluation function. Whatever is wrong with the evaluation at end nodes is what is mini-maxed back to the root and it is what matters.

A search can overcome incorrect evaluation - but it has to "see past" the misconception. I'll give you a real simple example that everyone should understand:

Bishop of opposite color endings are generally drawn even when one side is up a pawn or even two. Not always, but usually. So let's imagine that the program has to make a decision that will EVENTUALLY take the game into either a bishop of opposite color ending where you are 2 pawns up or some other ending where you are just have a good position but you are not up any material - but with a technical win. Perhaps it takes a 30 ply search just to see that you basically are presented with just these 2 types of positions that you can achieve. So you need a 30 ply search to see that you have these 2 "choices" but you might need an additional 50 ply search to see that the bishop of opposite color is a draw, and the other position is a win.

The "won" position may involved the ability to created a passed pawn that cannot be stopped without giving up something - but the program cannot see that any time soon, it has to have a strong sense that it needs to get into that type of position even without much of a search. The bishop of opposite color position which is a draw (in our example) has a material advantage of 2 pawns but the story is the same, the program really has to understand that the two pawn advantage doesn't mean anything. So the scoring of BOTH of these endings must conspire in order to make the correct decision and it is critical that the programs has a good sense of each.

My example is somewhat exaggerated and simplified, but I think it makes the point. Once the program is in either position it will probably play either very well, but that is not a big problem with computers, it's knowing what positions to go for when a choice of significantly different positions are available. Program are very good at determine which of two very similar positions are better, but very poor at determining which position is better when they are significantly different.

Years ago Cilkchess was in a tournament and I remember that it made a major decision giving it 2 connected flank passed pawns but allowing what seemed to me to be a pretty crushing center by the opponent. Cilkchess was searching far deeper than any program at the tournament but I remember thinking that the game might come down to this one decision and have little to do with the depth of search. Would it ever be able to make any progress before getting crushed in the center? Cilkchess won that game and probably made the right decision, but it illustrated to me that tactics and seeing a little deeper is not everything. Of course I always knew that, but this just drove the point home for me. As it turned out I don't think Cilkchess was ever in trouble and I probably was just nervous for my program - but that is besides the point - which is that it had to make a decision that it couldn't just search it's way through, it had to JUDGE the positions.

Another issue is that not all draws are created equal. You can have a technically drawn position but one of them might be very difficult to hold, and the other may have good chances for winning because it is difficult for the opponent to hold. No amount of searching can EVER give you the right answer for those positions if a draw is draw is a draw .... but those will be important for a long time to come. I can imagine in the future when program play 4000 ELO level most of the games will be draws but what might distinguish the best program from the 50th rank program might be that one game in 20 or 30 than the 50th program could not hold.

It's already like that in checkers for example in opening selection. Shaeffer and others have noticed that in checkers every opening is a draw, but to get that occasional win you have to find the tricky ones, the ones have some potential for the opponent to make a mistake and that are less easily played. Chess openings are a little like that already - some openings have a reputation for being more drawish than others and you don't play them if you need a win.
However, regarding engine strength, what is it that makes Houndini still noticeably stronger than all the other engines. Is it the better positional player? Or is Houdini's strength based on a great tactical search and some positional knowledge?
Houdini is based strongly on the Ippo family of programs and plays in a very similar way. However I believe Houdart put some work into every aspect of Houdini including the evaluation function. All of these program are very strong and have good evaluation functions and superb searches. I believe their searches are far better than their evaluation functions but it's not really that easy to categorize these things and computer chess is much like a black art where things are not always as they seem.

By the way, you can find tons of examples where any given program will make a better decision than another and will appear to have a much better evaluation function. That is not odd, what would be odd is if some program always played a better move in every position. Every program has unique positional strengths and weakness and holes that need to be plugged.
Albert Silver
Posts: 3019
Joined: Wed Mar 08, 2006 9:57 pm
Location: Rio de Janeiro, Brazil

Re: Perhaps a good example ...

Post by Albert Silver »

Frank Quisinsky wrote:

Code: Select all

[Event "40 Züge in 10 min"]
[Site "swcr-32-2, A3"]
[Date "2011.08.16"]
[Round "19.17"]
[White "Houdini 1.5 w32"]
[Black "GullChess 1.2 w32"]
[Result "1-0"]
[PlyCount "67"]
[EventDate "2011.??.??"]

1. e4 {[%eval 0,0] [%emt 0:00:00]} e6 {[%eval 0,0] [%emt 0:00:00]} 2. d4 {
[%eval 0,0] [%emt 0:00:00]} d5 {[%eval 0,0] [%emt 0:00:00]} 3. Nd2 {[%eval 0,0]
[%emt 0:00:00]} Nc6 {[%eval 0,0] [%emt 0:00:00]} 4. Ngf3 {[%eval 0,0] [%emt 0:
00:00]} Nf6 {[%eval 0,0] [%emt 0:00:00]} 5. e5 {[%eval 0,0] [%emt 0:00:00]} Nd7
{[%eval 0,0] [%emt 0:00:00]} 6. Bd3 {[%eval 0,0] [%emt 0:00:00]} Nb4 {[%eval 0,
0] [%emt 0:00:00]} 7. Be2 {[%eval 0,0] [%emt 0:00:00]} c5 {[%eval 0,0] [%emt 0:
00:00]} 8. c3 {[%eval 0,0] [%emt 0:00:00]} Nc6 {[%eval 0,0] [%emt 0:00:00]} 9.
O-O {[%eval 19,18] [%emt 0:01:17]} Be7 {[%eval 7,18] [%emt 0:00:19]} 10. a3 {
[%eval 16,18] [%emt 0:00:05] (Sb3)} Qb6 {[%eval -1,17] [%emt 0:00:15] (a5)} 11.
Nb3 {[%eval 27,19] [%emt 0:00:13]} O-O {[%eval 7,17] [%emt 0:00:06] (c4)} 12.
Nxc5 {[%eval 33,19] [%emt 0:00:14]} Nxc5 {[%eval 15,17] [%emt 0:00:08]} 13.
dxc5 {[%eval 38,18] [%emt 0:00:00]} Qc7 {[%eval 10,17] [%emt 0:00:21]} 14. Bf4
{[%eval 44,19] [%emt 0:00:00]} Bxc5 {[%eval 9,17] [%emt 0:00:16]} 15. Rc1 {
[%eval 38,19] [%emt 0:01:11]} a5 {[%eval 8,18] [%emt 0:00:00] (Td8)} 16. b4 {
[%eval 44,19] [%emt 0:00:12] (Dd2)} Ba7 {[%eval 14,17] [%emt 0:00:26]} 17. Qd2
{[%eval 44,18] [%emt 0:00:00] (b5)} axb4 {[%eval 17,16] [%emt 0:00:46] (Td8)}
18. cxb4 {[%eval 48,17] [%emt 0:00:22]} Qb6 {[%eval 21,17] [%emt 0:01:17] (Dd7)
} 19. Bd3 {[%eval 55,17] [%emt 0:00:14]} Re8 {[%eval 18,16] [%emt 0:00:09]} 20.
Bg5 {[%eval 99,18] [%emt 0:00:38] (Tfd1)} Bd7 {[%eval 15,15] [%emt 0:00:19] 
(Se7)}
One of the latest SWCR games from today. Here move 20. black is interesting. Gullchess is very weak in tactic, not the attacker compare to Komodo.

Houdini found the right move very fast and that is the different in openings. In this case a very fast and big advantage Houdini found.

Test it:
Question 1: Found Komodo the a better move as GullChess.
Question 2: Found Komodo the move Houdini plays.

I think, Question 1 yes
I think, Question 2 no

without to test it.
:-)

Best
Frank
[D]r1b1r1k1/bp3ppp/1qn1p3/3pP3/1P3B2/P2B1N2/3Q1PPP/2R2RK1 w - - 0 20

Yes, I ran it, and it is interesting that in your game Houdini missed the best move 20.Bxh7+, nice find.
"Tactics are the bricks and sticks that make up a game, but positional play is the architectural blueprint."