d-sparks/exacto

Exacto Chess Engine

exacto's Issues

Next steps for dev branch

In no particular order, except that likely time management should be the first priority so we can actually get this thing loaded into Tourney or something like it.

• Time management
• Rename all variables, methods, classes and structs to the Google style
• Investigate tensorflow for training regression/classification models, e.g.:
  • How much time to use on this move?
  • Move sorting parameters?
  • Evaluation parameters?
  • Tree pruning parameters?
• Parallelize
  • YBW algorithm?
• Search features
  • Adaptive null move forward pruning
  • Late move reductions
  • Killer moves and history heuristics
  • Static exchange evaluation

Mislabeled release

The sole existing release -- v0.e -- comes with an exec that identifies itself as 0.f. The codebase is 2015, while v0.e dates back to March 2014.

Since v0.e is the latest Exacto version on our lists and is practically impossible to find online (JM's site offers only the Mac version) it would be a good idea to repackage the existing release with the proper execs and code and make a separate one for v0.f, if only for the sake of historical accuracy.

If you have trouble locating the necessary files I put my copy that I got from Graham here.

Tirsa@CCRL