TalkChess.com

There are two different ways to implement SEE. One is to have some early shortcuts (e.g. in see_sign) and if they don't lead to cutoffs, build the complete swap list first and evaluate it at the end. This approach was for example taken by Fruit and Stockfish. At first glance this approach seems to b...

Recommended reading: http://www.debuggingrules.com/ Especially the rule: "Quit thinking and look". This means not to make wild guesses when you don't have an idea what in thousands of lines of code causes the difference. Rather add a dump and see where the difference occurs: http://talkchess.com/for...

With DEPTH_ONE removed, the MovePicker must be used at least once at the beginning for move ordering. Tests with more games must show which option is the best: - use MovePicker only once at the beginning (as in 1.0c). If we have to keep DEPTH_ONE specials, beginning would mean after DEPTH_ONE. - us...

mcostalba wrote: The biggest drawback of std::sort() is that is platform dependent:

That can be resolved (on the cost of runtime) by using std::stable_sort().

One problem is that the strong programs that we need for testing have lousy support for this. ACK. I modified some programs (Toga, Strelka) to support fixed nodes. Also some of the strong programs those days (Shredder, Rybka) do support fixed nodes. I filed a feature request to Mark for HIARCS, but...

The sort_moves function from Stockfish header move.h should be functionally equivalent to the following piece of STL code I didn't read through the whole discussion but I'd like to note that in Onno, I started with std::sort (or std::stable_sort?) from the STL (fastest to implement) and later repla...

It is true that if it fails low then it is not written, but in a "normal" search you return an exact score after having resolved all the fails high/low along the PV line. In deed. But in another threat we had a discussion about printing PVs that failed high or low. BTW we have tested when we moved ...

For some reason, it can happen that the PV is shorter than depth, I think I located what "some reason" is. Stockfish does not track the PV. It just tries to retrieve the PV from the TT after a move is finished. This will not always be successful. Not just because of possible early overwrites, also ...

In SF we simply call std::getline() and block there waiting for user input before to send best move. Fortunately you do wait_for_stop_or_ponderhit() (which calls getline and evaluates the result against "stop", "ponderhit", and "quit") don't you? If you just called getline, you would incorrectly se...

Daniel Shawul wrote:I don't like too much politics. I am sure this post will be enjoyed by many there. If I were a moderator here, this post will be moved immediately. I have posted my complaint nevertheless.

+1