From: Marco Costalba <mcostalba@gmail.com>
Date: Wed, 15 Jul 2009 07:43:09 +0000 (+0100)
Subject: Use increased LMR horizont only after a null move
X-Git-Url: https://git.sesse.net/?p=stockfish;a=commitdiff_plain;h=fe523b2d18c0bb4533aad296fd44d504f67f2d4a

Use increased LMR horizont only after a null move

Revert to LMR horizont of 2 plies. Only if parent move
is a null move increase to 3 so to avoid the bad combination
of null move reduction + LMR reduction. This is a more
aggressive patch then previous one, but it seems we are
going in the wromg direction.

After 531 games result is not good:

Mod vs Orig  +123/=265/-143 48.12%  255.5/531  -13 ELO

Signed-off-by: Marco Costalba <mcostalba@gmail.com>
---

diff --git a/src/search.cpp b/src/search.cpp
index c8c8d4bd..08e3a997 100644
--- a/src/search.cpp
+++ b/src/search.cpp
@@ -1363,7 +1363,7 @@ namespace {
 
       // Try to reduce non-pv search depth by one ply if move seems not problematic,
       // if the move fails high will be re-searched at full depth.
-      if (    depth >= 3*OnePly
+      if (    depth >= (ss[ply-1].currentMove == MOVE_NULL ? 3 : 2) * OnePly
           &&  moveCount >= LMRNonPVMoves
           && !dangerous
           && !moveIsCapture