\(\renewcommand\AA{\unicode{x212B}}\)
Properties File¶
The *.properties
Files¶
The Mantid framework is configured using up to three simple text *.properties
files that are read an interpreted every time the framework is started. These properties are not the same as the properties of algorithms. All three have the same format. The three files are read from first to last, with the values in subsequent *.properties
overriding those in previous ones.
Install directory
Mantid.properties
defines the default configuration that the development team suggest as sensible defaults. This file should not be altered by users as it will be replaced with every new install or upgrade of Mantid./etc/mantid.local.properties
is an optional, linux only file that sets shared defaults on a shared system. This is commonly used for setting thedefault.facility
,default.instrument
, anddatasearch.searcharchive
properties.Home directory
Mantid.user.properties
is where users may override any property setting in Mantid. Any Property setting in this file will override anything set in theMantid.properties
file. Simply either enter the property you wish to override in this file together with it’s new value. The change will take effect the next time Mantid is started. Subsequent installs or upgrades of Mantid will never alter this file.
The user properties file, Mantid.user.properties
, can be found
windows:
$MantidInstallDirectory\bin\Mantid.user.properties
linux and mac-os:
$HOME/.mantid/Mantid.user.properties
The Properties¶
Note
Use forward slash (/
) or double up on the number of backslash (\
) characters for all paths
Note
Boolean properties evaluate true
, 1
, and on
(case insensitive) as true
, all other values as false
.
General properties¶
Property |
Description |
Example value |
---|---|---|
|
A comma separated list of any categories of algorithms that should be hidden in Mantid. |
|
|
Action upon invoking a deprecated algorithm.
|
|
|
Action upon invoking the algorithm via one of
its deprecated aliases.
|
|
|
A semicolon separated list of function names that should be hidden in Mantid. |
|
|
Sets the maximum number of cores available to be used for threads for OpenMP. If zero it will use one thread per logical core available. |
|
Facility and instrument properties¶
Property |
Description |
Example value |
---|---|---|
|
The name of the default facility. The facility must be defined within the facilities.xml file to be considered valid. The file is described here. |
|
|
The name of the default instrument. The instrument must be defined within the facilities.xml file to be valid. The file is described here. |
|
|
The convention for converting to Q. For
|
|
Directory Properties¶
Property |
Description |
Example value |
---|---|---|
|
The directory where colormaps are located |
|
|
A semi-colon( |
|
|
The directory where data cache is located |
|
|
|
|
|
A default directory to use for saving files. the data archive |
|
|
The path to the directory that contains the Mantid plugin libraries |
|
|
A list of substrings to allow libraries to be skipped |
|
|
Where to load instrument definition files from |
|
|
The path to the directory containing the Mantid Qt-based plugin libraries |
|
|
Where to load parameter definition files from |
|
|
Python will also search the listed directories when importing modules. |
|
|
DEPRECATED: Use |
N/A |
|
A list of directories containing Python scripts that Mantid requires to function correctly. WARNING: Do not alter the default value. |
N/A |
|
A list of directories containing Python scripts that Mantid requires to function correctly. WARNING: Do not alter the default value. |
N/A |
|
A path to the location of the manifest file containing paths to each of the python algorithm files. WARNING: Do not alter the default value. |
N/A |
|
The directory of python .in files used as templates when generating python scripts from within an algorithm. |
N/A |
Logging Properties¶
The details of configuring the logging functionality within Mantid will not be explained here. For those who want more details look into the POCO logging classes and the Log4J logging module that it closely emulates. There are several comments in the properties file itself that explain the configuration we provide by default. However there are some obvious areas that you may want to alter and those properties are detailed below.
Property |
Description |
Example value |
---|---|---|
|
Defines the level of messages to be output by the system. The default is information, but this can be lowered to debug for more detailed feedback. |
|
|
Select where log messages appear.
|
|
The logging priority levels for the file logging and console logging can also be adjusted in python using the command:
#Set the log to debug level or above (7=debug)
ConfigService.setLogLevel(7)
#Set the log to critical level (2=critical) and do not log that it was changed
ConfigService.setLogLevel(2, True)
# Set the log to information and do not log that it was changed
ConfigService.setLogLevel("information", True)
More details on logging can be found in the developer docs .
Mantid Graphical User Interface Properties¶
Property |
Description |
Example value |
---|---|---|
|
Should Mantid use System Notifications for important messages? |
|
|
Enable cluster submission elements in GUIs |
|
|
Controls the use of OpenGL in rendering the “unwrapped” (flat) instrument views. |
|
|
Will reduce the size of the OpenGL display lists used when drawing the Instrument View. By doing this we reduce the chance that we will hit a memory allocation bug in the Mesa graphics library. This is only relevant if you using both Linux and a broken version of Mesa. |
|
|
Do not show ‘invisible’ workspaces |
|
|
Precision of hkl values shown in tables |
|
Network Properties¶
Property |
Description |
Example value |
---|---|---|
|
Network timeout for ICAT4 requests |
|
|
Check if there is a newer version available and
logs a message at |
|
|
Timeout for network requests when reading live data from ISIS (in seconds) |
|
|
Defines the default timeout for all network operations (in seconds). |
|
|
The timeout for network operations in the script repository, this overrides the default timeout. |
|
|
The api token for github calls used by
|
(not shown) |
|
Allows the system proxy to be overridden, if not set mantid will use the system proxy |
|
|
Must be set if proxy.host is set |
|
|
A sample url used to determine the system proxy to use on windows. |
|
|
Download new instrument definition files and
|
|
|
Enable usage reporting |
|
ScriptRepository Properties¶
Property |
Description |
Example value |
---|---|---|
|
Directory where ScriptRepository is Installed. |
|
|
Base URL for the remote script repository. |
|
|
CSV patterns for paths that should not be listed at ScriptRepository. |
|
|
URL for uploading scripts. |
|
Project Recovery¶
See project recovery for more details.
Property |
Description |
Example value |
---|---|---|
|
Whether project recovery is enabled |
|
|
How many checkpoints/backups to keep |
|
|
How often to save checkpoints in seconds |
|
Project Saving¶
Property |
Description |
Example value |
---|---|---|
|
Size in bytes of a project before the user is warned when saving |
|
Plotting Settings¶
Property |
Description |
Example value |
---|---|---|
|
Whether to show titles on plots |
|
|
Whether to show legend on plots |
|
|
The default font for labels and titles on plots. |
|
|
The default x scale on 1d plots |
|
|
The default y scale on 1d plots |
|
|
The default minimum x range |
|
|
The default maximum x range |
|
|
The default minimum y range |
|
|
The default maximum y range |
|
|
The default width of the lines that make the axes |
|
|
The default y scale on 1d plots |
|
|
Whether to show minor ticks on plots |
|
|
Whether to show minor gridlines on plots |
|
|
Whether to show ticks on the left side of the plot |
|
|
Whether to show ticks on the bottom of the plot |
|
|
Whether to show ticks on the right side of the plot |
|
|
Whether to show ticks on the top side of the plot |
|
|
Whether to show labels on the left side of the plot |
|
|
Whether to show labels on the bottom of the plot |
|
|
Whether to show labels on the right side of the plot |
|
|
Whether to show labels on the top side of the plot |
|
|
The default length of the major ticks |
|
|
The default width of the major ticks |
|
|
The default direction of the major ticks |
|
|
The default length of the minor ticks |
|
|
The default width of the minor ticks |
|
|
The default direction of the minor ticks |
|
|
Default Line style on 1d plots |
|
|
Default Draw style on 1d plots |
|
|
Default Line width on 1d plots |
|
|
Default marker style on 1d plots |
|
|
Default maker size on 1d plots |
|
|
Default cap size on error bars in 1d plots |
|
|
Default cap thickness on error bars in 1d plots |
|
|
Default number of error bars for every data point in 1d plots. Must be an integer |
|
|
Default width of error bars in 1d plots |
|
|
Default legend font size |
|
|
Default legend location |
|
|
Default colormap for image plots |
|
|
Default colorbar scale for image plots |
|
ISIS SANS Interface GUI Settings¶
Property |
Description |
Example value |
---|---|---|
|
Whether to show or hide plot results checkbox |
|
Algorithm Profiling Settings¶
See algorithm profiling for more details on using mantid profiler.
Property |
Description |
Example value |
---|---|---|
|
The filename for saving the log file. This can be the absolute
or relative path. This file is overwritten each session. Default
is |
|
|
Enable or disable writing the performance log. Write is disabled by default. |
|
Getting access to Mantid properties¶
To get access to, e.g. data saving path property from a C++ program one has to issue the following command:
path = ConfigService.getString("defaultsave.directory")
Modifying User Properties at Run Time¶
amend_config is a context manager that allows you to temporarily modify configuration settings related to a facility, instrument, data directory, or any additional keyword arguments. It ensures that the changes are only applied temporarily within the context and then restored to their original state when the context exits.
Category: Concepts