Analysis modules have an optional maintenance routine that can (optionally) get called from the main engine process (on it's own thread.)
This is currently broken since analysis modules are no longer loaded in the main engine process (they are loaded in the child worker processes).
I'd like to redesign this into a more simpler approach where you define a base Maintenance class separate from the AnalysisModule classes, and these are managed separately from the modules.
Analysis modules have an optional maintenance routine that can (optionally) get called from the main engine process (on it's own thread.)
This is currently broken since analysis modules are no longer loaded in the main engine process (they are loaded in the child worker processes).
I'd like to redesign this into a more simpler approach where you define a base Maintenance class separate from the AnalysisModule classes, and these are managed separately from the modules.