Gary,
I've noticed that all the model-free specific code in the 'multi'
directory has now been moved into the single module 'multi.commands'.
I had an idea for abstraction of that module from the dependence on
the model-free specific analysis and was wondering what you thought
about it. All the classes except 'MF_minimise_command' could be made
independent of model-free analysis simply by renaming. These could
then be used for other data analysis types in the future - exponential
curve fitting for the relaxation rates, SRLS, or what ever else would
like to use the code. The model-free specific code of the
'MF_minimise_command' class could be shifted into the
'specific_fns/model_free/' directory later on (the directory exists in
the current 1.3 line), or into the current
'specific_fns/model_free.py' file. The class could also be split into
a base class in 'multi' and derived class in 'specific_fns' for
further abstraction.
This idea would keep all the model-free specific code in the directory
'specific_fns/model_free' and keep the code of the 'multi' directory
sufficiently abstracted so that any type of analysis can take
advantage of it.
Cheers,
Edward
Abstraction of the code in the 'multi/commands.py' file of the 'multi_processor' branch.