STS revisited

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

Moderators: hgm, Rebel, chrisw

peter
Posts: 3186
Joined: Sat Feb 16, 2008 7:38 am
Full name: Peter Martan

STS revisited

Post by peter »

...revised and refurbished
:)
The Strategic Test Suite by Swaminathan and Corbit

https://sites.google.com/site/strategic ... e/sts-stat

had an own program made by Philippe Gailhac for evaluating it (see the site of the link), multiple solutions of strategically meaningful positions had to be judged with different amounts of points instead of single best moves only.

Pity most of the positions don't stand evaluation with modern engines as for the solutions and points anymore, stored in the 15 blocks of 100 positions each, thematically sorted, even if many of the positions are still worth trying as for positional testing of the kind, the suite was meant to be used orgininally as I understood that way back then.

Those never were meant for tactical single best move- testing, on the contrary engine should judge them almost without search, with as short TC as possible, to get move ordering almost out of "static eval" at once.

For this kind of testing with very short time control, I sorted out 594 of the orginally 1500 in the following way:
Only best move was kept, only those positions of at least 50%- difference between best and second best move- eval, seen from the height of lesser one, e.g. best move 0.75cp, second best not better than 0.50 cp.

SF was the main engine for me to evaluate with, notice that numeric height of eval of a certain engine itself shouldn't really matter if the relation of the evals given by other engines fit as well even with much higher or much lower numbers in output.
Anyhow the evaluation was mainly one of my own more then of enslavement to engines' one, most of the time I did rely on some short Forward- Backward and positional evaluation of the candidate moves done by my personal pov then.

Having that all said, I hope Dann Corbit has a look at the link, if by me also much honoured Mr. Swaminathan is reading her at times anymore, I don't know, but if I see his nick swami in members list still yet too.

https://www.dropbox.com/s/khn8tkonb68kcel/594.epd?dl=0

is .epd of the 594 positions with best move each, the numbers given as sources are such, that I got by putting all 1500 postions in order of the blocks' numbers of orginal suite together in one .pgn- file from 1 to 1500.

Hope, that's ok with you, dear Dann, please let me know your verdict if you find the time to see the positions through once in a while.
Here

Code: Select all

    Program                                    Elo   +/-  Matches  Score   Av.Op.   S.Pos.   MST1    MST2   RIndex

  1 Lc0v0.30.0-dag+git.c91bf77               : 3500    0    471    50.0 %   3500   486/512    1.0s    1.0s   1.00
  2 Stockfish310722                          : 3500    0    471    50.0 %   3500   482/512    1.0s    1.0s   0.99



MST1  : Mean solution time (solved positions only)
MST2  : Mean solution time (solved and unsolved positions)
RIndex: Score according to solution time ranking for each position
I did let two engines run with 2"/position (1 would have been enough too, just to have a minimal space of time to solution, so I doubled that) over the 512 first ones out of the 594 in .epd above.
That just to see, how many would get solved and if there would be any difference in rating and ranking by EloStatTS from Frank Schubert, without a program of that kind, there won't be any use in a test suite like this at all, I fear, counting unsolved postions only wouldn't give any statistical meaning. That there isn't any counting difference between LC0 and SF so far to me is just ok, being both the probably best engines as for their "static eval" at the moment, if TC was short enough to almost avoid any deeper search. LC0 was run with weights_run3_784822.lc0.

If there would be more programs with more positions (trying to get next version up to at least 650 by adding early opening positions out of books and databases with good statistical evaluation from high class games) to run with more engines (which would make discrimination by that bigger too as for the "Matches" of EloStatTS) I hope testing more engines of interest single threaded only then with very short TC again, that could give results of their own of interest yet too, of course as always not to be compared directly with such of other suites, e.g. such of tactical single best move suites, which at least have to be run with quite different hardware- TCs.
Will keep you informed, but will have to have at least some more weeks to get to next version, hopefully of more utility then but the one of this first beta- test.

Enjoy!
Peter.
peter
Posts: 3186
Joined: Sat Feb 16, 2008 7:38 am
Full name: Peter Martan

Re: STS revisited

Post by peter »

