We could single-out a metadata class (named HalFitData like now, or just Fit ?), and use this class to load and to save the fit data. This would allow users to save the fit result in a way that suits them.
If we change the structure of the repository according to #58, we could imagine that the default HalFitData class is included with the abstract classes in HAL.classes, but the user is allowed to overwrite it by putting a Metadata class with the same name in the 'module' folder.
We could single-out a metadata class (named HalFitData like now, or just Fit ?), and use this class to load and to save the fit data. This would allow users to save the fit result in a way that suits them.
If we change the structure of the repository according to #58, we could imagine that the default
HalFitDataclass is included with the abstract classes in HAL.classes, but the user is allowed to overwrite it by putting a Metadata class with the same name in the 'module' folder.