You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,18 +10,22 @@ A minimal configuration to specify using nightly builds of mantid installed in a
10
10
"CONDA_ENV": "mantid-dev"
11
11
}
12
12
```
13
-
For testing a configuration file can be supplied as a command line argument when running
13
+
For testing, a configuration file can be supplied as a command line argument when running
14
14
```shell
15
15
$ python scripts/livereduce.py ./livereduce.conf
16
16
```
17
-
If the instrument is not defined in the configuration file (default is `/etc/livereduce.conf`) the software will ask mantid for the default instrument using `mantid.kerel.ConfigService.getInstrument()` ([docs](https://docs.mantidproject.org/nightly/api/python/mantid/kernel/ConfigServiceImpl.html#mantid.kernel.ConfigServiceImpl.getInstrument)).
18
-
The default instrument is controlled in the [mantid properties files](https://docs.mantidproject.org/nightly/concepts/PropertiesFile.html) and is typically defined in `/etc/mantid.local.properties`.
17
+
If the instrument is not defined in the configuration file,
18
+
the software will ask mantid for the default instrument using
0 commit comments