Table Of Contents
Previous topic
gromacs.core – Core functionality
Next topic
gromacs.environment – Run time modification of behaviour
gromacs.core – Core functionality
gromacs.environment – Run time modification of behaviour
The config module provides configurable options for the whole package; It mostly serves to define which gromacs tools and other scripts are exposed in the gromacs package and where template files are located. The user can configure GromacsWrapper by
In order to set up a basic configuration file and the directories a user should execute gromacs.config.setup() at least once. It will prepare the user configurable area in their home directory and it will generate a default global configuration file ~/.gromacswrapper.cfg (the name is defined in CONFIGNAME):
import gromacs
gromacs.config.setup()
If the configuration file is edited then one can force a rereading of the new config file with gromacs.config.get_configuration():
gromacs.config.get_configuration()
However, this will not update the available command classes (e.g. when new executables were added to a tool group). In this case one either has to reload() a number of modules (gromacs, gromacs.config, gromacs.tools) although it is by far easier simply to quit python and freshly import gromacs.
Almost all aspects of GromacsWrapper (paths, names, what is loaded) can be changed from within the configuration file. The only exception is the name of the configuration file itself: This is hard-coded as ~/.gromacswrapper.cfg although it is possible to read other configuration files with the filename argument to get_configuration().
Important configuration variables are
Directory to store user templates and rc files. The default value is ~/.gromacswrapper.
Search path for user queuing scripts and templates. The internal package-supplied templates are always searched last via gromacs.config.get_templates(). Modify gromacs.config.path directly in order to customize the template and qscript searching. By default it has the value ['.', qscriptdir, templatesdir]. (Note that it is not a good idea to have template files and qscripts with the same name as they are both searched on the same path.) path is updated whenever cfg is re-read with get_configuration().
When GromacsWrapper starts up it runs check_setup(). This notifies the user if any config files or directories are missing and suggests to run setup(). The check if the default set up exists can be suppressed by setting the environment variable GROMACSWRAPPER_SUPPRESS_SETUP_CHECK to ‘true’ (‘yes’ and ‘1’ also work).
Users will likely only need to run gromacs.config.setup() once and perhaps occasionally execute gromacs.config.get_configuration(). Mainly the user is expected to configure GromacsWrapper by editing the configuration file ~/.gromacswrapper.cfg (which has ini-file syntax as described in ConfigParser).
Prepare a default GromacsWrapper global environment.
This function can be run repeatedly without harm.
Reads and parses the configuration file.
Default values are loaded and then replaced with the values from ~/.gromacswrapper.cfg if that file exists. The global configuration instance gromacswrapper.config.cfg is updated as are a number of global variables such as configdir, qscriptdir, templatesdir, logfilename, ...
Normally, the configuration is only loaded when the gromacs package is imported but a re-reading of the configuration can be forced anytime by calling get_configuration().
| Returns : | a dict with all updated global configuration variables |
|---|
Check if templates directories are setup and issue a warning and help.
Returns True if all files and directories are found and False otherwise.
Setting the environment variable GROMACSWRAPPER_SUPPRESS_SETUP_CHECK to ‘true’ (‘yes’ and ‘1’ also work) silence this function and make it always return True.
Changed in version 0.3.1: Uses GROMACSWRAPPER_SUPPRESS_SETUP_CHECK to suppress output (useful for scripts run on a server)
Developers are able to access all configuration data through gromacs.config.cfg, which represents the merger of the package default values and the user configuration file values.
cfg is the instance of GMXConfigParser that makes all global configuration data accessible
Customized ConfigParser.SafeConfigParser.
Reads and parses the configuration file.
Default values are loaded and then replaced with the values from ~/.gromacswrapper.cfg if that file exists. The global configuration instance gromacswrapper.config.cfg is updated as are a number of global variables such as configdir, qscriptdir, templatesdir, logfilename, ...
Normally, the configuration is only loaded when the gromacswrapper package is imported but a re-reading of the configuration can be forced anytime by calling get_configuration().
Dict of variables that we make available as globals in the module.
Can be used as
globals().update(GMXConfigParser.configuration) # update configdir, templatesdir ...
Return the textual representation of logging level ‘option’ or the number.
Note that option is always interpreted as an UPPERCASE string and hence integer log levels will not be recognized.
Return option as a a list of strings.
Split on white space or separator. Sort for sort = True.
Return option as an expanded path.
A subset of important data is also made available as top-level package variables as described under Location of template files (for historical reasons); the same variable are also available in the dict gromacs.config.configuration.
Dict containing important configuration variables, populated by get_configuration() (mainly a shortcut; use cfg in most cases).
Default values are hard-coded in
name of the global configuration file.
Holds the default values for important file and directory locations.
The following functions can be used to access configuration data. Note that files are searched first with their full filename, then in all directories listed in gromacs.config.path, and finally within the package itself.
Find template file t and return its real path.
t can be a single string or a list of strings. A string should be one of
The first match (in this order) is returned. If the argument is a single string then a single string is returned, otherwise a list of strings.
| Arguments : | t : template file or key (string or list of strings) |
|---|---|
| Returns : | os.path.realpath(t) (or a list thereof) |
| Raises : | ValueError if no file can be located. |
Find template file(s) t and return their real paths.
t can be a single string or a list of strings. A string should be one of
The first match (in this order) is returned for each input argument.
| Arguments : | t : template file or key (string or list of strings) |
|---|---|
| Returns : | list of os.path.realpath(t) |
| Raises : | ValueError if no file can be located. |
Gromacs commands log their invocation to a log file; typically at loglevel INFO (see the python logging module for details).
File name for the log file; all gromacs command and many utility functions (e.g. in gromacs.cbook and gromacs.setup) append messages there. Warnings and errors are also recorded here. The default is gromacs.log.
The default loglevel that is still printed to the console.
The default loglevel that is still written to the logfilename.
load_* variables are lists that contain instructions to other parts of the code which packages and scripts should be wrapped.
Python list of all tool file names. Filled from values in the tool groups in the configuration file.
3rd party bundled analysis scripts and tools; this is a list of triplets of
(script name/path, command name, doc string)
(See the source code for examples.)
load_tools is populated from lists of executable names in the configuration file.
The tool groups are strings that contain white-space separated file names of Gromacs tools. These lists determine which tools are made available as classes in gromacs.tools.
A typical Gromacs tools section of the config file looks like this:
[Gromacs]
# Release of the Gromacs package to which information in this sections applies.
release = 4.5.3
# tools contains the file names of all Gromacs tools for which classes are generated.
# Editing this list has only an effect when the package is reloaded.
# (Note that this example has a much shorter list than the actual default.)
tools =
editconf make_ndx grompp genion genbox
grompp pdb2gmx mdrun
# Additional gromacs tools that should be made available.
extra =
g_count g_flux
a_gridcalc a_ri3Dc g_ri3Dc
# which tool groups to make available as gromacs.NAME
groups = tools extra
Template variables list files in the package that can be used as templates such as run input files. Because the package can be a zipped egg we actually have to unwrap these files at this stage but this is completely transparent to the user.
Directory to store user supplied queuing system scripts. The default value is ~/.gromacswrapper/qscripts.
Directory to store user supplied template files such as mdp files. The default value is ~/.gromacswrapper/templates.
Directory to store configuration files for remote queuing systems gromacs.qsub.Manager instances. The default value is ~/.gromacswrapper/managers.
GromacsWrapper comes with a number of templates for run input files and queuing system scripts. They are provided as a convenience and examples but WITHOUT ANY GUARANTEE FOR CORRECTNESS OR SUITABILITY FOR ANY PURPOSE.
All template filenames are stored in gromacs.config.templates. Templates have to be extracted from the GromacsWrapper python egg file because they are used by external code: find the actual file locations from this variable.
Gromacs mdp templates
These are supplied as examples and there is NO GUARANTEE THAT THEY PRODUCE SENSIBLE OUTPUT — check for yourself! Note that only existing parameter names can be modified with gromacs.cbook.edit_mdp() at the moment; if in doubt add the parameter with its gromacs default value (or empty values) and modify later with edit_mdp().
The safest bet is to use one of the mdout.mdp files produced by gromacs.grompp() as a template as this mdp contains all parameters that are legal in the current version of Gromacs.
Queuing system templates
The queing system scripts are highly specific and you will need to add your own into gromacs.config.qscriptdir. See gromacs.qsub for the format and how these files are processed.
The default template for SGE/PBS run scripts.