peter wrote: Sun Sep 11, 2022 9:54 am LC0 was run with weights_run3_784822.lc0.
...on a 3070ti GPU, ran out of edit- time before, not being able to connect to server just at that moment for a while.

In the meantime here I had two more runs with the full 594 positions in Shredder- GUI with single second/position.
This time both engines used 1 thread of the 16x3.6GHz CPU only, taking default 2 CPU- threads for LC0 of course doen't give much difference, using same GPU again yet, but comparing SMP to single thread for SF shows, there isn't so much difference in percentage of solutions neither. That would fit to the assumption, that search and depth should matter less than as for tactical positions with some difficulty in regard to hardware and TC.
Hash for SF was 256Mb, LC0 had 200Mb NN-cache, 6men Syzygys loaded, 2 extra plies.
LC0:

Code: Select all

Bisher gelöst: 549 von 594  ;  50s

         1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16  17  18  19  20
 -------------------------------------------------------------------------------------
   0 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
  20 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
  40 |   0   0   0   -   0   0   0   0   0   0   0   0   -   0   0   -   0   0   0   0
  60 |   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0   0   0
  80 |   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -
 100 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 120 |   -   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 140 |   0   0   0   0   0   0   0   0   -   0   0   -   0   0   0   0   0   0   0   0
 160 |   0   0   0   -   0   0   -   0   -   0   0   0   0   0   0   0   0   0   0   0
 180 |   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0   -   0   0   0
 200 |   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   -   0   0   0
 220 |   -   0   0   -   0   0   0   0   0   -   0   0   0   0   -   -   0   0   0   0
 240 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   -
 260 |   0   0   0   -   0   0   0   0   0   0   0   0   -   0   0   -   0   0   0   0
 280 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0
 300 |   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0
 320 |   0   0   0   0   0   0   0   0   0   0   0   0   -   -   0   0   0   0   0   0
 340 |   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0
 360 |   -   0   0   0   0   0   -   -   0   0   0   0   0   0   -   -   0   0   0   0
 380 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -
 400 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 420 |   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0
 440 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 460 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 480 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 500 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 520 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 540 |   0   0   0   0   0   0   0   0   0   0   0   0   -   0   -   0   0   0   0   -
 560 |   0   0   0   0   0   0   0   -   0   -   0   0   0   0   0   0   0   0   0   0
 580 |   0   0   0   0   -   0   0   0   0   0   0   0   0   0

   1 sec -> 549/594
  K/s: 9.262  
  TotTime: 4:17m    SolTime: 50s
  Ply: 0   Positions:158   Avg Nodes:       0   Branching = 0.00
  Ply: 1   Positions:152   Avg Nodes:       3   Branching = 0.00
  Ply: 2   Positions:132   Avg Nodes:       9   Branching = 3.00
  Ply: 3   Positions:114   Avg Nodes:      29   Branching = 3.22
  Ply: 4   Positions: 83   Avg Nodes:      90   Branching = 3.10
  Ply: 5   Positions: 69   Avg Nodes:     256   Branching = 2.84
  Ply: 6   Positions: 71   Avg Nodes:     611   Branching = 2.39
  Ply: 7   Positions: 55   Avg Nodes:    1182   Branching = 1.93
  Ply: 8   Positions: 41   Avg Nodes:    1874   Branching = 1.59
  Ply: 9   Positions: 29   Avg Nodes:    3017   Branching = 1.61
  Ply:10   Positions: 17   Avg Nodes:    3211   Branching = 1.06
  Ply:11   Positions:  9   Avg Nodes:    3669   Branching = 1.14
  Ply:12   Positions:  2   Avg Nodes:    3675   Branching = 1.00
And SF 310722:

Code: Select all

