TalkChess.com

I missed this discussion. So what is agreed up on: info wdl 200 600 200 format for uci, and what for xboard? Thanks. I don't think anything has been agreed upon, but Fritz 17 is now confirmed to ship with a modified lc0 that has the patch pointed out in the original post: https://github.com/DanielU...

GPU: RTX 2070 May network versus elfv2: 10:10 October network versus elfv2: 12:8 So, the "700 Elo points" in self ratings is hugely inflated, and the progress is probably no more than 100 Elo points in 5 months, quite modest for Go. It's hard to say anything from such a short match, no? I think the...

Well, what is most wrong about 'wdl' as proposed is that it is partly redundant: the three values must sum up to 100. It would be more elegant to have the expected score (winprob + drawprob/2) as a new score mode (as alternative to 'mate' and 'cp'), and add a new info 'drawprob' with a single value...

I may add, uci protocol encourages clear key names, example, info depth, the word depth is fully spelled out. info score, the word score is fully spelled out too. info multipv and others. wdl is not clear, is it probability? is it a counter of something? winprob is more clearer to denote win probab...

phhnguyen wrote: ↑

Wed Oct 23, 2019 11:55 pm

Let me suggest a description about self-explaining data in which engines can tell chess GUIs how to display their data in the form of tables.

There is zero chance I'd be willing to shift the decision on how to present data from the USER INTERFACE to the ENGINE.

Why that configuration stuff at all? Just include the WDL with the three values for win, draw, loss in the info from engine to GUI. UCI explicitely specifies ignoring unknown things and continue parsing. If a GUI barfs on the wdl inside the info, it is not UCI-compliant anyway and should be fixed: ...

If an engine sends too much data to slowdown and/or crash chess GUIs, clearly it has a serious bug ;) Who has what bug? It's reasonable to optionally want the engine to dump out a ton of info every move for debugging. If there's no way to communicate what is useful to the UCI partner, the situation...

Perhaps simpler and more uci way of communicating is by key value pair. Example, winprob 20 drawprob 60 lossprob 20 values like 20, 60 and 20 are in percent. I don't see the benefit of having extra tags. We don't send a pv either with pv e4e4 pv e7e5 pv g1f3. I also don't see how it is simpler, loo...

This tells the engine what extra infos it can put in an 'info' command that the GUI knows how to display. If the GUI says it understands 'wdl', the engine can put wdl info with its PV, otherwise it will refrain from doing so. (Or it will find some backward-compatible way to display the info, like '...

phhnguyen wrote: ↑

Wed Oct 23, 2019 12:43 pm

I suggest a simple way: engines just send (JSON info) what they want.

This won't work for reasons already outlined in my post. The engine has no idea how much detail the GUI wants. And you can send enough info the make the GUI crawl...

HGM's idea seems fine.