From: Joona Kiiski <joona.kiiski@gmail.com>
Date: Sun, 31 Mar 2013 17:35:45 +0000 (+0100)
Subject: Double Impact of Gain tables
X-Git-Url: https://git.sesse.net/?p=stockfish;a=commitdiff_plain;h=36c82b751ce227c05bfb0dc74c311a469f7f8ec4

Double Impact of Gain tables

Very unorthodox idea.

After 16000 games at 60"+0.05
ELO: 3.14 +-3.4 (95%) LOS: 96.6%
Total: 13407 W: 2278 L: 2157 D: 8972

bench: 4705335
---

diff --git a/src/search.cpp b/src/search.cpp
index ed029b4c..5ff23ad0 100644
--- a/src/search.cpp
+++ b/src/search.cpp
@@ -875,7 +875,7 @@ split_point_start: // At split points actual search starts from here
           // but fixing this made program slightly weaker.
           Depth predictedDepth = newDepth - reduction<PvNode>(depth, moveCount);
           futilityValue =  ss->staticEval + ss->evalMargin + futility_margin(predictedDepth, moveCount)
-                         + Gain[pos.piece_moved(move)][to_sq(move)];
+                         + 2 * Gain[pos.piece_moved(move)][to_sq(move)];
 
           if (futilityValue < beta)
           {