Laskos wrote: ↑Wed Jun 19, 2019 1:52 pm
STS is not great positional test suite and this became clear precisely with Leela. I have my own 3 year old positional opening suite containing 200 positions
...
Is this test still available for download somewhere?
My forum research only found a dead link in a post sixteen months ago (not three years?).
Rebel wrote: ↑Fri Jun 21, 2019 8:40 am
I started talking to you because I disagreed about things you said about STS and he was right. I don't think 200 positions can ever be proof of overall superiority. I did Kai's test and 2 program in the range of 2400-2500 elo are in the middle between the tops.
Thanks. This is _positional_ test suite, not "strength" test suite. You results look reasonable (on strong GPU you will get even higher results for Leela late 20b nets). Mephisto Gideon can well be positionally above some recent much stronger engines. There is emphasis nowadays on a standard by now very efficient search.
My suite is rough and unpolished. I guess 10% of my solutions are wrong, and another 10% dubious. But seeing Lc0 at longer times on strong GPU solving about 80%, I get confidence in both: my suite is not totally useless AND in that Lc0 in the openings is a positional phenomenon. I guess the opening theory will soon be affected by NN-based engines.
Laskos wrote: ↑Wed Jun 19, 2019 1:52 pm
STS is not great positional test suite and this became clear precisely with Leela. I have my own 3 year old positional opening suite containing 200 positions
...
Is this test still available for download somewhere?
My forum research only found a dead link in a post sixteen months ago (not three years?).
I think I bundled together in a zip file the opening suite with the even more dubious midgame positional suite (I have an updated version of the latter).
peter wrote: ↑Fri Jun 21, 2019 12:20 am
But to me the only reason for a test- suite to get outdated was, if it was solved too easily and too completely by new arising engines. No reason to update because a single one new engine doesn't perform good enough for some fans of the new engine.
That's pretty unreasonable to Dann & Swami considering the energy and massive computer time they spend. It was good at the time, now it needs an update.
...
I don't believe that happened with the creation of STS. In the 90's people cooperated online to create a tactical suite called ECM. Many programmers profited despite its errors.
I didn't mean STS being outdated neither bulit for a single engine (neither Rybka nor any other of that time) I meant Kai's one.
But as I said before I wanted to talk about STS, take it up with Kai.
90% of coding is debugging, the other 10% is writing bugs.
Laskos wrote: ↑Fri Jun 21, 2019 10:24 amMy suite is rough and unpolished. I guess 10% of my solutions are wrong, and another 10% dubious. But seeing Lc0 at longer times on strong GPU solving about 80%, I get confidence in both: my suite is not totally useless AND in that Lc0 in the openings is a positional phenomenon. I guess the opening theory will soon be affected by NN-based engines.
The red is absolutely true. I was studying the one ply result of Lc0 (see the Whatever is current - Amazing Leela thread) and it amazes me that just on one ply it created the "Ruy Lopez - closed" main variation all by its own.
Laskos wrote: ↑Fri Jun 21, 2019 10:24 amMy suite is rough and unpolished. I guess 10% of my solutions are wrong, and another 10% dubious. But seeing Lc0 at longer times on strong GPU solving about 80%, I get confidence in both: my suite is not totally useless AND in that Lc0 in the openings is a positional phenomenon. I guess the opening theory will soon be affected by NN-based engines.
The red is absolutely true. I was studying the one ply result of Lc0 (see the Whatever is current - Amazing Leela thread) and it amazes me that just on one ply it created the "Ruy Lopez - closed" main variation all by its own.
The closer you get to the root of the game, the more the NN is a database lookup of the statistics of the input games, and since the input games are self-generated at something beyond 3000 Elo, it ought to be able to steer to various unknown as yet traps and re-assessments of known and unknown lines.
Laskos wrote: ↑Fri Jun 21, 2019 10:24 amMy suite is rough and unpolished.
Question about your suite, how long does it take (an estimation is also ok) to analyze your 200 positions at (say) depth=5 with a 256x20 NN on your (GPU) hardware.
90% of coding is debugging, the other 10% is writing bugs.
Laskos wrote: ↑Fri Jun 21, 2019 10:24 amMy suite is rough and unpolished.
Question about your suite, how long does it take (an estimation is also ok) to analyze your 200 positions at (say) depth=5 with a 256x20 NN on your (GPU) hardware.
Not sure about depth, I am testing at fixed time, but depth=5 is really low for current Lc0 on my GPU. The times are from 1s per position (about 15,000 nodes) to 120s per position (about 2,500,000 nodes).
Laskos wrote: ↑Fri Jun 21, 2019 10:24 amMy suite is rough and unpolished.
Question about your suite, how long does it take (an estimation is also ok) to analyze your 200 positions at (say) depth=5 with a 256x20 NN on your (GPU) hardware.
Not sure about depth, I am testing at fixed time, but depth=5 is really low for current Lc0 on my GPU. The times are from 1s per position (about 15,000 nodes) to 120s per position (about 2,500,000 nodes).
Thanks Kai. That's more than 100 x faster I have right now. I think I am going to buy some flowers for my wife tomorrow.
90% of coding is debugging, the other 10% is writing bugs.
Laskos wrote: ↑Fri Jun 21, 2019 10:24 amMy suite is rough and unpolished.
Question about your suite, how long does it take (an estimation is also ok) to analyze your 200 positions at (say) depth=5 with a 256x20 NN on your (GPU) hardware.
Not sure about depth, I am testing at fixed time, but depth=5 is really low for current Lc0 on my GPU. The times are from 1s per position (about 15,000 nodes) to 120s per position (about 2,500,000 nodes).
Thanks Kai. That's more than 100 x faster I have right now. I think I am going to buy some flowers for my wife tomorrow.