Dragon by Komodo Chess

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

Moderators: hgm, Rebel, chrisw

User avatar
cc2150dx
Posts: 325
Joined: Sat Nov 30, 2013 9:51 am
Location: Canada
Full name: Jason Coombs

Re: Dragon by Komodo Chess

Post by cc2150dx »

bastiball wrote: Mon Nov 23, 2020 1:22 pm How much the contempt affect Dragon? or it doesn't affect at all?
From Dragon readme file:

"A positive Contempt is used by the computer’s evaluation to discourage (or encourage if negative) piece trades, blocked pawn structures, and repetition draws early in the game."

"The default value 8 should help against weaker opponents. Against near-equal opponents e.g. (Stockfish 12/dev or Lc0) set Contempt to 0 for best results."

P.S. The second quote has been slightly modified.
bastiball
Posts: 5212
Joined: Tue Oct 20, 2020 4:18 am
Full name: Basti Dangca

Re: Dragon by Komodo Chess

Post by bastiball »

cc2150dx wrote: Mon Nov 23, 2020 2:42 pm
bastiball wrote: Mon Nov 23, 2020 1:22 pm How much the contempt affect Dragon? or it doesn't affect at all?
From Dragon readme file:

"A positive Contempt is used by the computer’s evaluation to discourage (or encourage if negative) piece trades, blocked pawn structures, and repetition draws early in the game."

"The default value 8 should help against weaker opponents. Against near-equal opponents e.g. (Stockfish 12/dev or Lc0) set Contempt to 0 for best results."

P.S. The second quote has been slightly modified.
Thanks for the info, appreciate it :D :D
Basti Dangca
CCRL testing group
User avatar
Nordlandia
Posts: 2821
Joined: Fri Sep 25, 2015 9:38 pm
Location: Sortland, Norway

Re: Dragon by Komodo Chess

Post by Nordlandia »

I tried this unique position for Dragon as black against SF and Lc0. It looks like white has good compensation for a couple of pawns. The compromise is that blacks are not allowed to castle.

So far, the games ends as draw. I was wondering if any other settings apart from default makes it doable for Dragon to win as black. For example if i increase/lower dynamism to make Dragon play more conservative or riskier with material advantage. What is your suggestion here. Is it likely that there are some exceptional settings that can be discovered ? comparable to "Kiudee-setting"

[d]rnbqkbnr/pppppppp/8/8/8/8/1PPPPPP1/RNBQKBNR w KQ - 0 1
lkaufman
Posts: 5960
Joined: Sun Jan 10, 2010 6:15 am
Location: Maryland USA

Re: Dragon by Komodo Chess

Post by lkaufman »

Nordlandia wrote: Mon Nov 23, 2020 4:18 pm I tried this unique position for Dragon as black against SF and Lc0. It looks like white has good compensation for a couple of pawns. The compromise is that blacks are not allowed to castle.

So far, the games ends as draw. I was wondering if any other settings apart from default makes it doable for Dragon to win as black. For example if i increase/lower dynamism to make Dragon play more conservative or riskier with material advantage. What is your suggestion here. Is it likely that there are some exceptional settings that can be discovered ? comparable to "Kiudee-setting"

[d]rnbqkbnr/pppppppp/8/8/8/8/1PPPPPP1/RNBQKBNR w KQ - 0 1
Settings that affect eval, such as Dynamism or King Safety, will have little effect in Dragon mode; they will only matter when regular eval is used, which in default mode is only in positions where it is unlikely to matter. The search parameters all work normally though.
Komodo rules!
User avatar
Nordlandia
Posts: 2821
Joined: Fri Sep 25, 2015 9:38 pm
Location: Sortland, Norway

Re: Dragon by Komodo Chess

Post by Nordlandia »

Dragon won just recently against Lc0 with dynamism raised to 120 and table memory at 128.
Leela 330 net used.
30m+30s TC.

[pgn][Event "i7-5960X 4.5GHz / 2x 2080 Supe"]
[Site "i7-5960X 4.5GHz / 2x 2080 Supe"]
[Date "2020.11.23"]
[Round "?"]
[White "lc0"]
[Black "dragon-64bit-avx2"]
[Result "0-1"]
[SetUp "1"]
[FEN "rnbqkbnr/pppppppp/8/8/8/8/1PPPPPP1/RNBQKBNR w KQ - 0 1"]
[PlyCount "105"]
[EventDate "2020.??.??"]
[TimeControl "1800+30"]