Bisher gelöst: 555 von 594  ;  1:07m

         1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16  17  18  19  20
 -------------------------------------------------------------------------------------
   0 |   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0   0
  20 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   1   0   0   0   0   0
  40 |   0   0   0   -   0   0   0   0   0   0   0   0   -   0   0   -   0   0   0   0
  60 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
  80 |   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -
 100 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0
 120 |   -   0   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0
 140 |   0   0   0   0   0   0   0   0   -   0   0   -   0   0   0   0   0   0   0   0
 160 |   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0   0
 180 |   -   0   0   -   0   0   0   0   0   -   0   0   0   0   0   0   -   0   0   0
 200 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0
 220 |   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0
 240 |   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   -   0   0   0   0
 260 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   -
 280 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0
 300 |   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   -   0   0   0   0
 320 |   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0
 340 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 360 |   -   0   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0
 380 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -
 400 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 420 |   0   0   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0
 440 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 460 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 480 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 500 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 520 |   0   -   0   0   -   0   0   0   0   0   -   -   0   0   0   0   0   0   0   0
 540 |   0   0   0   0   0   0   -   0   0   0   0   0   0   0   -   0   0   0   0   0
 560 |   0   0   0   0   0   0   0   -   0   -   0   0   0   0   0   0   0   0   0   0
 580 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0

   1 sec -> 554/594
  K/s: 1.717.001  
  TotTime: 10:31m    SolTime: 1:07m
  Ply: 0   Positions:312   Avg Nodes:       0   Branching = 0.00
  Ply: 1   Positions:369   Avg Nodes:      58   Branching = 0.00
  Ply: 2   Positions:341   Avg Nodes:     129   Branching = 2.22
  Ply: 3   Positions:329   Avg Nodes:     206   Branching = 1.60
  Ply: 4   Positions:307   Avg Nodes:     276   Branching = 1.34
  Ply: 5   Positions:290   Avg Nodes:     415   Branching = 1.50
  Ply: 6   Positions:240   Avg Nodes:     871   Branching = 2.10
  Ply: 7   Positions:177   Avg Nodes:    2109   Branching = 2.42
  Ply: 8   Positions:147   Avg Nodes:    4755   Branching = 2.25
  Ply: 9   Positions:138   Avg Nodes:    9053   Branching = 1.90
  Ply:10   Positions:101   Avg Nodes:   16234   Branching = 1.79
  Ply:11   Positions: 83   Avg Nodes:   32254   Branching = 1.99
  Ply:12   Positions: 74   Avg Nodes:   52529   Branching = 1.63
  Ply:13   Positions: 69   Avg Nodes:   93196   Branching = 1.77
  Ply:14   Positions: 60   Avg Nodes:  135072   Branching = 1.45
  Ply:15   Positions: 60   Avg Nodes:  194377   Branching = 1.44
  Ply:16   Positions: 44   Avg Nodes:  260743   Branching = 1.34
  Ply:17   Positions: 40   Avg Nodes:  435682   Branching = 1.67
  Ply:18   Positions: 38   Avg Nodes:  665593   Branching = 1.53
  Ply:19   Positions: 33   Avg Nodes:  910388   Branching = 1.37
  Ply:20   Positions: 26   Avg Nodes: 1102445   Branching = 1.21
  Ply:21   Positions: 22   Avg Nodes: 1328306   Branching = 1.20
  Ply:22   Positions: 13   Avg Nodes: 1467265   Branching = 1.10
  Ply:23   Positions:  5   Avg Nodes: 1543882   Branching = 1.05
  Ply:24   Positions:  2   Avg Nodes: 1581501   Branching = 1.02
  Ply:25   Positions:  1   Avg Nodes: 1712272   Branching = 1.08
  Ply:26   Positions:  1   Avg Nodes: 1839272   Branching = 1.07
Peter.
peter
Posts: 3186
Joined: Sat Feb 16, 2008 7:38 am
Full name: Peter Martan

Re: STS revisited

Post by peter »

Found out, I probably should have mentioned Ferdinand Mosca having made a revise of STS of his own some years ago too:

https://www.chessprogramming.org/Strate ... %20tool%20.

There was a thread about that here:

http://www.talkchess.com/forum3/viewtop ... 06#p628006

Knew about that but just didn't ever have a closer look at it, neither the positions nor the tool to evaluate, yet I feel the need to appologize to Ferdy not to have mentioned him at first posting too, in the meantime I saw other names of people having dealt with STS also like Thomas Mayer and Ed Schröder, my regrets to them and everybody else I forgot to mention too, it seems, STS has had quite some interest over the years at all.

Just downloaded the postions I used for my revise from the site, I gave the link in first posting

https://sites.google.com/site/strategic ... e/sts-stat

