<commit_before>\label{parameter_file}
Parameters can be set in one of two ways. Some commonly-used parameters can be
set on the command line. To see a list of these, run \BB\ with no command-line
arguments. Other parameters must be set in a parameter file. The name of this
file is specified on the command line with ``\texttt{-f}''.  Each line of the
parameter file contains either a comment or two words -- a keyword and a
value, separated by white space. If the first word (sequence of
non-white-space characters) on a line is not a keyword, then the line is
considered a comment line. Otherwise the parameter corresponding to the
keyword is set to the listed value. Usually the keyword is the same as the
parameter name in the source code. Here we list the keywords, the type of
value that should be given with the keywords and the default value. A
parameter corresponding to keyword ``K'' in module ``P'' can also be set by
using the keyword ``P\_K''.

To make this list shorter, occasionally a comma separated list of parameters
is given if the meanings of those parameters are strongly
connected. For clarity, the constant name is sometimes given instead
of the numerical value for default settings and options. The
corresponding value is given in curly braces for convenience.

\subsection{Global parameters}
\begin{description}

\item[{\tt verbosity} -- integer (0).]
Sets the verbosity of all modules to the given value. In general,
the greater this number the more verbose each module is. Experiment
to find out what this means.

\item[{\tt random\_seed} -- integer (17).]
A random seed.

\item[{\tt granularity} -- double (1e-6).]
should be set to ``the minimum difference between two distinct
objective function values'' less the epsilon tolerance. E.g., if every
variable is integral and the objective coefficients are integral then
for any feasible solution the objective value is integer, so {\tt
granularity} could be correctly set to .99999.

\item[{\tt upper\_bound} -- double (none)].
The value of the best known upper bound.

\end{description}

\subsection{Master module parameters}
\begin{description}

\item[{\tt M\_verbosity} -- integer (0).]

\item[{\tt M\_random\_seed} -- integer (17).]
A random seed just for the Master module.

\item[{\tt upper\_bound} -- double (no 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).

\item[{\tt lower\_bound} -- double (no lower bound).]<commit_msg>parameter "infile_name" added<commit_after>\label{parameter_file}
Parameters can be set in one of two ways. Some commonly-used parameters can be
set on the command line. To see a list of these, run \BB\ with no command-line
arguments. Other parameters must be set in a parameter file. The name of this
file is specified on the command line with ``\texttt{-f}''.  Each line of the
parameter file contains either a comment or two words -- a keyword and a
value, separated by white space. If the first word (sequence of
non-white-space characters) on a line is not a keyword, then the line is
considered a comment line. Otherwise the parameter corresponding to the
keyword is set to the listed value. Usually the keyword is the same as the
parameter name in the source code. Here we list the keywords, the type of
value that should be given with the keywords and the default value. A
parameter corresponding to keyword ``K'' in module ``P'' can also be set by
using the keyword ``P\_K''.

To make this list shorter, occasionally a comma separated list of parameters
is given if the meanings of those parameters are strongly
connected. For clarity, the constant name is sometimes given instead
of the numerical value for default settings and options. The
corresponding value is given in curly braces for convenience.

\subsection{Global parameters}
\begin{description}

\item[{\tt verbosity} -- integer (0).]
Sets the verbosity of all modules to the given value. In general,
the greater this number the more verbose each module is. Experiment
to find out what this means.

\item[{\tt random\_seed} -- integer (17).]
A random seed.

\item[{\tt granularity} -- double (1e-6).]
should be set to ``the minimum difference between two distinct
objective function values'' less the epsilon tolerance. E.g., if every
variable is integral and the objective coefficients are integral then
for any feasible solution the objective value is integer, so {\tt
granularity} could be correctly set to .99999.

\item[{\tt upper\_bound} -- double (none)].
The value of the best known upper bound.

\item[{\tt probname} -- string (empty string)].
The name of the problem name.

\item[{\tt infile\_name} -- string (empty string)].
The name of the input file which was read by ``-F'' flag.

\end{description}

\subsection{Master module parameters}
\begin{description}

\item[{\tt M\_verbosity} -- integer (0).]

\item[{\tt M\_random\_seed} -- integer (17).]
A random seed just for the Master module.

\item[{\tt upper\_bound} -- double (no 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).

\item[{\tt lower\_bound} -- double (no lower bound).]
{'fraction_non_alphanumeric': 0.07938931297709924, 'fraction_numerical': 0.004961832061068702, 'mean_word_length': 4.063768115942029, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3661634', 'n_tokens_mistral': 1380, 'n_tokens_neox': 1321, 'n_words': 789}