<chapter name="Settings Scheme"> 
<h2>Settings Scheme</h2> 
 
The <code>Settings</code> class keeps track of all the flags, modes, 
parameters and words used during the event generation. As such, it 
serves all the <code>Pythia</code> program elements from one central 
repository. Accessing it allows the user to modify the generator 
behaviour. 
 
<p/> 
Each <code>Pythia</code> object has a public member <code>settings</code> 
of the <code>Settings</code> class. Therefore you access the 
settings methods as <code>pythia.settings.command(argument)</code>, 
assuming that <code>pythia</code> is an instance of the <code>Pythia</code> 
class. Further, for the most frequent user tasks, <code>Pythia</code> 
methods have been defined, so that <code>pythia.command(argument)</code> 
would work, see further below. 
 
<p/> 
The central section on this page is the Operation one. The preceding 
concepts section is there mainly to introduce the basic structure and 
the set of properties that can be accessed. The subsequent sections 
provide a complete listing of the existing public methods, which most 
users probably will have little interaction with. 
 
<h3>Concepts</h3> 
 
We distinguish eight kinds of user-modifiable variables, by the way 
they have to be stored: 
<ol> 
<li>Flags are on/off switches, and are stored as <code>bool</code>.</li> 
<li>Modes corresponds to a finite enumeration of separate options, 
and are stored as <code>int</code>.</li> 
<li>Parameters take a continuum of values, and are stored as 
<code>double</code>. The shorthand notation parm is used in the C++ 
code and XML tags.</li> 
<li>Words are simple character strings and are stored as 
<code>string</code>. No double quotation marks &quot; or braces { } 
may appear inside a word, and commas , will take a spcial role next 
so should also be avoided. Normally the input string is expected not to 
contain any blanks or equal signs, but if it does it must be enclosed 
in braces { }.</li> 
<li>Vectors of flags take a variable length, and are stored as 
<code>vector&lt;bool&gt;</code>. The shorthand notation fvec is used 
in the C++ code and XML tags. When the vector is input as a string 
it should be given as a comma-separated list, either containing 
no blanks or else enclosed in braces { }.</li> 
<li>Vectors of modes take a variable length, and are stored as 
<code>vector&lt;int&gt;</code>. The shorthand notation mvec is used 
in the C++ code and XML tags. When the vector is input as a string 
it should be given as a comma-separated list, either containing 
no blanks or else enclosed in braces { }.</li> 
<li>Vectors of parameters take a variable length and for each element 
a continuum of values, and are stored as <code>vector&lt;double&gt;</code>. 
The shorthand notation pvec is used in the C++ code and XML tag. 
When the vector is input as a string it should be given as a comma-separated 
list, either containing no blanks or else enclosed in braces { }.</li> 
<li>Vectors of words take a variable length, and are stored as 
<code>vector&lt;string&gt;</code>. The shorthand notation wvec is used 
in the C++ code and XML tags. When the vector is input as a string 
it should be given as a comma-separated list, either containing 
no blanks or else enclosed in braces { }.</li> 
</ol> 
Note the special role played by the braces { } to enclose words or lists 
that are allowed to contain blanks and equal signs, and of commas , to 
separate the fields of the list, in analogy with how C++ arrays can be 
initialized. You should not be using these three characters for any other 
purposes. Input of a vector can be split across several lines, until a 
close brace } is found that matches the open brace {. If no such is found 
the program will abort, so beware. The double quotation mark &quot; is 
avoided since it is already used for other purposes. Also note that all 
shorthands have been chosen four letters long. 
<p/> 
In general, each variable stored in <code>Settings</code> is associated 
with four kinds of information: 
<ul> 
<li>The variable name, of the form <code>class:name</code> 
(or <code>file:name</code>, usually these agree), e.g. 
<code>TimeShower:pTmin</code>. The class/file part usually identifies 
the <code>.xml</code> file where the variable is defined, and the part of 
the program where it is used, but such a connection cannot be strictly 
upheld, since e.g. the same variable may be used in a few different 
cases (even if most of them are not).</li> 
<li>The default value, set in the original declaration, and intended 
to represent a reasonable choice.</li> 
<li>The current value, which differs from the default when the user so 
requests.</li> 
<li>An allowed range of values, represented by meaningful 
minimum and maximum values. This has no sense for a <code>flag</code>, 
an <code>fvec</code> a <code>word</code> or a <code>wvec</code> 
(and is not used there), is 
usually rather well-defined for a <code>mode</code> or <code>mvec</code>, 
but less so for a <code>parm</code> or <code>pvec</code>. Often the allowed 
range exaggerates the degree of our current knowledge, so as not to restrict 
too much what the user can do. One may choose not to set the lower or 
upper limit, in which case the range is open-ended. 
<br/>Normally input values outside the allowed range are changed 
to the be at nearest limit. For <code>mode</code>s only, a further 
boolean is stored to tell whether this should be allowed, or whether 
out-of-range inputs should be forbidden, to the extent that the whole 
PYTHIA initialization would abort. The latter applies to those modes 
that have been defined with the <code>modepick</code> label in the 
<code>xmldoc/*.xml</code> files, and where maximal and minimal values 
have been specified. Such labels are used to represent a discrete set 
of options, and so any value outside the allowed range is just plain 
wrong. Also attempts to change <code>modefix</code> fixed-value 
<code>mode</code>s lead to aborts. By contrast those defined with 
<code>mode</code> or <code>modeopen</code> follow the normal rules 
of being reset to fall into the allowed range, without any warnings.</li> 
</ul> 
 
<p/> 
Technically, the <code>Settings</code> class is implemented with the 
help of eight separate maps, one for each kind of variable, with the 
variable <code>name</code> used as key. 
 
<h3>Operation</h3> 
 
The normal flow of setting values is: 
 
<ol> 
 
<p/> <li> 
When a <code>Pythia</code> object <code>pythia </code>is created, 
the member <code>pythia.settings</code> is asked to scan the files 
listed in the <code>Index.xml</code> file in the <code>xmldoc</code> 
subdirectory. 
 
<p/> 
In all of the files scanned, lines beginning with 
<code>&lt;flag</code>, <code>&lt;mode</code>, <code>&lt;parm</code>, 
<code>&lt;word</code>, <code>&lt;fvec</code>, <code>&lt;mvec</code>, 
<code>&lt;pvec</code> or <code>&lt;wvec</code> are identified, and the 
information on such a line is used to define a new flag, mode, parameter, 
word, or vector of flags, modes or parameters. To exemplify, consider a line 
<pre> 
&lt;parm name="TimeShower:pTmin" default="0.5" min="0.1" max="2.0"> 
</pre> 
which appears in the <code>TimeShower.xml</code> file, and there 
defines a parameter <code>TimeShower:pTmin</code> with default value 
0.5 GeV and allowed variation in the range 0.1 - 2.0 GeV. The min 
and max values are optional. 
<note>Important:</note> the values in the <code>.xml</code> files should 
not be changed, except by the PYTHIA authors. Any changes should be 
done with the help of the methods described below. 
</li> 
 
<p/> <li> 
Between the creation of the <code>Pythia</code> object and the 
<code>init</code> call for it, you may use several alternative 
methods to modify some of the default values. The same variable 
can be changed several times. If so, it is the last read value 
that counts. The two special 
<code><aloc href="Tunes">Tune:ee</aloc></code> and 
<code><aloc href="Tunes">Tune:pp</aloc></code> modes and the 
<code><aloc href="MainProgramSettings">Print:quiet</aloc></code> flag 
are expanded to change several settings in one go, but these obey 
the same ordering rules. 
 
<p/> 
a) Inside your main program you can directly set values with 
<pre> 
    pythia.readString(string) 
</pre> 
where both the variable name and the value are contained inside 
the character string, separated by blanks and/or a =, e.g. 
<pre> 
    pythia.readString("TimeShower:pTmin = 1.0"); 
</pre> 
The match of the name to the database is case-insensitive. Names 
that do not match an existing variable are ignored. A warning is 
printed, however. Strings beginning with a non-alphanumeric character, 
like # or !, are assumed to be comments and are not processed at all. 
Values below the minimum or above the maximum are set at 
the respective border. In extreme cases, where it is necessary to 
go outside the allowed range, "<code>FORCE=</code>" can replace 
the normal "<code>=</code>" separator to force the requested value, 
at own responsibility. For <code>bool</code> values, the following 
notation may be used interchangeably: 
<code>true = on = yes = ok = 1</code>, while everything else gives 
<code>false</code> (including but not limited to 
<code>false</code>, <code>off</code>, <code>no</code> and 0).<br/> 
 
<p/> 
b) The <code>Pythia</code> <code>readString(string)</code> method 
actually does not do changes itself, but sends on the string either 
to the <code>Settings</code> class or to <code>ParticleData</code>. 
The former holds if the string begins with a letter, the latter 
if it begins with a digit. (The exception is if an input list has been 
begun by an open brace { but no matching close brace } was present; 
then all subsequent non-empty input is directed to <code>Settings</code> 
until the close brace is found.) If desired, it is possible to communicate 
directly with the corresponding <code>Settings</code> method: 
<pre> 
    pythia.settings.readString("TimeShower:pTmin = 1.0"); 
</pre> 
In this case, changes intended for <code>ParticleData</code> 
would not be understood. 
 
<p/> 
c) Underlying the <code>settings.readString(string)</code> method are 
the settings-type-sensitive commands in the <code>Settings</code>, that 
are split by names containing <code>flag</code>, <code>mode</code>, 
<code>parm</code> or <code>word</code>. Thus, the example now reads 
<pre> 
    pythia.settings.parm("TimeShower:pTmin", 1.0); 
</pre> 
Such a form could be convenient e.g. if a parameter is calculated 
at the beginning of the main program, and thus is available as a 
variable rather than as a character string. 
Note that Boolean values must here be given as <code>true</code> or 
<code>false</code> i.e. there is less flexibility than with the 
previous methods. 
 
<p/> 
At the same level, there are several different methods available. 
These are included in the full description below, but normally the user 
should have no need for them. 
 
<p/> 
d) A simpler and more useful way is to collect all your changes 
in a separate file, with one line per change, e.g. 
<pre> 
    TimeShower:pTmin = 1.0 
</pre> 
Each line is read in as a string and processed with the methods already 
introduced. 
 
The file can be read by the 
<pre> 
    pythia.readFile(fileName); 
</pre> 
method (or an <code>istream</code> instead of a <code>fileName</code>). 
The file can freely mix commands to the <code>Settings</code> and 
<code>ParticleData</code> classes, and so is preferable. Lines with 
settings are handled by calls to the 
<code>pythia.settings.readString(string)</code> method. 
 
<p/> 
A file can make use of two extra features that are not available with the 
<code>readString(...)</code> method. One is the possibility to provide 
information for several distinct <aloc href="ProgramFlow">subruns</aloc>. 
The other is the possibility to comment out a section of lines in the file. 
The first line of the commented section should then begin by <code>/*</code> 
and the last begin by <code>*/</code>. This is reminiscent of the convention 
used in C++ and other languages, but is not as powerful, in that it is not 
possible to comment in or out parts of lines. It is only the first two 
non-blank characters of a line that are checked for a match, and a line 
beginning with <code>*/</code> is counted as part of the commented section. 
To avoid mistakes it is best to keep <code>/*</code> and <code>*/</code> 
on lines of their own, optionally followed by comments, but not by commands. 
</li> 
 
<p/> <li> 
In the <code>pythia.init()</code> call, many of the various other program 
elements are initialized, making use of the current values in the database. 
Once initialized, the common <code>Settings</code> database is likely not 
consulted again by these routines. It is therefore not productive to do 
further changes in mid-run: at best nothing changes, at worst you may 
set up inconsistencies. 
 
<p/> 
A routine <code>reInit(fileName)</code> is provided, and can be used to 
zero all the maps and reinitialize them from scratch. Such a call might be 
useful if several subruns are to be made with widely different parameter 
sets - normally the maps are only built from scratch once, namely when the 
<code>Pythia()</code> object is created. A more economical alternative is 
offered by <code>resetAll()</code>, however, which sets all variables back 
to their default values. 
</li> 
 
<p/> <li> 
You may at any time obtain a listing of all variables in the 
database by calling 
<pre> 
    pythia.settings.listAll(); 
</pre> 
The listing is strictly alphabetical, which at least means that names 
from the same file are kept together, but otherwise may not be so 
well-structured: important and unimportant ones will appear mixed. 
A more relevant alternative is 
<pre> 
    pythia.settings.listChanged(); 
</pre> 
where you will only get those variables that differ from their 
defaults. Or you can use 
<pre> 
    pythia.settings.list("string"); 
</pre> 
where only those variables with names that contain the string 
(case-insensitive match) are listed. Thus, with a string 
<code>shower</code>, the shower-related variables would be shown. 
 
<p/> 
The method <code>pythia.settings.output(key)</code> can return the 
value of a variable as a string, convenient for output. In a 
<code>readString</code> or <code>readFile</code> command, the 
construction <code>key = ?</code> will echo back the variable 
and its value, using this method. 
</li> 
 
<p/> <li> 
The above listings are in a tabular form that cannot be read 
back in. Assuming you want to save all changed settings (maybe because 
you read in changes from several files), you can do that by calling 
<pre> 
    pythia.settings.writeFile(fileName); 
</pre> 
This file could then directly be read in by 
<code>readFile(fileName)</code> in a subsequent (identical) run. 
Some variants of this command are listed below. 
</li> 
</ol> 
 
<br/><hr/> 
<h3>The public methods</h3> 
 
The complete list of methods and arguments is as follows. Most of the 
ones of interest to the user have already been mentioned above. 
Others can be used, but the same functionality is better achieved 
by higher-level routines. Some are part of the internal machinery, 
and should not be touched by user. 
 
<p/> 
Note that there is no <code>Settings::readFile(...)</code> method. 
The intention is that you should use <code>Pythia::readFile(...)</code>. 
It parses and decides which individual lines should be sent on to 
<code>Settings::readString(...)</code>. 
 
<method name="Settings::Settings()"> 
the constructor, which takes no arguments. Internal. 
</method> 
 
<method name="bool Settings::initPtr(Info* infoPtrIn)"> 
initialize pointer to error-message database. Internal. 
</method> 
 
<method name="bool Settings::init(string 
startFile = &quot;../share/Pythia8/xmldoc/Index.xml&quot;, 
bool append = false)"> 
read in the settings database. 
<argument name="startFile" 
default="&quot;../share/Pythia8/xmldoc/Index.xml&quot;"> 
read in the settings from all the files listed in this file, and 
assumed to be located in the same subdirectory. 
</argument> 
<argument name="append" default="off"> 
By default nothing is done if the method has already been called once. 
If true the further settings read in are added to the current database. 
</argument> 
<note>Note:</note> The method returns false if it fails. 
</method> 
 
