algerbrex wrote: ↑Sat Jan 21, 2023 9:12 pm
Congratulations! I'm sure it feels great to have a more pure engine finally and the rating jump for Leorik 2.3 in the CCRL of over 50 Elo is very impressive. I think you've inspired me to get back into chess programming soon, I can't let Leorik get to far ahead
It would be great to have you back!
I know I haven't updated the devlog for a while but I'm actively working on Leorik. And just today I've replaced my Ryzen 3600 CPU with a Ryzen 5900X so instead of 10 games simultaneously I can now run 22 games to confirm quicker that all my "improvements" are indeed rubbish!
But seriously I'm really impressed with the new chip. Out of the box and on stock settings on my ancient 60€ mainboard it already performed on much higher clock rates than advertised. But the VRMs were getting hot (108° in a winter-cold room) so I undervolted the CPU, constrained the PPT to 100W and with just a 5-10% multi-core performance drop the entire system now only drains 180W from the wall-socket, while still boosting to 5Ghz single core and maintaining a stable 4.1Ghz on all-core load.
My only regret so far is that I didn't upgrade earlier!
Minimal Chess (simple, open source, C#) - Youtube & Github Leorik (competitive, in active development, C#) - Github & Lichess
lithander wrote: ↑Thu Dec 22, 2022 1:28 am
...
Here is a gauntlet I ran with a few engines of similar strength. All Elo values except Leorik's are fixed.
Hi, sorry for being less on topic but I have a question. In cutechess, how do you fix the elo of other players? I have been trying to do that for my gauntlets.
Sazgr wrote: ↑Mon Jan 23, 2023 8:32 pm
Hi, sorry for being less on topic but I have a question. In cutechess, how do you fix the elo of other players? I have been trying to do that for my gauntlets.
It may look inconvenient to do it like that but it has the additional advantage that you can look at the score whenever you like. You don't have to stop cutechess to see how the current standings are. And you can aggregate the games in multiple sessions.
Minimal Chess (simple, open source, C#) - Youtube & Github Leorik (competitive, in active development, C#) - Github & Lichess
lithander wrote: ↑Mon Jan 23, 2023 11:38 pm
It may look inconvenient to do it like that but it has the additional advantage that you can look at the score whenever you like. You don't have to stop cutechess to see how the current standings are. And you can aggregate the games in multiple sessions.
I maybe missed what you want to do, but in case you didn't know yet, you can add a flag to cutechess "-ratinginterval 50" which would mean that cutechess prints out the current standing every 50 games.
j.t. wrote: ↑Tue Jan 24, 2023 12:25 am
I maybe missed what you want to do, but in case you didn't know yet, you can add a flag to cutechess "-ratinginterval 50" which would mean that cutechess prints out the current standing every 50 games.
I didn't know that feature and it's a good tip! Thanks. The main reason I use Ordo though is that I fix all other engines with their CCRL rating so my own engines score is the only variable. And by that I try to find an Elo value for the tested version that is in the same scale as the CCRL.
Minimal Chess (simple, open source, C#) - Youtube & Github Leorik (competitive, in active development, C#) - Github & Lichess
Thinking about NN for Leorik. What if you keep your current eval for each piece as inputs. Then for each piece there is a hidden layer comprised of chess knowledge. And then there is one score for each piece as output. The outputs are added together to score the position. The hidden layer for each piece is trained from the same dataset that was used to train the PSTBls. How would that compare with NNUE?
Mike Sherwin wrote: ↑Thu Jan 26, 2023 9:36 am
Thinking about NN for Leorik.
I still haven't tried your idea of introducing 15x15 king-relative PSTs yet! And that's just one of many incremental steps I want to try before looking into NN-based eval in earnest. Once I'm ready I'll probably just start with the NNUE approach and a really simple topology like 768x64x1 for example! (6 Pieces x (Black + White) x 64 Squares = 768)
But currently I'm just focusing on search optimizations. I hope to get to 2800 CCRL Elo before touching the eval again.
Mike Sherwin wrote: ↑Thu Jan 26, 2023 9:36 am
How would that compare with NNUE?
I don't have the slightest idea! I can make all kind of crazy experiments once I know how to get basic NNUE to work in C#. And that's of course not possible without generating all the data and label it with my own engine and train the nets and so on... a lot to learn.
Minimal Chess (simple, open source, C#) - Youtube & Github Leorik (competitive, in active development, C#) - Github & Lichess
lithander wrote: ↑Sun Jan 22, 2023 8:49 pm
It would be great to have you back!
Thansk! Since I'm currently taking a CS course that uses Java, I may put Blunder to the side for a bit and work on creating an engine from scratch there, trying some different stuff, experimenting
lithander wrote: ↑Sun Jan 22, 2023 8:49 pm
I know I haven't updated the devlog for a while but I'm actively working on Leorik. And just today I've replaced my Ryzen 3600 CPU with a Ryzen 5900X so instead of 10 games simultaneously I can now run 22 games to confirm quicker that all my "improvements" are indeed rubbish!
But seriously I'm really impressed with the new chip. Out of the box and on stock settings on my ancient 60€ mainboard it already performed on much higher clock rates than advertised. But the VRMs were getting hot (108° in a winter-cold room) so I undervolted the CPU, constrained the PPT to 100W and with just a 5-10% multi-core performance drop the entire system now only drains 180W from the wall-socket, while still boosting to 5Ghz single core and maintaining a stable 4.1Ghz on all-core load.
My only regret so far is that I didn't upgrade earlier!
Nice! Depending on how much work I'm able to start doing on Blunder/my new engine during this semester, I may have to look into making some upgrades to my setup, as I'm able to run about 8 games comfortably using cutechess.