From 2940abdac83845aaa35592dc3450556b8b9a9c7f Mon Sep 17 00:00:00 2001 From: Marco Costalba Date: Tue, 29 Sep 2009 10:14:09 +0100 Subject: [PATCH] Print RootMoveList startup scoring This satisfies a specific user request of 28/8/2009 "The only issue I have is that during multiPV analysis, the depth 1 best move score is not reported by the engine (reporting for the best move begins at depth 2). I need it at depth 1 also. Would it be possible to make this modification in future versions? This would be of great help as otherwise I will have to use a lesser engine. The goal of my project is to calculate the ELO performance in a game and also the ELO rating of individual moves. For this I need depth 1 scores for lower rated performances. I intend to distribute the program for free upon completion. Thanks, Jack Welbourne" Signed-off-by: Marco Costalba --- src/search.cpp | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/search.cpp b/src/search.cpp index 24230ee7..7d8f8e87 100644 --- a/src/search.cpp +++ b/src/search.cpp @@ -658,6 +658,15 @@ namespace { // searchMoves are verified, copied, scored and sorted RootMoveList rml(p, searchMoves); + // Print RootMoveList c'tor startup scoring to the standard output, + // so that we print information also for iteration 1. + std::cout << "info depth " << 1 << "\ninfo depth " << 1 + << " score " << value_to_string(rml.get_move_score(0)) + << " time " << current_search_time() + << " nodes " << nodes_searched() + << " nps " << nps() + << " pv " << rml.get_move(0) << "\n"; + // Initialize TT.new_search(); H.clear(); -- 2.39.2