TalkChess.com

Wow, thanks for the info. Can you tell me the name (and download links if you have) of those DLL? It's api-ms-win-core-winrt-l1-1-0.dll and api-ms-win-core-winrt-string-l1-1-0.dll . Either you extract that from a Win10 system that you have around, or you could also get them from https://wikidll.com...

Actually, it does run under Win7-64 - just two additional MS DLLs required. Although I don't quite see the point of making it Win10 and MacOS only for now. My CT800 UCI engine seems to work nicely. Some things I noticed when playing around: 1) Why do I have to enter the engine name manually? That sh...

xr_a_y wrote: ↑

Sat Nov 09, 2019 3:21 pm

So if I need to now which one is best (after the TT one), I need to score them all (at least captures ...)

You could use MVV/LVA at this stage because that's cheap, pick the highest one of these and see whether you get a cut-off. If not, you can score and sort the remaining ones via SEE.

Minic is sorting all moves as soon as TT move is not a beta cut-off You could benchmark how often your first move cuts off if it isn't a TT hit, this will probably be something like 50-70%. Means, in all those cases, sorting the full move list is unnecessary because you're only going to use the top...

Not a fan of a depth limit, since they can occasionally be quite "coarse" in terms of time. And also unrealistic because humans also calculate deeper if there are fewer moves to consider. I have a pretty decent NPS idea in the works. I have normalized on 2800 Elo == 6M nodes per second (on my MacBo...

That prologue stuff is pointless. Just do 12 classic games, and if it's 6:6 afterwards, the player with the higher Elo is declared winner. That's equivalent.

I thought UCI options were not case sensitive. That's correct as per the UCI spec: The name and value of the option in <id> should not be case sensitive and can inlude spaces. But it should still fit in with the other parameters of the UCI spec - if it is even necessary, which it shouldn't be. Howe...

What is the usual policy of interfaces for UCI_ prefixed options they do not know? The UCI spec says: If the GUI gets an unknown Option with the prefix "UCI_", it should just ignore it and not display it in the engine's options dialog. Given how the whole spec misuses "should", this is meant as req...

Oh, that's nice. Thanks Graham, as always, for the tournaments.

The same skill can't be used on both machines... As for the search speed dependent part of the throttling: If you implement the waiting loop not to reduce NPS by a percentage, i.e. not relative to the machine's full speed, but instead configure NPS directly in throttled mode, then the same setting ...