BTW. this link doesn't work anymore at the moment, hope the site wasn't already taken offline just to stop people like me from doing further nonsense with it
:)
Peter.
swami
Posts: 6640
Joined: Thu Mar 09, 2006 4:21 am

Re: STS revisited

Post by swami »

peter wrote: Sun Sep 11, 2022 2:24 pm Found out, I probably should have mentioned Ferdinand Mosca having made a revise of STS of his own some years ago too:

https://www.chessprogramming.org/Strate ... %20tool%20.

There was a thread about that here:

http://www.talkchess.com/forum3/viewtop ... 06#p628006

Knew about that but just didn't ever have a closer look at it, neither the positions nor the tool to evaluate, yet I feel the need to appologize to Ferdy not to have mentioned him at first posting too, in the meantime I saw other names of people having dealt with STS also like Thomas Mayer and Ed Schröder, my regrets to them and everybody else I forgot to mention too, it seems, STS has had quite some interest over the years at all.

Just downloaded the postions I used for my revise from the site, I gave the link in first posting

https://sites.google.com/site/strategic ... e/sts-stat

BTW. this link doesn't work anymore at the moment, hope the site wasn't already taken offline just to stop people like me from doing further nonsense with it
:)
I just revisited the site after a long time, and first thing I got prompted to was to migrate to the newer version of the Google site, as old one (classic it was) is no longer functional. Hope I didn't mess it up while migrating. The link appears to be working fine, just let me know if it doesn't, I will figure out what went wrong. As for your initial post, let me go through the modification - It was long back and I had to rehash all that stuff to really get into the realm. Some of the positions may have aged and maybe due for replacement, however it's of good use for upcoming engines, which are not really at the top.
peter
Posts: 3186
Joined: Sat Feb 16, 2008 7:38 am
Full name: Peter Martan

Re: STS revisited

Post by peter »

swami wrote: Sun Sep 11, 2022 8:02 pm I just revisited the site after a long time, and first thing I got prompted to was to migrate to the newer version of the Google site, as old one (classic it was) is no longer functional. Hope I didn't mess it up while migrating. The link appears to be working fine, just let me know if it doesn't, I will figure out what went wrong. As for your initial post, let me go through the modification - It was long back and I had to rehash all that stuff to really get into the realm. Some of the positions may have aged and maybe due for replacement, however it's of good use for upcoming engines, which are not really at the top.
Hi Swami!
Thanks for migrating the site, link works again.
Nice to read from you
:!:
Peter.
User avatar
Rebel
Posts: 6995
Joined: Thu Aug 18, 2011 12:04 pm

Re: STS revisited

Post by Rebel »

As I found out a couple of years ago engines like Rybka and Houdini scored a lot better than Stockfish / Komodo. No big surprise if you realize the STS positions were analyzed by the then top engines Rybka and Houdini.
90% of coding is debugging, the other 10% is writing bugs.
peter
Posts: 3186
Joined: Sat Feb 16, 2008 7:38 am
Full name: Peter Martan

Re: STS revisited

Post by peter »

Rebel wrote: Sun Sep 11, 2022 9:09 pm As I found out a couple of years ago engines like Rybka and Houdini scored a lot better than Stockfish / Komodo. No big surprise if you realize the STS positions were analyzed by the then top engines Rybka and Houdini.
Of course, so I tried to filter out the positions with too near to each other candidate moves and stored a single best move only at the rest of them, which in many cases wasn't the same one as the old, then best rated one. You can compare by the numbers in 594.epd stored as source within original suite of 1500.

So the solutions by too much fortune as well as the ones with wrong moves stored as solution and thus solved wrongly by e.g. Rybka and Houdini having brought these moves up in the suite way back then, these bugs shouldn't favour these old engines anymore.

Here I had one more run with Fritz 15 (Rybka 4.x) single thread (3.5GHz) 1"/position, 64Mb hash to compare to the runs of LC0 and SF above.

Code: Select all

