Depending on verbosity level given as option "-v=level", toulbar2
will output:
More...
Depending on verbosity level given as option "-v=level", toulbar2
will output:
- (level=0, no verbosity) default output mode: shows version number, number of variables and cost functions read in the problem file, number of unassigned variables and cost functions after preprocessing, problem upper and lower bounds after preprocessing. Outputs current best solution cost found, ends by giving the optimum or "No solution". Last output line should always be: "end."
- (level=-1, no verbosity) restricted output mode: do not print current best solution cost found
- (level=1) shows also search choices ("["search_depth problem_lower_bound problem_upper_bound sum_of_current_domain_sizes"] Try" variable_index operator value) with operator being assignment ("=="), value removal ("!="), domain splitting ("<=" or ">=", also showing EAC value in parenthesis)
- (level=2) shows also current domains (variable_index list_of_current_domain_values "/" number_of_cost_functions (see approximate degree in Variable elimination) "/" weighted_degree list_of_unary_costs "s:" support_value) before each search choice and reports problem lower bound increases, NC bucket sort data (see NC bucket sort), and basic operations on domains of variables
- (level=3) reports also basic arc EPT operations on cost functions (see Soft arc consistency and problem reformulation)
- (level=4) shows also current list of cost functions for each variable and reports more details on arc EPT operations (showing all changes in cost functions)
- (level=5) reports more details on cost functions defined in extension giving their content (cost table by first increasing values in the current domain of the last variable in the scope)
For debugging purposes, another option "-Z=level" allows one to monitor the search:
- (level 1) shows current search depth (number of search choices from the root of the search tree) and reports statistics on nogoods for BTD-like methods
- (level 2) idem
- (level 3) also saves current problem into a file before each search choice
- Note
toulbar2
, compiled in debug mode, can be more verbose and it checks a lot of assertions (pre/post conditions in the code)
-
toulbar2
will output an help message giving available options if run without any parameters