<method name="bool init(istream& is, bool append = false)"> 
read in the settings from an input stream. This allows initialization 
without reading the xml files directly, which is useful for initialization 
of multiple copies of Pythia8. 
</method> 
 
<method name="bool Settings::reInit(string 
startFile = &quot;../share/Pythia8/xmldoc/Index.xml&quot;)"> 
overwrite the existing database. 
<argument name="startFile" 
default="&quot;../share/Pythia8/xmldoc/Index.xml&quot;"> 
read in the settings from all the files listed in this file, and 
assumed to be located in the same subdirectory. 
</argument> 
<note>Note:</note> The method returns false if it fails. 
</method> 
 
<method name="bool Settings::readString(string line, bool warn = true)"> 
read in a string, and change the relevant quantity in the database. 
It is normally used indirectly, via 
<code>Pythia::readString(...)</code> and 
<code>Pythia::readFile(...)</code>. 
<argument name="line"> 
the string to be interpreted as an instruction. 
</argument> 
<argument name="warn" default="on"> 
write a warning message or not whenever the instruction does not make 
sense, e.g. if the variable does not exist in the databases. 
</argument> 
<note>Note:</note> the method returns false if it fails to 
make sense out of the input string. 
</method> 
 
<method name="bool Settings::writeFile(string toFile, 
bool writeAll = false)"> 
</method> 
<methodmore name="bool Settings::writeFile(ostream& os = cout, 
bool writeAll = false)"> 
write current settings to a file or to an <code>ostream</code>. 
<argument name="toFile, os"> 
file or stream on which settings are written. 
</argument> 
<argument name="writeAll" default="off"> 
normally only settings that have been changed are written, 
but if true then all settings are output. 
</argument> 
<note>Note:</note> the method returns false if it fails. 
</methodmore> 
 
