Search Instrumentation for debugging
Moderator: Ras
-
dkappe
- Posts: 1636
- Joined: Tue Aug 21, 2018 7:52 pm
- Full name: Dietrich Kappe
Search Instrumentation for debugging
Has anyone used a compile time search instrumentation for debugging pruning, like NMP and RFP? Any tips on gets reported?
Fat Titz by Stockfish, the engine with the bodaciously big net. Remember: size matters. If you want to learn more about this engine just google for "Fat Titz".
-
jdart
- Posts: 4441
- Joined: Fri Mar 10, 2006 5:23 am
- Location: http://www.arasanchess.org
Re: Search Instrumentation for debugging
If compiled with -DSEARCH_STATS, Arasan can produce a report at the end of a search listing how many of each type of extension, reduction and pruning were done. It isn't terribly useful for debugging, but can give a general idea of what's happening. Static null pruning is generally the most common reason a node is pruned.
In addition, SEARCH_TRACE will produce complete tracing of all nodes, including the depth at each node, pruning decisions, etc. I found this quite useful for debugging, in the earlier stages of the program when there were more bugs.
In addition, SEARCH_TRACE will produce complete tracing of all nodes, including the depth at each node, pruning decisions, etc. I found this quite useful for debugging, in the earlier stages of the program when there were more bugs.