Skip to content
This repository has been archived by the owner on Nov 14, 2022. It is now read-only.

Instrument specific Mantid.user.properties #1494

Open
Pasarus opened this issue Aug 18, 2022 · 0 comments
Open

Instrument specific Mantid.user.properties #1494

Pasarus opened this issue Aug 18, 2022 · 0 comments

Comments

@Pasarus
Copy link
Member

Pasarus commented Aug 18, 2022

Issue raised by: [developer/user/project requirement]

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)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant