Input file sections¶
The PyRETIS input file described in detail in the user guide. The short version is:
The input file is TOML. It is organised into sections whose keywords are given values:
[section] keyword = "value"
Comments are marked with a #.
Section names and keywords are lower case, and the file is case-sensitive.
Below, we list the different sections that you can make use of in order to define your simulation:
Section |
Usage |
|---|---|
For defining the simulation we are going to run. |
|
For defining system properties. |
|
For defining a simulation box. |
|
For defining the initial state of particles. |
|
For defining a forcefield. |
|
For defining potential functions to use in the force field. |
|
For defining the simulation engine. |
|
For defining the order parameter. |
|
For defining settings for a RETIS simulation. |
|
For defining settings for a PPTIS or REPPTIS simulation. |
|
For defining settings for a TIS simulation. |
|
For configuring the infinite-swapping scheduler (parallel workers). |
|
For defining how the initial path is generated. |
|
For defining output settings. |
|
For defining custom unit systems. |
In addition, an analysis can be defined using:
Section |
Usage |
|---|---|
For defining an analysis. |
Keywords that take no effect on a run¶
Every keyword an input gives either takes effect on the run, or the input
is refused before the run starts, with a message that names each such
keyword and its value, says why it takes no effect, and names the keyword
to set instead when another keyword sets what it would set. A keyword can
take effect on one task and none on another: the [output] keywords of
the in-process output are read by the md tasks and refused by a
path-sampling run, whose scheduler writes its own output files. The rule
is declared in one place, pyretis.inout.key_table.NO_EFFECT, and the
settings parse of every input route applies it: a TOML input, and a
legacy .rst input, which pyretis run checks before it routes it
(a path-sampling one to its TOML twin). A value the table accepts states
what the run does (rgen = "pcg64", [engine] subcycles = 1): the
run takes it as it takes an input without the keyword. A run file
(output.toml) written by an earlier PyRETIS that holds such a
keyword continues and analyses: the keyword is left out when the file is
read, silently when its value is the one the settings parse gives or an
accepted one, and named in a warning otherwise.
In the table, a path-sampling run is a run of the task retis,
repptis, tis, pptis or explore, and the refusal applies
to make-tis-files as well, which writes the input of a tis run of
each ensemble.
Keyword |
Refused on |
Set instead |
|---|---|---|
|
Every task. |
|
|
Every task. |
|
|
Every task but a path-sampling run that picks the ensemble of
its moves: a |
|
|
A |
|
|
A path-sampling run. |
|
|
A path-sampling run. |
|
|
A path-sampling run, unless the value is |
|
|
A path-sampling run that kicks no path in process: a |
|
|
A path-sampling run, unless the value is |
|
|
Every run in which no ensemble runs it: an ensemble runs it when
its list in |
|
|
A path-sampling run. |
|
|
A path-sampling run. |
|
|
A path-sampling run other than |
|
|
A path-sampling run other than |
|
|
A path-sampling run other than |
|
|
A path-sampling run other than a |
|
|
A path-sampling run. |
|
|
An |
The run file output.toml of a run records none of these keywords.
The rgen keyword of [simulation], [system], [tis],
[engine], [engine0], [retis], [particles.velocity] and of
a numbered engine section names a random generator: "pcg64" (numpy’s PCG64),
"rgen" (numpy’s legacy MT19937), "mock", "rgen-borg" or
"mock-borg". An input whose rgen names no generator is refused
on every task, with the values that name one.
Notation for describing keywords¶
Each keyword entry is shown as:
keyword = DATA-TYPE
where keyword is the input-file key and DATA-TYPE is the kind of value
accepted by that key. The paragraph below each keyword explains what it controls.
When a keyword has a default value, the default is listed directly below the
description.
Example:
task = string
Selects the simulation task to run.
Default:
md
The data types used in the keyword reference are listed below.
DATA-TYPE |
Description |
Example |
|---|---|---|
string |
A string of characters, i.e. text. |
|
integer |
An integer. |
|
float |
A floating-point number |
|
boolean |
A boolean value
( |
|
dictionary |
A Python dictionary. |
|
list |
A Python list. |
|
tuple |
A Python tuple. |
|
None |
This represents an optional value |