|
libkombilo
0.8
|
#include <search.h>
Public Member Functions | |
| std::string | asString () |
| void | validate () |
| std::vector< std::string > * | SGFTagsAsStrings () |
| ProcessOptions () | |
| sets default values which can be overwritten individually | |
| ProcessOptions (std::string s) | |
Data Fields | |
| bool | processVariations |
| bool | sgfInDB |
| std::string | rootNodeTags |
| a comma-separated list of those SGF tags which should be written to the database | |
| int | algos |
| algorithms to be used | |
| int | algo_hash_full_maxNumStones |
| int | algo_hash_corner_maxNumStones |
| int | professional_tag |
| whether to use "P" tag (0 = don't use; 1 = always use; 2 = use for players with 1p to 9p ranks) | |
You create an instance of this class by using the default constructor ProcessOptions() which will set reasonable default values. You can then change these values manually, if you want. Here are the relevant options
rootNodeTags This is a string containing a comma-separated list of the SGF tags which should be extracted from the files to the database. The default value is BR,CA,DT,EV,HA,KM,PB,PC,PW,RE,RO,RU,SZ,US,WR. sgfInDB Determines whether the complete sgf file will be stored in the database. (Default: true.) algos This option determines which algorithms will be available for pattern searches. It has the form of a bitmask. A minimal setting (processing is very fast, searching not so fast) is ALGO_FINALPOS | ALGO_MOVELIST . Usually you will want to use ALGO_FINALPOS | ALGO_MOVELIST | ALGO_HASH_FULL | ALGO_HASH_CORNER, which is the default value - this enables all the algorithms which are currently available. processVariations A boolean which says whether variations in games should be 'processed' (and hence will be available for pattern searches), or should be ignored. (This default value can be overridden in start_processing in order to enable variations for part of the database.) Default: true. algo_hash_full_maxNumStones Used to fine-tune the ALGO_HASH_FULL algorithm. Positions with more than algo_hash_full_maxNumStones will not be stored in the hashing table. A reasonable value seems to be something around 50 (the default value). For positions with more stones, the ALGO_FINALPOS algorithm is usually sufficiently fast anyway. algo_hash_corner_maxNumStones Same for ALGO_HASH_CORNER. Default: 20. professional_tag Determines whether/which games should be tagged as pro games. 0 = do not tag any games (default); 1 = tag all games; 2 = use for players with 1p to 9p ranks in the BR, WR SGF tags. 
1.8.11