Bisher gelöst: 491 von 594  ;  2:29m

         1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16  17  18  19  20
 -------------------------------------------------------------------------------------
   0 |   0   0   0   0   0   0   0   0   0   -   0   -   0   0   0   0   0   0   0   0
  20 |   0   0   -   0   0   0   0   -   0   -   0   0   0   -   0   0   0   0   0   0
  40 |   0   -   0   -   0   0   -   0   0   0   0   0   -   -   0   0   0   0   0   0
  60 |   0   -   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   0   0   0
  80 |   0   0   -   -   0   -   0   -   -   0   0   0   0   0   0   0   0   0   0   -
 100 |   0   0   0   0   0   0   -   -   0   0   0   -   0   0   0   0   0   0   0   0
 120 |   0   0   0   0   0   0   0   0   -   -   0   0   0   0   0   0   -   -   0   0
 140 |   0   0   0   0   0   -   0   0   -   0   0   -   0   0   0   0   0   0   0   0
 160 |   0   0   0   0   0   -   -   0   -   0   0   0   0   0   0   0   0   0   0   0
 180 |   0   0   0   -   0   0   0   -   0   -   0   0   0   -   -   0   -   0   0   0
 200 |   -   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0
 220 |   0   -   0   -   0   0   0   0   0   0   0   0   0   0   -   -   0   0   0   0
 240 |   0   0   -   0   0   0   -   -   0   -   0   0   -   -   -   -   0   -   0   -
 260 |   -   0   0   -   0   0   0   0   -   -   0   0   -   -   0   0   0   0   0   -
 280 |   -   0   -   0   -   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0
 300 |   0   0   0   0   0   0   0   0   0   -   0   0   0   0   0   -   -   0   0   0
 320 |   0   0   0   0   0   0   0   0   0   0   0   0   -   -   0   -   0   0   -   0
 340 |   0   0   0   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0
 360 |   0   0   0   0   -   0   -   0   0   0   -   0   0   0   0   -   0   0   0   0
 380 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 400 |   0   0   -   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   -   0
 420 |   -   0   0   0   0   0   -   0   0   0   0   0   -   -   0   0   0   0   0   -
 440 |   0   0   0   0   -   0   0   0   0   0   0   0   0   0   -   0   0   0   0   -
 460 |   0   0   -   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0
 480 |   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   -   0   0   0   0
 500 |   0   0   0   0   0   -   0   0   0   0   -   0   0   0   0   0   0   0   0   -
 520 |   0   0   0   0   -   0   0   0   0   0   -   0   0   0   0   0   -   0   0   -
 540 |   0   0   0   0   0   0   -   0   0   0   0   0   0   0   0   0   0   0   0   0
 560 |   0   0   0   0   0   0   0   -   0   -   0   -   0   0   0   0   0   0   0   0
 580 |   0   0   0   0   0   0   0   0   0   0   0   0   -   0

   1 sec -> 491/594
  K/s: 1.421.104  
  TotTime: 9:46m    SolTime: 2:29m
  Ply: 0   Positions:594   Avg Nodes:       0   Branching = 0.00
  Ply: 4   Positions:344   Avg Nodes:     548   Branching = 0.00
  Ply: 5   Positions:303   Avg Nodes:    1122   Branching = 2.05
  Ply: 6   Positions:271   Avg Nodes:    2082   Branching = 1.86
  Ply: 7   Positions:265   Avg Nodes:    3677   Branching = 1.77
  Ply: 8   Positions:254   Avg Nodes:    6554   Branching = 1.78
  Ply: 9   Positions:239   Avg Nodes:   11487   Branching = 1.75
  Ply:10   Positions:226   Avg Nodes:   21372   Branching = 1.86
  Ply:11   Positions:201   Avg Nodes:   35987   Branching = 1.68
  Ply:12   Positions:173   Avg Nodes:   61350   Branching = 1.70
  Ply:13   Positions:158   Avg Nodes:  107008   Branching = 1.74
  Ply:14   Positions:147   Avg Nodes:  177369   Branching = 1.66
  Ply:15   Positions:135   Avg Nodes:  289489   Branching = 1.63
  Ply:16   Positions:120   Avg Nodes:  426532   Branching = 1.47
  Ply:17   Positions:106   Avg Nodes:  595229   Branching = 1.40
  Ply:18   Positions: 86   Avg Nodes:  841294   Branching = 1.41
  Ply:19   Positions: 66   Avg Nodes:  969216   Branching = 1.15
  Ply:20   Positions: 37   Avg Nodes: 1062651   Branching = 1.10
  Ply:21   Positions: 26   Avg Nodes: 1155243   Branching = 1.09
  Ply:22   Positions: 11   Avg Nodes: 1233459   Branching = 1.07
  Ply:23   Positions:  4   Avg Nodes: 1206358   Branching = 0.98
  Ply:24   Positions:  2   Avg Nodes: 1356704   Branching = 1.12
  Ply:25   Positions:  1   Avg Nodes: 1426001   Branching = 1.05
