Cutechess-cli 0.5.0 for Linux available

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

Moderator: Ras

lucasart
Posts: 3241
Joined: Mon May 31, 2010 1:29 pm
Full name: lucasart

Re: Cutechess-cli 0.5.0 for Linux available

Post by lucasart »

A nice feature you could add to cutechess-cli is "proto=auto". Some GUIs (like Arena for example) can do this, and detect automatically the protocol.

The implementation would be fairly simple:
- try sending "uci" to the engine
- upon receipt of "uciok" you know the protocol should be UCI, otherwise you can assume it's Xboard.

Also proto=auto could be the default value. So if no proto is specified, cutechess-cli would use proto=auto.
User avatar
ilari
Posts: 750
Joined: Mon Mar 27, 2006 7:45 pm
Location: Finland

Re: Cutechess-cli 0.5.0 for Linux available

Post by ilari »

lucasart wrote:A nice feature you could add to cutechess-cli is "proto=auto". Some GUIs (like Arena for example) can do this, and detect automatically the protocol.

The implementation would be fairly simple:
- try sending "uci" to the engine
- upon receipt of "uciok" you know the protocol should be UCI, otherwise you can assume it's Xboard.

Also proto=auto could be the default value. So if no proto is specified, cutechess-cli would use proto=auto.
I've been thinking about this. The problem is that auto-detection never seems to be completely fail-safe. There's also the fact that libcutechess could easily support more protocols, which would make auto-detection even tougher.
lucasart
Posts: 3241
Joined: Mon May 31, 2010 1:29 pm
Full name: lucasart

Re: Cutechess-cli 0.5.0 for Linux available

Post by lucasart »

ilari wrote:
lucasart wrote:A nice feature you could add to cutechess-cli is "proto=auto". Some GUIs (like Arena for example) can do this, and detect automatically the protocol.

The implementation would be fairly simple:
- try sending "uci" to the engine
- upon receipt of "uciok" you know the protocol should be UCI, otherwise you can assume it's Xboard.

Also proto=auto could be the default value. So if no proto is specified, cutechess-cli would use proto=auto.
I've been thinking about this. The problem is that auto-detection never seems to be completely fail-safe. There's also the fact that libcutechess could easily support more protocols, which would make auto-detection even tougher.
Well, up to you. It's not really a big deal, just a "nice to have" feature.

I'm currently using cutechess-cli quite intensively to construct my "GPL Blitz list" (cf my post on the Tournament forum). And it's behaving wonderfully well :)

As for Beowulf, this engine supports both UCI and Xboard. But the UCI support is buggy (as I mentionned earlier). So I'm testing it in Xboard mode and it's fine.