Further streamline connected pawn evaluation

Make even more clear what are the terms that
contribute to evaluate connected pawns, and
completely separate them from the weights
that are now fully looked up in a table.

For future tuning makes sense to init the table with
a formula instead of hard-code it. This allows to
reduce problem space cardinality and makes tuning
easier.

And fix a MSVC warning while there:
warning C4804: '>>' : unsafe use of type 'bool' in operation

No functional change.
This commit is contained in:
lucasart
2014-10-12 20:03:49 +01:00
committed by Joona Kiiski
parent 069073ea68
commit 91de6b0f37
3 changed files with 24 additions and 16 deletions

View File

@@ -37,6 +37,7 @@ int main(int argc, char* argv[]) {
Bitbases::init_kpk();
Search::init();
Eval::init();
Pawns::init();
Threads.init();
TT.resize(Options["Hash"]);