Yet 64 more unsolved positions than SF under same conditions.
I don't think Houdini 4 would be much more successful, that's one version I still have.
If I'm wrong, I'll come back with this one run too, if not I'll go on adding more positions fitting to the 594. Those are just to few to get enough discrimination in that kind of a positional test to separate the best ones from each other, the 594 would already work for engines like Fritz15, as Swami did suppose already too in his posting,
regards
Peter.
swami
Posts: 6640
Joined: Thu Mar 09, 2006 4:21 am

Re: STS revisited

Post by swami »

peter wrote: Sun Sep 11, 2022 8:29 pm
swami wrote: Sun Sep 11, 2022 8:02 pm I just revisited the site after a long time, and first thing I got prompted to was to migrate to the newer version of the Google site, as old one (classic it was) is no longer functional. Hope I didn't mess it up while migrating. The link appears to be working fine, just let me know if it doesn't, I will figure out what went wrong. As for your initial post, let me go through the modification - It was long back and I had to rehash all that stuff to really get into the realm. Some of the positions may have aged and maybe due for replacement, however it's of good use for upcoming engines, which are not really at the top.
Hi Swami!
Thanks for migrating the site, link works again.
Nice to read from you
:!:
Thanks Peter, got many mails that downloads aren't working. I guess I will have to check the site settings again.
peter
Posts: 3186
Joined: Sat Feb 16, 2008 7:38 am
Full name: Peter Martan

Re: STS revisited

Post by peter »

swami wrote: Wed Sep 14, 2022 7:34 am
peter wrote: Sun Sep 11, 2022 8:29 pm
swami wrote: Sun Sep 11, 2022 8:02 pm I just revisited the site after a long time, and first thing I got prompted to was to migrate to the newer version of the Google site, as old one (classic it was) is no longer functional. Hope I didn't mess it up while migrating. The link appears to be working fine, just let me know if it doesn't, I will figure out what went wrong. As for your initial post, let me go through the modification - It was long back and I had to rehash all that stuff to really get into the realm. Some of the positions may have aged and maybe due for replacement, however it's of good use for upcoming engines, which are not really at the top.
Hi Swami!
Thanks for migrating the site, link works again.
Nice to read from you
:!:
Thanks Peter, got many mails that downloads aren't working. I guess I will have to check the site settings again.
I didn't try any new downloads from the sites, but it's good to know, you care.
BTW, here' one more link:

https://www.dropbox.com/s/k3pvjhcdhkwgpes/1001.epd?dl=0

These 1001 positions are from combining 700 I made out of the 594 by adding single best move early opening positions, with the 111 of Eret

https://glarean-magazin.ch/2017/03/05/c ... test-eret/

and the 200 of latest Arasan Testsuite.

https://www.arasanchess.org/testsuite.shtml

, removed the few doublets of these 3 parts, they fit together quite well as for hardware- TC.

1"/position single threaded already gives some more discrimination even of the best one engines too. Running those positions with less than 1" is even more selecitve of course and make use of SMP possible too, e.g. 200msec isn't a bad test- scheme here, SF dev. with 30 threads of a 16x3.5GHz CPU gives 923/1001 solved.
I'd add some increment for initialation- time of LC0 to compare to SF.
LC0 with 3070ti GPU and 300msec/pos. solved 797/1001.

EloStatTS works only with Fritz, which can't be set to <1", but then Frank Schubert's program is able to compensate longer initialation- time, the engine needs with each new position, by the so called Offset.pgn in EloStatTS- download.
I'm happy to have such a positional test suite again to be run with very short TC, supplementary to the more difficult tactical ones, that do need longer hardware- TC of course.

Best regards
Peter.