Master module parameters

M_verbosity - integer (0).

[p]Master Module Parameters!M_verbosity

M_random_seed - integer (17).

[p]Master Module Parameters!M_random_seed A random seed just for the Master module.

upper_bound - double (no upper bound).

[p]Master Module Parameters!upper_bound This parameter is used if the user wants to artificially impose an upper bound (for instance if a solution of that value is already known).

lower_bound - double (no lower bound).

[p]Master Module Parameters!lower_bound This parameter is used if the user wants to artificially impose a lower bound.

upper_bound_estimate - double (no estimate).

[p]Master Module Parameters!upper_bound_estimate This parameter is used if the user wants to provide an estimate of the optimal value which will help guide the search. This is used in conjunction with the diving strategy BEST_ESTIMATE.

tm_exe, dg_exe - strings (``tm'', ``dg'').

[p]Master Module Parameters!tm_exe [p]Master Module Parameters!dg_exe The name of the executable files of the TM and DG modules. Note that the TM executable name may have extensions that depend on the configuration of the modules, but the default is always set to the file name produced by the makefile. If you change the name of the treemanager executable from the default, you must set this parameter to the new name.

tm_debug, dg_debug - boolean (both FALSE).

[p]Master Module Parameters!tm_debug [p]Master Module Parameters!dg_debug Whether these modules should be started under a debugger or not (see 5.6.2 for more details on this).

tm_machine - string (empty string).

[p]Master Module Parameters!tm_machine On which processor of the virtual machine the TM should be run. Leaving this parameter as an empty string means arbitrary selection.

do_draw_graph - boolean (FALSE).

[p]Master Module Parameters!do_draw_graph Whether to start up the DG module or not (see Section 5.6.4 for an introduction to this).

do_branch_and_cut - boolean (TRUE).

[p]Master Module Parameters!do_branch_and_cut Whether to run the branch and cut algorithm or not. (Set this to FALSE to run the user's heuristics only.)

mc_search_order - integer (MC_FIFO).

[p]Master Module Parameters!mc_search_order Use the fifo (MC_FIFO) or lifo (MC_LIFO) searh order during the multi criteria solution procedure.

mc_warm_start - boolean(FALSE).

[p]Master Module Parameters!mc_warm_start Whether to solve the corresponding problem of each iteration from a warm start loaded from a base iteration (which is the first iteration where gamma = 1.0 and tau = 0.0) or from scratch. Currently, this option is supported if only the supported solutions are desired to be found.

trim_warm_tree - boolean(FALSE).

[p]Master Module Parameters!trim_warm_tree Whether to trim the warm start tree before re-solving. This consists of locating nodes whose descendants are all likely to be pruned in the resolve and eliminating those descendants in favor of processing the parent node itself.

mc_compare_solution_tolerance - double(0.001).

[p]Master Module Parameters!mc_compare_solution_tolerance If the difference between the objective values of two solutions to be compared, during the bicriteria solution procedure, are less than this tolerance, then assume them to be equal.

mc_binary_search_tolerance - double(0).

[p]Master Module Parameters!mc_binary_search_tolerance The tolerance to be used to differentiate the gamma values if binary search is used during the bicriteria solution procedure. A value greater than zero will cause the binary search to be activated.