protonspring
protonspring
The EGTB files should almost never change. Should i add them to the books repo and do a PR?
The set of files here was only 3MB. If that size alone is better than engames.cpp, then isn't that a different scenario?
i don't think it will be hard at all to fix fishtest to support this test.
i would expect the drive would cache those little files. if you are very worried about it, I might also just suggest to set up a ram disk and put...
i would be interested in adding only the necessary tables to replace some specific endgames. I have less experience than you folks, but KRPKR or KBPKR seem quite challenging. Perhaps...
At the very least, fix the directory issue so that a fishtest user could add an egtb to their code branch and test it on the framework.
If fishtest executed stockfish from the build directory, it would allow a developer to test whatever they wanted. What is the reasoning for changing the working directory?
Sry for the dumb questions, But wouldn't it be much more simple to just run the executable in the build directory?
Two questions: 1. Are all workers building now? 2. Are the branches to compare ( master vs patch) built in different directories?
I sm happy to help out if you give me some basic rules. On Sun, Sep 30, 2018, 2:11 PM Joost VandeVondele wrote: > right now, looks like we're short...