<method name="bool Settings::writeFileXML(ostream& os = cout)"> 
write out the information stored in xmldoc to be used later to 
initialize Settings through an input stream. 
</method> 
 
<method name="void Settings::listAll()"> 
</method> 
<methodmore name="void Settings::listChanged()"> 
</methodmore> 
<methodmore name="void Settings::list(string match)"> 
list all or changed settings, or a group of them. 
<argument name="match"> 
list all those settings where the name contains 
the <code>match</code> (sub)string (case-insensitive). 
</argument> 
</methodmore> 
 
<method name="string Settings::output(string key, bool fullLine = true)"> 
provide the value of a variable as a character string, whatever the type. 
If the variable does not exist then <code>unknown</code> is returned. 
<argument name="key"> 
the name of the settings variable. 
</argument> 
<argument name="fullLine" default="on"> 
If true then a whole "line" is returned, " <code>key = value\n</code>", 
while if false only the  <code>value</code> string. 
</argument> 
</method> 
 
<method name="vector&lt;string&gt; Settings::getReadHistory()"> 
Method to retrieve the history of <code>readString</code> commands that 
have been processed by the <code>Settings</code> instance, e.g. for 
inspection. Note that <code>readFile</code> command lines are interpreted 
by <code>readString</code> and thus also are listed, as are the 
<code>Settings</code> commands read by <code>Pythia::readString</code> 
and <code>Pythia::readFile</code>. 
</method> 
 
<method name="vector&lt;string&gt; Settings::getReadHistory(int subrun)"> 
Method to retrieve the history of <code>readString</code> commands that 
have been processed by <code>Settings</code>, for a specific subrun 
(see the section on <aidx href="MainProgramSettings">Main-Program 
Settings</aidx>). For <code>subrun = -1</code>, returns the 
<code>readString</code> history common to all subruns. For 
<code>subrun >= 0</code>, returns the history of <code>readString</code> 
commands for that specific subrun (omitting the common part). 
</method> 
 
<method name="void Settings::resetAll()"> 
reset all current values to their defaults. 
</method> 
 
<method name="bool Settings::isFlag(string key)"> 
</method> 
<methodmore name="bool Settings::isMode(string key)"> 
</methodmore> 
<methodmore name="bool Settings::isParm(string key)"> 
</methodmore> 
<methodmore name="bool Settings::isWord(string key)"> 
</methodmore> 
<methodmore name="bool Settings::isFVec(string key)"> 
</methodmore> 
<methodmore name="bool Settings::isMVec(string key)"> 
</methodmore> 
<methodmore name="bool Settings::isPVec(string key)"> 
</methodmore> 
<methodmore name="bool Settings::isWVec(string key)"> 
return true if an entry of the given name and kind 
exists, else false. 
</methodmore> 
 
<method name="void Settings::addFlag(string key, bool default)"> 
</method> 
<methodmore name="void Settings::addMode(string key, 
int default, bool hasMin, bool hasMax, int min, int max)"> 
</methodmore> 
<methodmore name="void Settings::addParm(string key, 
double default, bool hasMin, bool hasMax, double min, double max)"> 
</methodmore> 
<methodmore name="void Settings::addWord(string key, 
string default)"> 
</methodmore> 
<methodmore name="void Settings::addFVec(string key, 
vector&lt;bool&gt; default)"> 
</methodmore> 
<methodmore name="void Settings::addMVec(string key, 
vector&lt;int&gt; default, bool hasMin, bool hasMax, 
int min, int max)"> 
</methodmore> 
<methodmore name="void Settings::addPVec(string key, 
vector&lt;double&gt; default, bool hasMin, bool hasMax, 
double min, double max)"> 
</methodmore> 
<methodmore name="void Settings::addWVec(string key, 
vector&lt;string&gt; default)"> 
add an entry of the respective kind to the database. The name and default 
value(s) always has to be supplied, for <code>Mode</code>, <code>Parm</code>, 
<code>MVec</code> and <code>PVec</code> additionally if lower and/or 
upper limits are to be imposed and, if so, what those limit are. 
</methodmore> 
 
