Yes, two moves isn't enough. But three is too many. You could rerun the same test with WTM each position to confirm this.Guenther wrote: ↑Fri Jul 26, 2019 6:30 pmI did a quick test with CFish20190717 vs. itself and surprisingly the draw rate was still very high > 70% at a fast tc of 40/40''.OneTrickPony wrote: ↑Fri Jul 26, 2019 2:01 pm What about: white gets to make 2 first moves and gives draw odds.
Lc0 eval is similar to opposite castling armageddon proposed in OP but it's even simpler to explain.
used this set of positions:
Code: Select all
rnbqkbnr/pppppppp/8/8/3PP3/8/PPP2PPP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3P4/5N2/PPP1PPPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2PP4/8/PP2PPPP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2P5/2N5/PP1PPPPP/R1BQKBNR b KQkq - 0 1 kbnr/pppppppp/8/8/2P5/6P1/PP1PPP1P/RNBQKBNR b KQkq - 0 1 kbnr/pppppppp/8/8/2P5/5N2/PP1PPPPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4PP2/8/PPPP2PP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4P3/2N5/PPPP1PPP/R1BQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/8/1P6/PBPPPPPP/RN1QKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/8/6P1/PPPPPPBP/RNBQK1NR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/5P2/5N2/PPPPP1PP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4P3/5N2/PPPP1PPP/RNBQKB1R b KQkq - 0 1
opposite castling armageddon
Moderators: hgm, Rebel, chrisw
-
- Posts: 5960
- Joined: Sun Jan 10, 2010 6:15 am
- Location: Maryland USA
Re: opposite castling armageddon
Komodo rules!
-
- Posts: 2444
- Joined: Sat Sep 03, 2011 7:25 am
- Location: Berlin, Germany
- Full name: Stefan Pohl
Re: opposite castling armageddon
All you need is here:Guenther wrote: ↑Fri Jul 26, 2019 6:30 pmI did a quick test with CFish20190717 vs. itself and surprisingly the draw rate was still very high > 70% at a fast tc of 40/40''.OneTrickPony wrote: ↑Fri Jul 26, 2019 2:01 pm What about: white gets to make 2 first moves and gives draw odds.
Lc0 eval is similar to opposite castling armageddon proposed in OP but it's even simpler to explain.
used this set of positions:
https://www.sp-cc.de/drawkiller-openings.htm
With low draw-rates. And no need for new chess-rules, because all Drawkiller lines are starting at the normal classical chess starting position:
These are the two move-sequences, which create the „SALC“-like king- and rook-positions on the chessboard:
1. e3 d6 2. Nh3 Nc6 3. Bd3 Be6 4. O-O Qd7 5. Kh1 O-O-O 6. Re1 Kb8 7. Bf1 Ka8 8. Ng1 Qe8 9. Nf3 Bc8 10. Ng1 Nb8
1. d3 e6 2. Be3 Bd6 3. Nc3 Nh6 4. Qd2 O-O 5. O-O-O Kh8 6. Kb1 Re8 7. Ka1 Bf8 8. Qe1 Ng8 9. Bc1 Nf6 10. Nb1 Ng8
(and at the end of these lines, only some pawn-moves follow)...
Test results:
(asmFish 170426 vs. Komodo 10.4, 5'+3'' time-control, singlecore, no ponder, no endgame-bases, LittleBlitzerGUI, 1000 games each testrun(!) except Noomen Gambit-lines (only 246 positions, so 492 games were played) and Noomen TCEC Superfinal (only 100 positions, so 200 games were played))
Stockfish Framework standard 8 move openings: Score 60.3% – 39.7%, draws: 63.4%
FEOBOS v20 contempt 5 top 500 openings: Score 58.7% - 41.3%, draws: 64.1%
HERT 500 set: Score: 60.6% - 39.4%, draws: 60.4%
Noomen Gambit-Lines: Score 59.1% - 40.9%, draws: 59.3%
4 GM-moves short book: Score 60.5% - 39.5%, draws: 57.1%
Noomen TCEC Superfinal (Season 9+10): Score: 62.5% - 37.5%, draws: 50.0%
SALC V5 half-closed: Score 61.6% - 38.4%, draws: 49.2%
SALC V5 full-closed 500 positions: Score 66.5% - 33.5%, draws: 47.7%
NEW:
Drawkiller (normal set): Score: 65.3% - 34.7%, draws: 33.5%
Drawkiller (tournament set): Score: 65.3% - 34.7%, draws: 33.5%
(no mistake by me: the results of Drawkiller normal and tournament were exactly
the same after 1000 played games!)
Drawkiller (small 500 positions set): Score: 66.4% - 33.6%, draws 30.5%
NEW in V2.0:
Drawkiller balanced (small 500 positions set): Score: 69.3% - 30.7%, draws 35.2%
Drawkiller balanced: Score 69.4% - 30.6%, draws 36.4%
Drawkiller balanced big (15962 positions): Score 67.4% - 32.6%, draws 38.8%
NEW in V3.0:
Drawkiller EloZoom (small 500 positions set): Score: 72.0% - 28.0%, draws 34.6%
Drawkiller EloZoom: Score: 73.2% - 26.8%, draws 36.5%
Drawkiller EloZoom big (20043 positions): Score: 69.2% - 30.8%, draws 40.7%
As you can see, the Drawkiller openings are not just an improvement over my SALC openings, they are a breakthrough into another dimension! Never before any openings-set gave such low draw-rates without crunching the scores of the engines towards 50%, but instead pushing the scores away from 50%. The Drawkiller Normal- and Tournament sets nearly halve the draw-rate, compared to FEOBOS or the Stockfish Framework 8-move openings. And the small 500 set has more than a halved draw-rate compared to FEOBOS or the Stockfish Framework 8-move openings.
-
- Posts: 5960
- Joined: Sun Jan 10, 2010 6:15 am
- Location: Maryland USA
Re: opposite castling armageddon
You have achieved a big reduction in draw rate, but the game you are playing no longer resembles chess. Maybe half the game is about getting your king safe while getting your pieces developed well and securing space, and if you start the game with the kings already safely tucked away it's just a very different game. Also the topic here is how to eliminate draws so there is always a decisive result of each game, reducing the percentage doesn't accomplish that, although it is a desirable goal I agree.pohl4711 wrote: ↑Fri Jul 26, 2019 7:45 pmAll you need is here:Guenther wrote: ↑Fri Jul 26, 2019 6:30 pmI did a quick test with CFish20190717 vs. itself and surprisingly the draw rate was still very high > 70% at a fast tc of 40/40''.OneTrickPony wrote: ↑Fri Jul 26, 2019 2:01 pm What about: white gets to make 2 first moves and gives draw odds.
Lc0 eval is similar to opposite castling armageddon proposed in OP but it's even simpler to explain.
used this set of positions:
https://www.sp-cc.de/drawkiller-openings.htm
With low draw-rates. And no need for new chess-rules, because all Drawkiller lines are starting at the normal classical chess starting position:
These are the two move-sequences, which create the „SALC“-like king- and rook-positions on the chessboard:
1. e3 d6 2. Nh3 Nc6 3. Bd3 Be6 4. O-O Qd7 5. Kh1 O-O-O 6. Re1 Kb8 7. Bf1 Ka8 8. Ng1 Qe8 9. Nf3 Bc8 10. Ng1 Nb8
1. d3 e6 2. Be3 Bd6 3. Nc3 Nh6 4. Qd2 O-O 5. O-O-O Kh8 6. Kb1 Re8 7. Ka1 Bf8 8. Qe1 Ng8 9. Bc1 Nf6 10. Nb1 Ng8
(and at the end of these lines, only some pawn-moves follow)...
Test results:
(asmFish 170426 vs. Komodo 10.4, 5'+3'' time-control, singlecore, no ponder, no endgame-bases, LittleBlitzerGUI, 1000 games each testrun(!) except Noomen Gambit-lines (only 246 positions, so 492 games were played) and Noomen TCEC Superfinal (only 100 positions, so 200 games were played))
Stockfish Framework standard 8 move openings: Score 60.3% – 39.7%, draws: 63.4%
FEOBOS v20 contempt 5 top 500 openings: Score 58.7% - 41.3%, draws: 64.1%
HERT 500 set: Score: 60.6% - 39.4%, draws: 60.4%
Noomen Gambit-Lines: Score 59.1% - 40.9%, draws: 59.3%
4 GM-moves short book: Score 60.5% - 39.5%, draws: 57.1%
Noomen TCEC Superfinal (Season 9+10): Score: 62.5% - 37.5%, draws: 50.0%
SALC V5 half-closed: Score 61.6% - 38.4%, draws: 49.2%
SALC V5 full-closed 500 positions: Score 66.5% - 33.5%, draws: 47.7%
NEW:
Drawkiller (normal set): Score: 65.3% - 34.7%, draws: 33.5%
Drawkiller (tournament set): Score: 65.3% - 34.7%, draws: 33.5%
(no mistake by me: the results of Drawkiller normal and tournament were exactly
the same after 1000 played games!)
Drawkiller (small 500 positions set): Score: 66.4% - 33.6%, draws 30.5%
NEW in V2.0:
Drawkiller balanced (small 500 positions set): Score: 69.3% - 30.7%, draws 35.2%
Drawkiller balanced: Score 69.4% - 30.6%, draws 36.4%
Drawkiller balanced big (15962 positions): Score 67.4% - 32.6%, draws 38.8%
NEW in V3.0:
Drawkiller EloZoom (small 500 positions set): Score: 72.0% - 28.0%, draws 34.6%
Drawkiller EloZoom: Score: 73.2% - 26.8%, draws 36.5%
Drawkiller EloZoom big (20043 positions): Score: 69.2% - 30.8%, draws 40.7%
As you can see, the Drawkiller openings are not just an improvement over my SALC openings, they are a breakthrough into another dimension! Never before any openings-set gave such low draw-rates without crunching the scores of the engines towards 50%, but instead pushing the scores away from 50%. The Drawkiller Normal- and Tournament sets nearly halve the draw-rate, compared to FEOBOS or the Stockfish Framework 8-move openings. And the small 500 set has more than a halved draw-rate compared to FEOBOS or the Stockfish Framework 8-move openings.
Komodo rules!
-
- Posts: 4611
- Joined: Wed Oct 01, 2008 6:33 am
- Location: Regensburg, Germany
- Full name: Guenther Simon
Re: opposite castling armageddon
By far not enough games but also surprisingly interim result of 11 White wins and 13 draws after 24 games with another epd set:lkaufman wrote: ↑Fri Jul 26, 2019 7:27 pmYes, two moves isn't enough. But three is too many. You could rerun the same test with WTM each position to confirm this.Guenther wrote: ↑Fri Jul 26, 2019 6:30 pmI did a quick test with CFish20190717 vs. itself and surprisingly the draw rate was still very high > 70% at a fast tc of 40/40''.OneTrickPony wrote: ↑Fri Jul 26, 2019 2:01 pm What about: white gets to make 2 first moves and gives draw odds.
Lc0 eval is similar to opposite castling armageddon proposed in OP but it's even simpler to explain.
used this set of positions:
Code: Select all
rnbqkbnr/pppppppp/8/8/3PP3/8/PPP2PPP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3P4/5N2/PPP1PPPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2PP4/8/PP2PPPP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2P5/2N5/PP1PPPPP/R1BQKBNR b KQkq - 0 1 kbnr/pppppppp/8/8/2P5/6P1/PP1PPP1P/RNBQKBNR b KQkq - 0 1 kbnr/pppppppp/8/8/2P5/5N2/PP1PPPPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4PP2/8/PPPP2PP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4P3/2N5/PPPP1PPP/R1BQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/8/1P6/PBPPPPPP/RN1QKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/8/6P1/PPPPPPBP/RNBQK1NR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/5P2/5N2/PPPPP1PP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4P3/5N2/PPPP1PPP/RNBQKB1R b KQkq - 0 1
(only diff between CFish1 and CFish2 being contempt 9 vs. 10 - regrettably far too hot here for more games currently.)
Code: Select all
rnbqkbnr/pppppppp/8/8/2PPP3/8/PP3PPP/RNBQKBNR b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/2P5/2N3P1/PP1PPP1P/R1BQKBNR b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/3P4/5NP1/PPP1PP1P/RNBQKB1R b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/2B1P3/5N2/PPPP1PPP/RNBQK2R b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/4PP2/5N2/PPPP2PP/RNBQKB1R b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/4PP2/2N5/PPPP2PP/R1BQKBNR b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/2PP4/2N5/PP2PPPP/R1BQKBNR b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/3P4/1P3N2/P1P1PPPP/RNBQKB1R b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/3P4/1P3N2/P1P1PPPP/RNBQKB1R b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/3PP3/5N2/PPP2PPP/RNBQKB1R b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/3PP3/2N5/PPP2PPP/R1BQKBNR b KQkq - 0 1
rnbqkbnr/pppppppp/8/8/3P4/6P1/PPP1PPBP/RNBQK1NR b KQkq - 0 1
https://rwbc-chess.de
trollwatch:
Talkchess nowadays is a joke - it is full of trolls/idiots/people stuck in the pleistocene > 80% of the posts fall into this category...
trollwatch:
Talkchess nowadays is a joke - it is full of trolls/idiots/people stuck in the pleistocene > 80% of the posts fall into this category...
-
- Posts: 4611
- Joined: Wed Oct 01, 2008 6:33 am
- Location: Regensburg, Germany
- Full name: Guenther Simon
Re: opposite castling armageddon
Noticed that in my adhoc created epd for 3 moves by accident one position was twice...and this position produced 4 draws.Guenther wrote: ↑Fri Jul 26, 2019 8:23 pm
By far not enough games but also surprisingly interim result of 11 White wins and 13 draws after 24 games with another epd set:
(only diff between CFish1 and CFish2 being contempt 9 vs. 10 - regrettably far too hot here for more games currently.)
Code: Select all
rnbqkbnr/pppppppp/8/8/2PPP3/8/PP3PPP/RNBQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2P5/2N3P1/PP1PPP1P/R1BQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3P4/5NP1/PPP1PP1P/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2B1P3/5N2/PPPP1PPP/RNBQK2R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4PP2/5N2/PPPP2PP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/4PP2/2N5/PPPP2PP/R1BQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/2PP4/2N5/PP2PPPP/R1BQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3P4/1P3N2/P1P1PPPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3P4/1P3N2/P1P1PPPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3PP3/5N2/PPP2PPP/RNBQKB1R b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3PP3/2N5/PPP2PPP/R1BQKBNR b KQkq - 0 1 rnbqkbnr/pppppppp/8/8/3P4/6P1/PPP1PPBP/RNBQK1NR b KQkq - 0 1
https://rwbc-chess.de
trollwatch:
Talkchess nowadays is a joke - it is full of trolls/idiots/people stuck in the pleistocene > 80% of the posts fall into this category...
trollwatch:
Talkchess nowadays is a joke - it is full of trolls/idiots/people stuck in the pleistocene > 80% of the posts fall into this category...
-
- Posts: 937
- Joined: Fri Mar 10, 2006 4:29 pm
- Location: Germany
Re: opposite castling armageddon
Here are two games played by a modified Stockfish, time control was 30"+0.3".lkaufman wrote: ↑Fri Jul 26, 2019 7:03 am I have wondered what would be the simplest rule change to chess that would make it a two-result game (win or loss) while still being roughly fair to both players. In the real chess world this is sometimes done by giving White more time and Black draw odds, but with a few exceptions this has been done only at ten minute or faster time limits. Let's say we won't use time in the rules, equal time is assumed. Here is what I think might be an original, simple, and fair enough solution.
White is not allowed to castle long, Black is not allowed to castle short, Black wins draws. That's it. It is a subset of normal chess; if you stipulate the starting sequence 1.Na3 Nh6 2.Rb1 Rg8 3.Ra1 Rh8 4.Nb1 Ng8 you get the above castling status. Since castling short is easier to accomplish than castling long and doesn't require an extra move to "finish" the castle (Kb8) White's advantage is obviously larger than normal, despite the symmetry of the rule, and the fact that same side castling never happens makes the draw odds less significant. But it's far from clear which side has the better chances or the theoretically won position. Most people would rather play White, because it's more "fun", but whether White would score more than 50% in either human vs human or engine vs engine play is not obvious. Recent strong versions of Lc0 give White about 68-70% win exp. with draws counting as a half, which is close to the point where White would win half the games outright. Stockfish and Komodo give White a bit more of an advantage than what I would normally call the line between a draw and a win (about .7 for Komodo, about 1 for SF). I had ten different Lc0 networks play it out using the "Shootout" feature on Fritz, at 2' + 1" on rtx 2080, and White won four, drew six. My hunch is that White will come out slightly ahead in human GM play, perhaps about even or a bit behind in engine play, but of course it's very hard to predict, and ten games with similar engines means little.
So who would you bet on, White or Black. First case top human GMs playing, second case top engines. And who benefits from longer time controls, White or Black? Is it roughly fair? It doesn't have to be perfectly fair, as players alternate colors and chess isn't at all fair in that sense now.
Note: it recognizes draws by repetition, 50-move rule und stalemates as wins for Black,
but not draws by insufficient material and no draw endgame rules have been changed.
[pgn][Event "?"] [Site "?"] [Date "2019.07.26"] [Round "1"] [White "SF-Armageddon1"] [Black "SF-Armageddon2"] [Result "0-1"] [ECO "D00"] [GameDuration "00:02:22"] [GameEndTime "2019-07-26T19:57:18.717 CEST"] [GameStartTime "2019-07-26T19:54:56.303 CEST"] [Opening "Queen's pawn game"] [PlyCount "277"] [Termination "adjudication"] [TimeControl "30+0.3"] 1. d4 {+1.15/19 2.1s} d5 {-1.30/17 1.5s} 2. e3 {+1.07/17 0.47s} Nc6 {-1.29/16 0.32s} 3. Nf3 {+1.06/17 0.82s} Bg4 {-1.21/17 0.33s} 4. Be2 {+1.21/16 0.22s} e6 {-1.18/19 3.9s} 5. c4 {+1.13/19 2.7s} Nf6 {-1.08/18 0.67s} 6. O-O {+1.15/16 0.77s} h5 {-1.08/18 0.62s} 7. Nbd2 {+1.07/18 1.6s} Be7 {-0.99/17 0.45s} 8. a3 {+1.11/18 1.0s} Kf8 {-1.12/21 3.3s} 9. b4 {+1.06/18 0.35s} a6 {-1.15/19 0.29s} 10. Bb2 {+1.04/18 0.42s} g6 {-1.21/19 0.57s} 11. h3 {+1.25/17 0.41s} Bf5 {-1.47/19 1.2s} 12. Nh4 {+1.21/18 0.46s} Bd6 {-1.23/20 1.4s} 13. Rc1 {+1.25/17 0.42s} Kg7 {-1.05/16 0.28s} 14. Qb3 {+1.21/17 0.58s} Rb8 {-1.07/18 0.56s} 15. Rfd1 {+1.21/19 1.9s} Na7 {-1.05/18 1.3s} 16. a4 {+1.31/19 2.4s} c6 {-1.09/16 0.61s} 17. Ra1 {+1.30/17 0.66s} Bc7 {-1.23/18 1.6s} 18. b5 {+0.89/19 1.5s} axb5 {-0.89/18 0.27s} 19. axb5 {+1.02/18 0.37s} Nc8 {-1.09/19 1.4s} 20. Nxf5+ {+1.07/18 0.70s} gxf5 {-0.83/17 0.32s} 21. Rdc1 {+1.02/20 2.1s} cxb5 {-0.82/20 2.1s} 22. cxd5 {+0.93/18 0.41s} Nxd5 {-1.01/19 0.63s} 23. Bf3 {+1.26/20 1.2s} b4 {-1.19/20 0.84s} 24. Bxd5 {+1.42/18 0.31s} exd5 {-1.15/21 1.0s} 25. Qxb4 {+1.49/21 1.8s} Rh6 {-1.22/20 0.96s} 26. Qb3 {+1.34/19 2.0s} Rb6 {-1.36/19 0.67s} 27. Qc2 {+1.33/19 0.36s} f4 {-1.31/18 0.31s} 28. e4 {+1.70/18 0.92s} Ne7 {-1.12/19 0.84s} 29. exd5 {+1.70/19 0.89s} Nxd5 {-0.97/19 0.93s} 30. Nc4 {+1.66/19 0.47s} Rb5 {-1.17/21 1.7s} 31. Qf5 {+1.60/18 0.60s} Qf6 {-0.95/20 0.29s} 32. Qxh5 {+1.65/19 0.41s} Rh8 {-1.04/22 0.81s} 33. Qf3 {+1.71/20 0.77s} Qf5 {-1.14/22 0.60s} 34. Ba3 {+1.20/23 2.5s} Qh5 {-1.29/21 0.97s} 35. Qxh5 {+0.96/22 1.6s} Rxh5 {-1.22/21 0.77s} 36. Nd2 {+1.35/22 1.6s} Ra5 {-1.25/20 2.2s} 37. Kf1 {+1.37/17 0.21s} Kg6 {-1.49/19 1.4s} 38. Bb2 {+1.27/20 2.0s} Rb5 {-1.32/19 0.48s} 39. Rab1 {+1.34/16 0.14s} Bd6 {-1.16/16 0.15s} 40. Ke2 {+1.38/17 0.25s} Be7 {-1.34/17 0.56s} 41. Kf3 {+1.30/19 1.2s} Rh8 {-1.12/18 0.24s} 42. Ba1 {+1.42/17 0.14s} Rb4 {-1.47/23 1.8s} 43. Ke4 {+1.07/20 0.80s} Rd8 {-1.11/16 0.15s} 44. Rxb4 {+1.08/16 0.31s} Nxb4 {-1.06/19 0.38s} 45. Re1 {+1.08/15 0.13s} b5 {-0.69/16 0.36s} 46. Bc3 {+1.18/17 0.26s} Rc8 {-0.64/15 0.15s} 47. Bxb4 {+1.24/18 0.17s} Bxb4 {-1.12/21 1.1s} 48. Rd1 {+1.33/16 0.14s} Rc2 {-1.21/17 0.27s} 49. Nf3 {+1.28/17 0.25s} Rxf2 {-1.32/17 0.40s} 50. Ne5+ {+1.49/16 0.15s} Kg5 {-1.27/19 0.57s} 51. Rb1 {+1.73/16 0.50s} f5+ {-1.07/17 0.24s} 52. Kd5 {+1.48/17 0.33s} Bf8 {-1.23/18 0.35s} 53. Rxb5 {+1.54/18 0.45s} Rxg2 {-1.04/17 0.16s} 54. Ke6 {+1.06/17 0.53s} Kh4 {-1.13/16 0.20s} 55. Kxf5 {+1.39/16 0.13s} Kxh3 {-1.07/15 0.15s} 56. Kxf4 {+1.27/16 0.42s} Rf2+ {-1.28/16 0.43s} 57. Ke4 {+1.46/15 0.24s} Be7 {-1.27/16 0.37s} 58. Rb7 {+1.70/15 0.18s} Bf6 {-1.44/17 0.52s} 59. Nd3 {+1.67/18 0.29s} Ra2 {-1.23/17 0.31s} 60. Kf3 {+1.19/17 0.39s} Kh4 {-1.09/14 0.12s} 61. Kf4 {+1.30/17 0.19s} Bg5+ {-0.97/16 0.18s} 62. Kf5 {+1.33/18 0.63s} Ra5+ {-1.05/17 0.37s} 63. Ke6 {+1.43/17 0.17s} Ra8 {-1.33/18 0.52s} 64. Rb1 {+1.17/17 0.57s} Rd8 {-0.95/14 0.14s} 65. d5 {+1.27/16 0.30s} Re8+ {-1.21/16 0.46s} 66. Kd6 {+0.92/18 0.29s} Be7+ {-1.33/17 0.30s} 67. Kd7 {+1.46/14 0.13s} Rd8+ {-1.46/14 0.23s} 68. Ke6 {+1.15/16 0.39s} Kg3 {-1.24/15 0.36s} 69. Ke5 {+1.23/15 0.41s} Re8 {-1.27/14 0.30s} 70. Nf4 {+1.53/16 0.17s} Kf2 {-1.62/14 0.30s} 71. Ne6 {+1.30/16 0.43s} Ra8 {-0.98/15 0.26s} 72. Nd4 {+1.36/14 0.19s} Ra6 {-0.84/14 0.20s} 73. Rb3 {+1.10/15 0.41s} Bd6+ {-0.85/14 0.21s} 74. Kf5 {+0.98/15 0.30s} Bc5 {-0.85/15 0.26s} 75. Nc6 {+0.87/16 0.30s} Ra3 {-0.90/16 0.46s} 76. Rb2+ {+0.93/14 0.13s} Ke3 {-0.84/14 0.15s} 77. Rc2 {+0.82/16 0.28s} Bf8 {-0.82/15 0.15s} 78. Ke6 {+0.81/16 0.15s} Ra6 {-0.84/17 0.43s} 79. Rc4 {+0.77/18 0.45s} Rb6 {-0.79/15 0.14s} 80. d6 {+0.70/14 0.15s} Bxd6 {-0.78/17 0.39s} 81. Kxd6 {+0.72/16 0.59s} Rb5 {-0.80/15 0.21s} 82. Rh4 {+0.69/16 0.34s} Rg5 {-0.75/15 0.54s} 83. Ne7 {+0.70/14 0.30s} Ra5 {-0.72/15 0.40s} 84. Nd5+ {+0.64/13 0.30s} Kf3 {-0.73/13 0.21s} 85. Ke5 {+0.76/12 0.30s} Ra8 {-0.65/12 0.17s} 86. Kf5 {+0.71/14 0.27s} Rf8+ {-0.71/14 0.58s} 87. Nf6 {+0.65/14 0.29s} Ke3 {-0.62/14 0.32s} 88. Ke5 {+0.70/12 0.099s} Kd3 {-0.65/13 0.10s} 89. Rh3+ {+0.66/14 0.28s} Kc4 {-0.66/14 0.14s} 90. Rh1 {+0.64/12 0.19s} Kd3 {-0.69/13 0.34s} 91. Nd7 {+0.61/15 0.52s} Re8+ {-0.63/12 0.23s} 92. Kd5 {+0.63/15 0.32s} Rd8 {-0.70/14 0.29s} 93. Rh3+ {+0.58/14 0.35s} Ke2 {-0.62/14 0.33s} 94. Ke6 {+0.56/14 0.39s} Re8+ {-0.65/13 0.41s} 95. Kf5 {+0.74/12 0.075s} Ra8 {-0.69/13 0.23s} 96. Ke4 {+0.58/13 0.37s} Kf2 {-0.64/13 0.60s} 97. Rh6 {+0.73/13 0.45s} Ra4+ {-0.57/12 0.27s} 98. Kd5 {+0.55/14 0.30s} Ra8 {-0.64/12 0.38s} 99. Nc5 {+0.76/12 0.077s} Kf3 {-0.79/13 0.30s} 100. Ke5 {+0.63/14 0.52s} Ra5 {-0.78/13 0.30s} 101. Kd5 {+0.68/14 0.31s} Ra8 {-0.66/14 0.22s} 102. Rh3+ {+0.73/13 0.30s} Kg4 {-0.61/12 0.28s} 103. Rh1 {+0.58/14 0.30s} Rd8+ {-0.53/12 0.24s} 104. Ke5 {+0.74/14 0.076s} Kf3 {-0.64/14 0.46s} 105. Rh3+ {+0.55/15 0.52s} Kg4 {-0.68/13 0.30s} 106. Rh1 {+0.58/14 0.10s} Ra8 {-0.76/14 0.30s} 107. Rf1 {+0.58/14 0.46s} Ra5 {-0.55/14 0.30s} 108. Kd5 {+0.57/16 0.35s} Ra8 {-0.65/13 0.30s} 109. Ne6 {+0.75/13 0.17s} Ra5+ {-0.87/12 0.30s} 110. Ke4 {+0.76/15 0.43s} Ra4+ {-0.63/11 0.18s} 111. Ke3 {+0.72/14 0.30s} Ra3+ {-0.46/13 0.42s} 112. Ke2 {+0.68/14 0.30s} Ra6 {-0.13/11 0.24s} 113. Rf4+ {+0.72/13 0.30s} Kg3 {-0.15/12 0.17s} 114. Rf6 {+0.52/14 0.30s} Kg4 {-0.33/14 0.48s} 115. Rf4+ {+0.56/15 0.30s} Kg3 {-0.13/14 0.26s} 116. Rf6 {+0.70/14 0.30s} Kg4 {-0.69/13 0.34s} 117. Kd3 {+0.67/14 0.30s} Ra4 {-0.59/12 0.27s} 118. Rf8 {+0.71/12 0.30s} Ra6 {-0.13/11 0.24s} 119. Nd4 {+0.52/12 0.30s} Kg5 {-0.55/12 0.39s} 120. Nf3+ {+0.71/14 0.30s} Kg4 {-0.13/11 0.25s} 121. Ne5+ {+0.48/15 0.30s} Kg5 {-0.13/11 0.19s} 122. Rf1 {+0.46/14 0.30s} Ra5 {-0.41/13 0.46s} 123. Nc4 {+0.22/15 0.30s} Ra8 {-0.13/12 0.17s} 124. Ke4 {+0.03/13 0.30s} Rc8 {-0.03/13 0.43s} 125. Nd6 {+0.03/13 0.30s} Ra8 {+0.13/12 0.17s} 126. Nc4 {-0.23/13 0.30s} Kg6 {+0.48/13 0.13s} 127. Rf7 {-4.79/12 0.30s} Kxf7 {+0.46/12 0.18s} 128. Nb2 {-0.42/15 0.28s} Re8+ {+5.17/18 0.34s} 129. Kf3 {-0.56/16 0.32s} Ke6 {+5.17/14 0.098s} 130. Nd3 {-1.39/16 0.30s} Kf5 {+5.36/15 0.18s} 131. Nb4 {-0.79/16 0.27s} Rc8 {+1.16/19 0.82s} 132. Nd5 {-0.61/20 0.33s} Ke5 {+5.15/20 0.27s} 133. Ne7 {-52.80/21 0.30s} Re8 {+53.03/20 0.12s} 134. Ng6+ {-5.36/15 0.074s} Kf5 {+53.46/21 0.39s} 135. Nf4 {-6.01/18 0.52s} Ra8 {+53.61/19 0.22s} 136. Nh5 {-50.30/20 0.31s} Ra3+ {+53.70/26 0.25s} 137. Kg2 {-53.82/24 0.30s} Ke5 {+147.58/24 0.32s} 138. Kf2 {-53.51/24 0.25s} Rc3 {+55.55/27 0.64s} 139. Ng3 {-53.20/19 0.20s, Black wins by adjudication} 0-1 [Event "?"] [Site "?"] [Date "2019.07.26"] [Round "1"] [White "SF-Armageddon2"] [Black "SF-Armageddon1"] [Result "1-0"] [ECO "D00"] [GameDuration "00:01:49"] [GameEndTime "2019-07-26T19:56:45.969 CEST"] [GameStartTime "2019-07-26T19:54:56.306 CEST"] [Opening "Queen's pawn game"] [PlyCount "170"] [Termination "adjudication"] [TimeControl "30+0.3"] 1. d4 {+1.15/19 2.1s} d5 {-1.30/17 1.5s} 2. e3 {+1.07/17 0.47s} Nc6 {-1.29/16 0.32s} 3. Nf3 {+1.06/17 0.82s} Bg4 {-1.21/17 0.33s} 4. Be2 {+1.21/16 0.22s} e6 {-1.18/19 3.9s} 5. c4 {+1.13/19 2.7s} Nf6 {-1.08/18 0.67s} 6. O-O {+1.15/16 0.76s} h5 {-1.08/18 0.62s} 7. Nbd2 {+1.07/18 1.6s} Be7 {-0.99/17 0.45s} 8. a3 {+1.11/18 1.0s} Kf8 {-1.12/21 3.3s} 9. b4 {+1.06/18 0.35s} a6 {-1.15/19 0.29s} 10. Bb2 {+1.04/18 0.41s} g6 {-1.21/19 0.57s} 11. h3 {+1.25/17 0.40s} Bf5 {-1.47/19 1.2s} 12. Nh4 {+1.21/18 0.46s} Bd6 {-1.23/20 1.4s} 13. Rc1 {+1.25/17 0.42s} Kg7 {-1.05/16 0.28s} 14. Qb3 {+1.21/17 0.58s} Rb8 {-1.07/18 0.57s} 15. Rfd1 {+1.21/19 1.8s} Na7 {-1.05/18 1.3s} 16. a4 {+1.31/19 2.4s} c6 {-1.09/16 0.61s} 17. Ra1 {+1.30/17 0.66s} Bc7 {-1.23/18 1.6s} 18. b5 {+0.89/19 1.5s} axb5 {-0.89/18 0.27s} 19. axb5 {+1.02/18 0.37s} Nc8 {-1.09/19 1.4s} 20. Nxf5+ {+1.07/18 0.70s} gxf5 {-0.83/17 0.32s} 21. Rdc1 {+1.02/20 2.1s} cxb5 {-0.82/20 2.1s} 22. cxd5 {+0.93/18 0.40s} Nxd5 {-1.01/19 0.63s} 23. Bf3 {+1.26/20 1.1s} b4 {-1.19/20 0.84s} 24. Bxd5 {+1.42/18 0.30s} exd5 {-1.15/21 1.0s} 25. Qxb4 {+1.49/21 1.8s} Rh6 {-1.22/20 0.96s} 26. Qb3 {+1.34/19 1.9s} Rb6 {-1.36/19 0.67s} 27. Qc2 {+1.33/19 0.35s} f4 {-1.31/18 0.31s} 28. e4 {+1.70/18 0.92s} Ne7 {-1.12/19 0.83s} 29. exd5 {+1.70/19 0.88s} Nxd5 {-0.97/19 0.93s} 30. Nc4 {+1.66/19 0.47s} Rb5 {-1.17/21 1.7s} 31. Qf5 {+1.60/18 0.60s} Qf6 {-0.95/20 0.28s} 32. Qxh5 {+1.65/19 0.41s} Rh8 {-1.04/22 0.81s} 33. Qf3 {+1.71/20 0.77s} Qf5 {-1.14/22 0.61s} 34. Ba3 {+1.20/23 2.5s} Qh5 {-1.29/21 0.97s} 35. Qxh5 {+0.96/22 1.6s} Rxh5 {-1.22/21 0.77s} 36. Nd2 {+1.35/22 1.6s} Ra5 {-1.25/20 2.2s} 37. Kf1 {+1.37/17 0.21s} Kg6 {-1.49/19 1.4s} 38. Bb2 {+1.37/20 2.0s} Rb5 {-1.32/19 0.48s} 39. Rab1 {+1.27/17 0.32s} Bd6 {-1.16/16 0.15s} 40. Ke2 {+1.30/17 0.24s} Be7 {-1.34/17 0.56s} 41. Ba1 {+1.31/16 0.18s} Rxb1 {-1.16/17 0.24s} 42. Rxb1 {+1.38/17 0.17s} b5 {-1.63/18 0.73s} 43. Nf3 {+1.45/18 0.36s} f6 {-1.48/17 0.21s} 44. Kd3 {+1.63/17 0.21s} Bb4 {-1.53/19 0.74s} 45. Bb2 {+1.64/17 0.19s} Kf5 {-1.61/18 0.55s} 46. Bc1 {+1.68/18 0.21s} Ke6 {-1.57/18 0.15s} 47. Bd2 {+1.50/19 0.45s} Bxd2 {-1.39/17 0.18s} 48. Kxd2 {+1.25/19 0.70s} b4 {-1.49/18 0.46s} 49. Kd3 {+1.22/18 0.24s} Rh8 {-1.28/18 0.31s} 50. Re1+ {+1.22/17 0.44s} Kd6 {-1.23/18 0.39s} 51. Ra1 {+1.73/17 0.21s} Rc8 {-1.15/18 1.1s} 52. Ra6+ {+1.60/16 0.42s} Kd7 {-1.24/18 0.62s} 53. Ke4 {+1.77/17 0.41s} Nc3+ {-0.95/16 0.27s} 54. Kf5 {+1.38/16 0.49s} Kc7 {-1.02/16 0.30s} 55. h4 {+1.23/17 0.48s} b3 {-0.84/14 0.14s} 56. Nd2 {+1.38/16 0.18s} b2 {-0.85/15 0.24s} 57. Ra5 {+1.84/17 0.25s} Kd6 {-0.82/15 0.21s} 58. h5 {+1.58/19 0.40s} f3 {-1.70/19 0.85s} 59. gxf3 {+1.68/19 0.16s} b1=Q+ {-1.70/18 0.14s} 60. Nxb1 {+2.06/19 0.24s} Nxb1 {-2.38/21 0.46s} 61. h6 {+2.30/17 0.15s} Nc3 {-2.24/21 0.27s} 62. h7 {+2.43/17 0.25s} Nd5 {-2.24/18 0.25s} 63. Ra6+ {+2.45/17 0.16s} Ke7 {-2.33/19 0.16s} 64. Ra7+ {+2.69/19 0.38s} Kd6 {-3.11/19 0.49s} 65. Kg6 {+2.74/18 0.15s} f5 {-2.46/19 0.36s} 66. Ra6+ {+2.35/22 1.2s} Ke7 {-1.75/18 0.096s} 67. Ra7+ {+2.76/18 0.11s} Kd6 {-2.36/22 0.39s} 68. Ra1 {+3.06/19 0.17s} Nf4+ {-2.84/18 0.55s} 69. Kxf5 {+2.76/22 0.48s} Rh8 {-3.02/20 0.32s} 70. Kxf4 {+3.15/19 0.15s} Rxh7 {-2.66/18 0.10s} 71. Ke4 {+3.25/22 0.34s} Re7+ {-3.03/21 0.49s} 72. Kd3 {+3.20/23 0.56s} Rb7 {-2.72/19 0.21s} 73. Ra6+ {+3.40/21 0.39s} Kd5 {-3.40/21 0.39s} 74. Ra5+ {+3.49/20 0.16s} Kd6 {-3.44/21 0.26s} 75. f4 {+3.55/21 0.17s} Rb3+ {-3.46/20 0.11s} 76. Ke4 {+3.55/21 0.24s} Rb2 {-4.07/23 0.52s} 77. f3 {+3.87/20 0.17s} Ke7 {-5.16/20 0.31s} 78. Re5+ {+4.76/19 0.31s} Kf7 {-5.17/21 0.10s} 79. d5 {+6.12/22 0.63s} Rb4+ {-5.17/17 0.13s} 80. Ke3 {+6.61/20 0.11s} Rb1 {-5.90/22 0.61s} 81. Kd4 {+6.75/23 0.15s} Rd1+ {-6.75/22 0.35s} 82. Kc5 {+7.31/23 0.51s} Rc1+ {-7.08/21 0.30s} 83. Kb6 {+7.30/27 0.21s} Rd1 {-7.34/25 0.30s} 84. Kc7 {+7.31/27 0.23s} Rc1+ {-7.78/24 0.30s} 85. Kd7 {+7.46/27 0.27s} Kf6 {-10.36/21 0.30s, White wins by adjudication} 1-0[/pgn]
Jörg Oster
-
- Posts: 2444
- Joined: Sat Sep 03, 2011 7:25 am
- Location: Berlin, Germany
- Full name: Stefan Pohl
Re: opposite castling armageddon
The low-draw rates of Drawkiller prove, that you are completely wrong: moving the kings to opposite side of the board does NOT make them safe. Otherwise the draw-rates must be much higher (mention, that all Drawkiller endpositions have a balanced Komodo-eval). So classical openings make kings save (perhaps), but definitly not Drawkiller.lkaufman wrote: ↑Fri Jul 26, 2019 8:21 pm You have achieved a big reduction in draw rate, but the game you are playing no longer resembles chess. Maybe half the game is about getting your king safe while getting your pieces developed well and securing space, and if you start the game with the kings already safely tucked away it's just a very different game.
The pieces are NOT getting “developed well“ with Drawkiller: 11 of 16 non-pawn pieces are on the same position as in the classical chess starting position and all 16 non-pawn pieces are on the both baselines (1 and 8). So classical openings develop pieces (perhaps), but definitly not Drawkiller.
-
- Posts: 5960
- Joined: Sun Jan 10, 2010 6:15 am
- Location: Maryland USA
Re: opposite castling armageddon
Yes, I should have said that your start positions make the kings about as safe as they can be given the opposite-side castling stipulation. My point is that part of chess is deciding where to place the king and how to develop in such a way as to make it possible to get the king to whichever corner is desired. Your start positions just skip over this very fundamental part of chess. Now I don't dispute that your drawkiller set is useful for testing engines, although it won't test their ability to play the opening properly. I suppose for people who only use engines starting around move 15 or so when the opening is pretty much finished, your set is extremely valuable. But I don't think it is a serious candidate for human use, or for testing how engines play the openings. Too much of the game has already been set in stone for that purpose. I much prefer chess960 for human use, as all the decisions of how to develop and safeguard the king remain to be made. But chess960 is only useful for engines to the extent that it becomes accepted by human players.pohl4711 wrote: ↑Sat Jul 27, 2019 4:27 amThe low-draw rates of Drawkiller prove, that you are completely wrong: moving the kings to opposite side of the board does NOT make them safe. Otherwise the draw-rates must be much higher (mention, that all Drawkiller endpositions have a balanced Komodo-eval). So classical openings make kings save (perhaps), but definitly not Drawkiller.lkaufman wrote: ↑Fri Jul 26, 2019 8:21 pm You have achieved a big reduction in draw rate, but the game you are playing no longer resembles chess. Maybe half the game is about getting your king safe while getting your pieces developed well and securing space, and if you start the game with the kings already safely tucked away it's just a very different game.
The pieces are NOT getting “developed well“ with Drawkiller: 11 of 16 non-pawn pieces are on the same position as in the classical chess starting position and all 16 non-pawn pieces are on the both baselines (1 and 8). So classical openings develop pieces (perhaps), but definitly not Drawkiller.
Komodo rules!
-
- Posts: 4833
- Joined: Sun Aug 10, 2008 3:15 pm
- Location: Philippines
Re: opposite castling armageddon
Implemented Armageddon in Deuterium (around 3000 on ccrl 40/4), test it at dissimilar TC, white has 5 minutes and black has 4 minutes. It used a 4-ply noomen opening suite run in cutechess-cli randomly.lkaufman wrote: ↑Fri Jul 26, 2019 7:03 am I have wondered what would be the simplest rule change to chess that would make it a two-result game (win or loss) while still being roughly fair to both players. In the real chess world this is sometimes done by giving White more time and Black draw odds, but with a few exceptions this has been done only at ten minute or faster time limits. Let's say we won't use time in the rules, equal time is assumed. Here is what I think might be an original, simple, and fair enough solution.
White is not allowed to castle long, Black is not allowed to castle short, Black wins draws. That's it. It is a subset of normal chess; if you stipulate the starting sequence 1.Na3 Nh6 2.Rb1 Rg8 3.Ra1 Rh8 4.Nb1 Ng8 you get the above castling status. Since castling short is easier to accomplish than castling long and doesn't require an extra move to "finish" the castle (Kb8) White's advantage is obviously larger than normal, despite the symmetry of the rule, and the fact that same side castling never happens makes the draw odds less significant. But it's far from clear which side has the better chances or the theoretically won position. Most people would rather play White, because it's more "fun", but whether White would score more than 50% in either human vs human or engine vs engine play is not obvious. Recent strong versions of Lc0 give White about 68-70% win exp. with draws counting as a half, which is close to the point where White would win half the games outright. Stockfish and Komodo give White a bit more of an advantage than what I would normally call the line between a draw and a win (about .7 for Komodo, about 1 for SF). I had ten different Lc0 networks play it out using the "Shootout" feature on Fritz, at 2' + 1" on rtx 2080, and White won four, drew six. My hunch is that White will come out slightly ahead in human GM play, perhaps about even or a bit behind in engine play, but of course it's very hard to predict, and ten games with similar engines means little.
So who would you bet on, White or Black. First case top human GMs playing, second case top engines. And who benefits from longer time controls, White or Black? Is it roughly fair? It doesn't have to be perfectly fair, as players alternate colors and chess isn't at all fair in that sense now.
Result after 50 games.
Code: Select all
GameVariant: armageddon
WhiteTC: 300, BlackTC: 240
Engine Total Win Loss Draw Score Score%
Deuterium v2019.2.37.62 armageddon_white 50 17 6 27 17 34.0
Deuterium v2019.2.37.62 armageddon_black 50 6 17 27 33 66.0
Games with draw results were already corrected see Termination tag in the game.
Also implemented a variant with your idea and call it lkaufman. TC is the same as in armageddon that is white has 5 minutes and black has 4 minutes. I would like to see the impact of the castling this is why I use dissimilar TC, similar to armageddon test. Also used the 4-ply noomen test suite.
Result after 50 games.
Code: Select all
GameVariant: lkaufman
WhiteTC: 300, BlackTC: 240
Engine Total Win Loss Draw Score Score%
Deuterium v2019.2.37.63 Lkaufman_white 50 21 10 19 21 42.0
Deuterium v2019.2.37.63 Lkaufman_black 50 10 21 19 29 58.0
So there is improvement on the white performance (34% to 42%) from armageddon to lkaufman.
-
- Posts: 2444
- Joined: Sat Sep 03, 2011 7:25 am
- Location: Berlin, Germany
- Full name: Stefan Pohl
Re: opposite castling armageddon
I find the idea interesting. So, I took the Stockfish Framework 8move-openings v3 (34700 games) and added the line 1.Na3 Nh6 2.Rb1 Rg8 3.Ra1 Rh8 4.Nb1 Ng8 in the front of each opening and deleted all lines, which included illegal move sequences, now (short castlings of Black for example).lkaufman wrote: ↑Fri Jul 26, 2019 7:03 am I have wondered what would be the simplest rule change to chess that would make it a two-result game (win or loss) while still being roughly fair to both players. In the real chess world this is sometimes done by giving White more time and Black draw odds, but with a few exceptions this has been done only at ten minute or faster time limits. Let's say we won't use time in the rules, equal time is assumed. Here is what I think might be an original, simple, and fair enough solution.
White is not allowed to castle long, Black is not allowed to castle short, Black wins draws. That's it. It is a subset of normal chess; if you stipulate the starting sequence 1.Na3 Nh6 2.Rb1 Rg8 3.Ra1 Rh8 4.Nb1 Ng8 you get the above castling status. Since castling short is easier to accomplish than castling long and doesn't require an extra move to "finish" the castle (Kb8) White's advantage is obviously larger than normal, despite the symmetry of the rule, and the fact that same side castling never happens makes the draw odds less significant. But it's far from clear which side has the better chances or the theoretically won position. Most people would rather play White, because it's more "fun", but whether White would score more than 50% in either human vs human or engine vs engine play is not obvious. Recent strong versions of Lc0 give White about 68-70% win exp. with draws counting as a half, which is close to the point where White would win half the games outright. Stockfish and Komodo give White a bit more of an advantage than what I would normally call the line between a draw and a win (about .7 for Komodo, about 1 for SF). I had ten different Lc0 networks play it out using the "Shootout" feature on Fritz, at 2' + 1" on rtx 2080, and White won four, drew six. My hunch is that White will come out slightly ahead in human GM play, perhaps about even or a bit behind in engine play, but of course it's very hard to predict, and ten games with similar engines means little.
So who would you bet on, White or Black. First case top human GMs playing, second case top engines. And who benefits from longer time controls, White or Black? Is it roughly fair? It doesn't have to be perfectly fair, as players alternate colors and chess isn't at all fair in that sense now.
20616 opening lines remaining.
I added a smaller set with only 4 moves (8 plies) played (plus the Armageddon line). Unique endpositions only:
3614 opening lines remaining.
I added a smaller set with only 2.5 moves (5 plies) played (plus the Armageddon line). Unique endpositions only:
871 opening lines remaining.
You find the PGN and the EPD-files in the folder. You can use them for engine-play. When finished, just set all drawn-games to a win for Black - done!
Download on my website or right here:
https://www.sp-cc.de/files/lk_armageddon.zip
Stefan (SPCC)