The 3 first ones are new records if we omit the 2 tricky version of Eman and BlueFish who are very weak in play.
These 3 engines combined, find 193 (!!!) solutions !
If we add Crystal-2020-06-29, they find 199 solutions !
To solved 11 remaining positions, you need to add Sting-SF (more specialized in fortress detection and positions without progress). A winning pack of 5 to not overlook tricky tactics and singular shots.
It's still 3 positions not found with this very clever pack :
1rb1qrk1/2b2pp1/p3pBn1/3pP1Pp/1ppP4/2P1QN2/PP3P1P/R2BR1K1 w - - bm Nh4; id "Hard-Talkchess-2020.023" ;
2bqrr1k/p5b1/1p1p2pp/nPpBp3/P1P1N2P/3PN1P1/R4P1K/3Q1R2 w - - bm Nc3; id "Hard-Talkchess-2020.038" ;
r2r2k1/pqp1bppp/1pn1pn2/8/2NP1B2/2N1P1P1/PPQ2P1P/R4RK1 b - - bm Rxd4; id "Hard-Talkchess-2020.179" ;
Some engines that will be tested in the following days : Crystal_x64_110920, Cfish NUMA 261020 and Sting-sf-25.
How to interpret the table? I understand there are 213 positions in this test.
Each line is a position of the test. The number is the second needed to find the solution. If there's no number, the solution is not found.
When you go down after line #213, you will see the average time and the number of solutions found.
The 3 first ones are new records if we omit the 2 tricky version of Eman and BlueFish who are very weak in play.
These 3 engines combined, find 193 (!!!) solutions !
If we add Crystal-2020-06-29, they find 199 solutions !
To solved 11 remaining positions, you need to add Sting-SF (more specialized in fortress detection and positions without progress). A winning pack of 5 to not overlook tricky tactics and singular shots.
It's still 3 positions not found with this very clever pack :
1rb1qrk1/2b2pp1/p3pBn1/3pP1Pp/1ppP4/2P1QN2/PP3P1P/R2BR1K1 w - - bm Nh4; id "Hard-Talkchess-2020.023" ;
2bqrr1k/p5b1/1p1p2pp/nPpBp3/P1P1N2P/3PN1P1/R4P1K/3Q1R2 w - - bm Nc3; id "Hard-Talkchess-2020.038" ;
r2r2k1/pqp1bppp/1pn1pn2/8/2NP1B2/2N1P1P1/PPQ2P1P/R4RK1 b - - bm Rxd4; id "Hard-Talkchess-2020.179" ;
Some engines that will be tested in the following days : Crystal_x64_110920, Cfish NUMA 261020 and Sting-sf-25.
How to interpret the table? I understand there are 213 positions in this test.
Each line is a position of the test. The number is the second needed to find the solution. If there's no number, the solution is not found.
When you go down after line #213, you will see the average time and the number of solutions found.
Thanks, nice table it is detailed. I plan two things, one run this test with Lc0 (on my current gtx gpu) at lower movetime not 30 minutes per position just to see how it performs and second find the top 100 easier positions. Criteria for easy could be the high number of engines where the position is solved and the lower time where the position is solved. If you have a rating list for those engines, another criteria to include would be, the positions solved by lower rated engine would also contribute to determine the easier positions. Any idea on how to find the top 100 easier positions?
Vinvin wrote: ↑Mon Dec 28, 2020 8:01 am
Each line is a position of the test. The number is the second needed to find the solution. If there's no number, the solution is not found.
When you go down after line #213, you will see the average time and the number of solutions found.
This is the top 100 easier positions based on larger count of engines that solved the positions followed by a smaller average time the engines solved the positions.
Vinvin wrote: ↑Mon Dec 28, 2020 8:01 am
Each line is a position of the test. The number is the second needed to find the solution. If there's no number, the solution is not found.
When you go down after line #213, you will see the average time and the number of solutions found.
What is your setting in arena?
At left, it's not very important, it's just the lines displayed after n-depth. I set to "10" but you can leave at "2".
I activate "abort", minimal depth= "24", if correct move is held "3" additional plies.