<method name="bool Settings::flag(string key)"> 
</method> 
<methodmore name="int Settings::mode(string key)"> 
</methodmore> 
<methodmore name="double Settings::parm(string key)"> 
</methodmore> 
<methodmore name="string Settings::word(string key)"> 
</methodmore> 
<methodmore name="vector&lt;bool&gt; Settings::fvec(string key)"> 
</methodmore> 
<methodmore name="vector&lt;int&gt; Settings::mvec(string key)"> 
</methodmore> 
<methodmore name="vector&lt;double&gt; Settings::pvec(string key)"> 
</methodmore> 
<methodmore name="vector&lt;string&gt; Settings::wvec(string key)"> 
return the current value(s) of the respective setting. If the name 
does not exist in the database, a value <code>false</code>, 
<code>0</code>, <code>0.</code>, <code>&quot; &quot;</code>, or a 
vector of length 1 and value <code>false</code>, <code>0</code>, 
<code>0.</code> or <code>&quot; &quot;</code>, respectively, is returned. 
</methodmore> 
 
<method name="bool Settings::flagDefault(string key)"> 
</method> 
<methodmore name="int Settings::modeDefault(string key)"> 
</methodmore> 
<methodmore name="double Settings::parmDefault(string key)"> 
</methodmore> 
<methodmore name="string Settings::wordDefault(string key)"> 
</methodmore> 
<methodmore name="vector&lt;bool&gt; Settings::fvecDefault(string key)"> 
</methodmore> 
<methodmore name="vector&lt;int&gt; Settings::mvecDefault(string key)"> 
</methodmore> 
<methodmore name="vector&lt;double&gt; Settings::pvecDefault(string key)"> 
</methodmore> 
<methodmore name="vector&lt;string&gt; Settings::wvecDefault(string key)"> 
return the default value(s) of the respective setting. If the name 
does not exist in the database, a value <code>false</code>, 
<code>0</code>, <code>0.</code>, <code>&quot; &quot;</code>, or a 
vector of length 1 and value <code>false</code>, <code>0</code>, 
<code>0.</code> or <code>&quot; &quot;</code>, respectively, is returned. 
</methodmore> 
 
<method name="map&lt;string, Flag&gt; Settings::getFlagMap(string match)"> 
</method> 
<methodmore name="map&lt;string, Mode&gt; Settings::getModeMap(string match)"> 
</methodmore> 
<methodmore name="map&lt;string, Parm&gt; Settings::getParmMap(string match)"> 
</methodmore> 
<methodmore name="map&lt;string, Word&gt; Settings::getWordMap(string match)"> 
</methodmore> 
<methodmore name="map&lt;string, FVec&gt; Settings::getFVecMap(string match)"> 
</methodmore> 
<methodmore name="map&lt;string, MVec&gt; Settings::getMVecMap(string match)"> 
</methodmore> 
<methodmore name="map&lt;string, PVec&gt; Settings::getPVecMap(string match)"> 
</methodmore> 
<methodmore name="map&lt;string, WVec&gt; Settings::getWVecMap(string match)"> 
return a map of all settings of the respective type that contain the 
string "match" in its name. 
</methodmore> 
 
