Built-in Parameters¶
The OpenPathSampling CLI comes with a number of parameters (i.e., options and arguments) that can be passed to your commands. Be very shy about adding new parameters; in general, it is best to re-use the parameters that already exist. This is because re-using these parameters provides important consistency in the user experience.
Here are the parameters that are pre-defined in the parameters.py
file:
Parameter |
Flags |
|
Help |
---|---|---|---|
|
|
|
file to append to |
|
|
|
name of CV; may be used more than once |
|
|
|
identifer for the engine |
|
|
|
identifier for initial conditions (sample set or trajectory); may be used more than once |
|
|
|
identifier for initial snapshot |
|
|
|
|
|
|
|
name of CV; may be used more than once |
|
|
|
name or index of engine; may be used more than once |
|
|
|
name of index of ensemble; may be used more than once |
|
|
|
name or index of network; may be used more than once |
|
|
|
name or index of move scheme; may be used more than once |
|
|
|
tag for object; may be used more than once |
|
|
|
name or index of volume; may be used more than once |
|
|
No |
number of Monte Carlo trials to run |
|
|
|
output ncfile |
|
|
|
identifier for the move scheme |
|
|
|
name of state; may be used more than once |
If you need a parameter that isn’t in that list, it could either be:
a one-off for just your command: just use
click
.something to be reused: your should make an instance of a subclass of
AbstractLoader
, or duck-type something that behaves the same way. You need a methodMYPARAMTER.clicked()
that takes the an argumentrequired
and creates theclick
decorator, as well as a methodget
that extracts the correct form of the parameter you need.