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
{{ message }}
This repository has been archived by the owner on Nov 14, 2022. It is now read-only.
What?
We currently store some instrument-specific datasearch.directories in the Mantid.user.properties file. This is stored locally on our first compute node.
This is going to cause issues when we deploy more nodes because that file has to be maintained to be the same across multiple nodes.
A better approach would be to store that information in user/scripts/autoreduction for each instrument and load it either in the ReductionRunner or just at runtime in the reduce.py.
Another benefit of this is that it allows the users to configure Mantid directly (and potentially other software, so maybe user/scripts/autoreduction/configs is a good idea), rather than having to go through us to specify the newest required datasearch.directories (and other configs)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue raised by: [developer/user/project requirement]
What?
We currently store some instrument-specific
datasearch.directories
in theMantid.user.properties
file. This is stored locally on our first compute node.This is going to cause issues when we deploy more nodes because that file has to be maintained to be the same across multiple nodes.
A better approach would be to store that information in
user/scripts/autoreduction
for each instrument and load it either in the ReductionRunner or just at runtime in the reduce.py.Another benefit of this is that it allows the users to configure Mantid directly (and potentially other software, so maybe
user/scripts/autoreduction/configs
is a good idea), rather than having to go through us to specify the newest requireddatasearch.directories
(and other configs)The text was updated successfully, but these errors were encountered: