Resource folders are not tied to processors
The path we are taking for now is to have for each beamline:
- One processor (deriving from
XrpdProcessor
) - One resource folder
The problem is that since resource folders are not tied to processors, methods that are not overriden by the beamline-specific processor are still using the resource folder from XrpdProcessor
(i.e. resources/xrpd
).
See for example ensure_workflow_accessible
If the workflow path is not existing, it will use the one from resources/xrpd
, and this for every beamline-specific processor. This is less a problem here because it is a fallback but it can be a problem if we start relying on resource folders for future developments.
I wonder if the resource folder should not be a parameter of the processor ? Thoughts @denolf ?
Edited by Loic Huder