1. e4 {-0.29/11 32.54s} g6 {0.92/31 276.7s} 2. Nf3 {-0.32/12 93.74s} d6 {
1.00/30 73.69s} 3. d4 {-0.36/13 36.61s} Bg7 {0.79/31 193.9s} 4. Bc4 {-0.35/12
49.94s} h6 {0.66/30 102.2s} 5. O-O {-0.36/12 80.40s} Kf8 {0.78/31 124.2s} 6. b4
{-0.36/15 55.60s} a6 {0.86/30 58.99s} 7. Nbd2 {-0.35/13 50.86s} Nf6 {0.56/30
177.8s} 8. Bb2 {-0.35/14 67.12s} Bg4 {0.73/28 49.56s} 9. e5 {-0.35/19 46.13s}
Nh7 {0.88/32 155.6s} 10. Bb3 {-0.40/21 94.72s} Ng5 {1.13/28 37.97s} 11. Nxg5 {
-0.34/19 46.02s} Bxd1 {1.77/26 29.79s} 12. Nxf7 {-0.34/21 30.87s} Qc8 {1.05/29
37.04s} 13. Raxd1 {-0.38/19 74.96s} a5 {0.78/32 220.8s} 14. Nxh8 {-0.36/21 36.
73s} Bxh8 {0.90/31 75.22s} 15. b5 {-0.33/23 53.49s} a4 {0.99/28 53.14s} 16. Ba2
{-0.32/25 29.59s} Qd7 {0.79/31 82.30s} 17. c4 {-0.35/25 41.79s} a3 {1.23/30 43.
87s} 18. Ba1 {-0.42/21 106.9s} dxe5 {1.16/33 49.31s} 19. dxe5 {-0.61/23 117.6s}
Qe6 {1.42/30 27.99s} 20. Nf3 {-0.64/22 48.41s} Nd7 {1.04/32 37.54s} 21. Nd4 {
-0.53/25 106.5s} Qg8 {1.02/32 38.82s} 22. f4 {-0.54/27 31.38s} Ke8 {1.07/31 31.
16s} 23. Bc3 {-0.53/25 0.22s} Rd8 {1.54/32 49.69s} 24. Rfe1 {-0.64/28 109.3s}
g5 {1.68/32 40.73s} 25. f5 {-0.76/34 45.40s} Bxe5 {1.74/31 25.00s} 26. Ne6 {
-0.85/32 33.03s} Bxc3 {1.97/31 29.26s} 27. Nxc7+ {-0.97/33 48.56s} Kf8 {
1.71/34 39.23s} 28. Ne6+ {-1.02/29 35.07s} Kf7 {1.84/36 69.76s} 29. c5 {
-1.04/28 198.7s} Kf6 {1.89/33 37.23s} 30. Re2 {-1.03/30 0.26s} Be5 {2.03/32 32.
46s} 31. c6 {-1.07/28 0.46s} bxc6 {2.21/34 42.97s} 32. bxc6 {-1.01/32 117.2s}
Qe8 {2.24/34 30.86s} 33. Red2 {-1.07/34 49.75s} Qh5 {2.45/35 45.76s} 34. cxd7 {
-1.10/34 24.51s} Qh2+ {2.04/33 37.45s} 35. Kf1 {-1.11/34 1.27s} Bc7 {2.28/32
22.80s} 36. Nxd8 {-1.12/33 0.26s} Qh1+ {2.34/33 36.03s} 37. Kf2 {-1.15/30 82.
07s} Bb6+ {2.32/35 91.94s} 38. Kf3 {-1.15/35 0.27s} Qh5+ {2.17/32 49.64s} 39.
Ke4 {-1.15/29 1.41s} Qg4+ {2.37/33 42.22s} 40. Kd3 {-1.21/27 150.3s} Qxf5+ {
2.24/31 33.83s} 41. Kc4 {-1.23/29 241.4s} Qc5+ {2.30/33 40.86s} 42. Kb3 {
-1.25/28 17.01s} Bxd8 {2.61/30 64.86s} 43. Rd5 {-1.01/19 173.4s} Qb6+ {3.86/29
29.35s} 44. Ka4 {-1.00/27 3.71s} Kg7 {4.34/32 44.69s} 45. g4 {-1.56/16 157.0s}
e5 {6.99/28 29.66s} 46. Rd6 {-3.22/16 61.80s} Qa5+ {9.13/27 27.43s} 47. Kb3 {
-2.14/1 0.001s} e4 {9.81/28 33.97s} 48. R1d5 {-4.39/13 82.53s} Qc7 {9.75/27 24.
55s} 49. Ka4 {-4.95/14 68.76s} Qb8 {12.14/25 33.53s} 50. Re6 {-8.45/11 81.37s}
Qb2 {15.04/24 16.95s} 51. Re8 {-10.57/11 46.36s} Qxa2 {250.00/25 23.31s} 52.
Rc5 {-11.68/11 54.05s} Qb2 {250.00/23 4.70s} 53. Rxd8 {adjudication -12.39/11
33.58s, Black wins by adjudication} 0-1[/pgn]
Madeleine Birchfield
Posts: 512
Joined: Tue Sep 29, 2020 4:29 pm
Location: Dublin, Ireland
Full name: Madeleine Birchfield

Re: Dragon by Komodo Chess

Post by Madeleine Birchfield »

Alayan wrote: Tue Nov 10, 2020 8:42 pm
lkaufman wrote: Tue Nov 10, 2020 7:42 pm When both engines were set to use MultiPV=4 for standard chess, Dragon MCTS was able to defeat SF12 decisively in a 3600 games blitz match, so we believe that on most computers it is the world's strongest engine when looking at four or more lines of play at once.
This marketing claim "forgets" to acknowledge that this increased strength of the first move is achieved by reducing how deep the engines looks at lines beyond the first one. Indeed, the ability to report multiple PVs with eval, and dedicating similar resources to explore each of the lines, are separate concepts.

Play with MultiPV=4 only reflects the quality of the first move, not that of the 2nd, 3rd or 4th, and is a fundamentally flawed way to evaluate how useful a MultiPV implementation is.

The increased quality of the first move in Komodo (and Leela) MCTS comes at the cost of a lowered quality and reliability for the moves, PV and evals of the 2nd and further lines come from smaller search trees. Turning MultiPV on in these engines doesn't increase the likelihood that they discover an initially disliked move is much better than first thought.

Most people that do use MultiPV for analysis expressed strong opposition to this trade-off when reducing 2nd and further PV lines was considered for Stockfish, though in some circumstances (moves that are much worse than the main move) it can be useful.

For deep analysis, multiPV isn't going to be used on positions with one clear forced move anyway, and the effective time-handicap that makes KMCTS look good at blitz matter much less while the search/eval deficit remain, making Stockfish the best MultiPV engine for e.g. correspondence chess.
Furthermore, Larry Kaufman based his claims on a sample size of one (a blitz game) which is simply not enough evidence to conclude anythung. In fact, extensive testing by Stefan Pohl show Dragon MCTS to be 180 elo worse than Dragon AB, around the level of Stockfish 9.

http://talkchess.com/forum3/viewtopic.php?f=6&t=75900
https://www.sp-cc.de

Following Larry Kaufman's logic with this evidence would mean that Dragon AB is far better than Dragon MCTS for analysis.
lkaufman
Posts: 5960
Joined: Sun Jan 10, 2010 6:15 am
Location: Maryland USA

Re: Dragon by Komodo Chess

Post by lkaufman »

Madeleine Birchfield wrote: Mon Nov 23, 2020 9:18 pm
Alayan wrote: Tue Nov 10, 2020 8:42 pm
lkaufman wrote: Tue Nov 10, 2020 7:42 pm When both engines were set to use MultiPV=4 for standard chess, Dragon MCTS was able to defeat SF12 decisively in a 3600 games blitz match, so we believe that on most computers it is the world's strongest engine when looking at four or more lines of play at once.
This marketing claim "forgets" to acknowledge that this increased strength of the first move is achieved by reducing how deep the engines looks at lines beyond the first one. Indeed, the ability to report multiple PVs with eval, and dedicating similar resources to explore each of the lines, are separate concepts.

Play with MultiPV=4 only reflects the quality of the first move, not that of the 2nd, 3rd or 4th, and is a fundamentally flawed way to evaluate how useful a MultiPV implementation is.

The increased quality of the first move in Komodo (and Leela) MCTS comes at the cost of a lowered quality and reliability for the moves, PV and evals of the 2nd and further lines come from smaller search trees. Turning MultiPV on in these engines doesn't increase the likelihood that they discover an initially disliked move is much better than first thought.

Most people that do use MultiPV for analysis expressed strong opposition to this trade-off when reducing 2nd and further PV lines was considered for Stockfish, though in some circumstances (moves that are much worse than the main move) it can be useful.

For deep analysis, multiPV isn't going to be used on positions with one clear forced move anyway, and the effective time-handicap that makes KMCTS look good at blitz matter much less while the search/eval deficit remain, making Stockfish the best MultiPV engine for e.g. correspondence chess.
Furthermore, Larry Kaufman based his claims on a sample size of one (a blitz game) which is simply not enough evidence to conclude anythung. In fact, extensive testing by Stefan Pohl show Dragon MCTS to be 180 elo worse than Dragon AB, around the level of Stockfish 9.

http://talkchess.com/forum3/viewtopic.php?f=6&t=75900
https://www.sp-cc.de

Following Larry Kaufman's logic with this evidence would mean that Dragon AB is far better than Dragon MCTS for analysis.
??? My sample size was 3600 games, not one game! I don't follow your logic here at all. We certainly don't claim that Dragon AB is superior to Dragon MCTS for Multipv (3 or more) analysis, but it is certainly superior for analysis with no MultiPV. MultiPV cripples normal engines like Dragon AB and Stockfish, that's why Dragon MCTS can win a long match from SF 12 if both use MultiPV of 4. If they don't use MultiPV, then Dragon MCTS is still stronger than Komodo 14.1 in standard mode (as Stefan Pohl confirmed), but it is weaker than SF11, never mind 12. Our testing is not contradicted by Stefan Pohl's results, we're talking about two very different uses of the engines.
Komodo rules!
Chessqueen
Posts: 5582
Joined: Wed Sep 05, 2018 2:16 am
Location: Moving
Full name: Jorge Picado

Re: Dragon by Komodo Chess

Post by Chessqueen »

mwyoung wrote: Fri Nov 13, 2020 6:36 pm
Cornfed wrote: Fri Nov 13, 2020 6:06 pm Still about 80 points behind a similar current Stockfish. Not bad.
At 5m+5s on a 32 thread 2950x. Dragon is doing much better then 80 Elo. Very good for the first release of Dragon.

Mark L. asked my to change the default setting for hash memory from default. I do not know if this changed the results. Default was 64, and was changed to 512. The suggested best setting for this many threads.

Here is the results playing the best Stockfish.

Dragon by Komodo Chess vs Stockfish 101120 (TC=5m+5s)

With 198 games played so far. Dragon vs Stockfish 101120 +6 =172 -20. 46.5% TP = -25 Elo.

Live Stream
Why doesn't MwYoung start a 200 games match like you did with Stockfish normal but against MCTS vs Stockfish-NNUE in FRC?
Do NOT worry and be happy, we all live a short life :roll:
Cornfed
Posts: 511
Joined: Sun Apr 26, 2020 11:40 pm
Full name: Brian D. Smith

Re: Dragon by Komodo Chess

Post by Cornfed »

Chessqueen wrote: Tue Nov 24, 2020 5:53 pm
mwyoung wrote: Fri Nov 13, 2020 6:36 pm
Cornfed wrote: Fri Nov 13, 2020 6:06 pm Still about 80 points behind a similar current Stockfish. Not bad.
At 5m+5s on a 32 thread 2950x. Dragon is doing much better then 80 Elo. Very good for the first release of Dragon.

Mark L. asked my to change the default setting for hash memory from default. I do not know if this changed the results. Default was 64, and was changed to 512. The suggested best setting for this many threads.

Here is the results playing the best Stockfish.

Dragon by Komodo Chess vs Stockfish 101120 (TC=5m+5s)

With 198 games played so far. Dragon vs Stockfish 101120 +6 =172 -20. 46.5% TP = -25 Elo.

Live Stream
Why doesn't MwYoung start a 200 games match like you did with Stockfish normal but against MCTS vs Stockfish-NNUE in FRC?
Better yet...how can only 6 wins vs 20 losses = a mere -25 elo difference?

I know, of course, it's all the draws; but to measure by elo like this is kind of shortsighted as a way to try to quantify and be meaningful. The ability to 'win'/'lose' should be a bit more important in thinking of how one program fairs against another.

In this case:
Over a 1000 game match you get 30 wins vs 100 losses.
Over a 10,000 game match you get 300 wins vs 1000 losses.

Opinions can vary, but a 30% to 70% ratio among decisive games seems pretty meaningful. In a 10 game match (thinking for a sec about Fischer's proposal for a title match) where draws don't matter (hey, it's a half point for each...neither side actually gains anything...except mere elo for all the draws ...nod to Ulf Andersson being #3 in the world rankings at one time), a 7-3 result would be considered a route.
Madeleine Birchfield
Posts: 512
Joined: Tue Sep 29, 2020 4:29 pm
Location: Dublin, Ireland
Full name: Madeleine Birchfield

Re: Dragon by Komodo Chess

Post by Madeleine Birchfield »

Will Dragon by Komodo Chess be playing in TCEC Season 20?