How do I force cutechess-cli to play a specific EPD position

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

Moderator: Ras

Tom Likens
Posts: 303
Joined: Sat Apr 28, 2012 6:18 pm
Location: Austin, TX

Re: How do I force cutechess-cli to play a specific EPD posi

Post by Tom Likens »

Ilari,

I've compiled the source from git and it seems to working. I fed it 4000 epd positions and it's cranking through them now. Initially, it threw me since it complained about not recognizing the "-epdin" command line argument, but then I realized you'd incorporated it's functionality into the "-opening" command line argument, which actually makes sense now that PGN and EPD files are handled in the same way.

Anyway, very nice. I need to modify my clop python scripts and a few other things but that's trivial.

One thing, I wanted to ask about--I'm not sure about the program versioning number you're using. This is version "0.5.1". When does a change become significant enough to increment the minor number. What I'm asking is what would have to change for this to become "0.5.2" etc.? Differentiating the minor version number might make it a bit easier to keep track of the features that the various versions support.

regards,
--tom
User avatar
ilari
Posts: 750
Joined: Mon Mar 27, 2006 7:45 pm
Location: Finland

Re: How do I force cutechess-cli to play a specific EPD posi

Post by ilari »

Tom Likens wrote:Ilari,

I've compiled the source from git and it seems to working. I fed it 4000 epd positions and it's cranking through them now. Initially, it threw me since it complained about not recognizing the "-epdin" command line argument, but then I realized you'd incorporated it's functionality into the "-opening" command line argument, which actually makes sense now that PGN and EPD files are handled in the same way.

Anyway, very nice. I need to modify my clop python scripts and a few other things but that's trivial.
Right, I forgot to mention that the command line options had changed. In pre-alpha software anything can change at any time. Once we get to 1.0 we're not going to make big changes so lightly.
One thing, I wanted to ask about--I'm not sure about the program versioning number you're using. This is version "0.5.1". When does a change become significant enough to increment the minor number. What I'm asking is what would have to change for this to become "0.5.2" etc.? Differentiating the minor version number might make it a bit easier to keep track of the features that the various versions support.

regards,
--tom
Actually the minor number is the second number - it's major, minor, patch. If I released a bugfixed version of the latest version it would be v0.5.2. But the next version is going to have a lot of new functionality so it deserves a minor version bump and is going to be v0.6.0. What you're using is not officially released yet, so even though cutechess-cli reports version 0.5.1 it's more like version 4f345b7c3f (the SHA1 checksum of the latest Git commit).