<method name="void Settings::flag(string key, bool now, bool force = false)"> 
</method> 
<methodmore name="void Settings::mode(string key, int now, 
bool force = false)"> 
</methodmore> 
<methodmore name="void Settings::parm(string key, double now, 
bool force = false)"> 
</methodmore> 
<methodmore name="void Settings::word(string key, string now, 
bool force = false)"> 
</methodmore> 
<methodmore name="void Settings::fvec(string key, vector&lt;bool&gt; now, 
bool force = false)"> 
</methodmore> 
<methodmore name="void Settings::mvec(string key, vector&lt;int&gt; now, 
bool force = false)"> 
</methodmore> 
<methodmore name="void Settings::pvec(string key, vector&lt;double&gt; now, 
bool force = false)"> 
</methodmore> 
<methodmore name="void Settings::wvec(string key, vector&lt;string&gt; now, 
bool force = false)"> 
change the current value(s) of the respective setting to the provided 
new value(s). If lower or upper limits have been set and 
<code>force=false</code>, input values 
outside the allowed range are reinterpreted as being at the nearest 
limit. If <code>force = true</code>, upper and lower limits will be 
ignored, allowing to force values outside the allowed range (to be 
used with caution and at own responsibility!). Any key not found in the 
settings database will be ignored, unless <code>force = true</code>, in 
which case the missing key will be added to the database with the 
given value. 
</methodmore> 
 
<method name="void Settings::forceMode(string key, int now)"> 
</method> 
<methodmore name="void Settings::forceParm(string key, double now)"> 
</methodmore> 
<methodmore name="void Settings::forceMVec(string key, 
vector&lt;int&gt; now)"> 
</methodmore> 
<methodmore name="void Settings::forcePVec(string key, 
vector&lt;double&gt; now)"> 
as above, but do not check lower and upper limits, so that the current 
value(s) can be put outside the intended borders. 
<note>Note:</note> these methods have been superseded by the 
<code>force = true</code> option in the standard methods above. 
They are kept for backwards compatibility with version 8.223 and earlier 
but will be removed in a future major release. 
</methodmore> 
 
<method name="void Settings::resetFlag(string key)"> 
</method> 
<methodmore name="void Settings::resetMode(string key)"> 
</methodmore> 
<methodmore name="void Settings::resetParm(string key)"> 
</methodmore> 
<methodmore name="void Settings::resetWord(string key)"> 
</methodmore> 
<methodmore name="void Settings::resetFVec(string key)"> 
</methodmore> 
<methodmore name="void Settings::resetMVec(string key)"> 
</methodmore> 
<methodmore name="void Settings::resetPVec(string key)"> 
</methodmore> 
<methodmore name="void Settings::resetWVec(string key)"> 
reset the current value to the default one. 
</methodmore> 
 
<method name="bool Settings::getIsInit()"> 
return true if the database has been initialized, else false. 
</method> 
 
<method name="bool Settings::readingFailed()"> 
return true if some input could not be parsed, else false. 
</method> 
 
<method name="bool Settings::unfinishedInput()"> 
return true if input of a vector has been begun with am 
open brace { but no matching closing brace } has been found 
(so far), else false. 
</method> 
 
<method name="bool Settings::hasHardProc()"> 
return true if any hard processes are switched on, i.e. any process 
not belonging to the <code>SoftQCD</code> or <code>LowEnergyQCD</code> 
categories, else false. This method does not check whether Les Houches 
input is used, so that may have to be done separately. Since the method 
contains a hardcoding of what hard process types exist, in order to 
detect if any are on, it could be broken by the addition of new internal 
processes. It is therefore mainly useful for warning purposes, not for 
hard decisions. 
</method> 
 
</chapter> 
 
<!-- Copyright (C) 2020 Torbjorn Sjostrand --> 
