Output > spectra representation
For now we are saving data as represented:
This way of storing data is also closely related to the
This present several limitation:
- for now we have to define after each process which values (keys) of the spectra we want to save. Those keys has to be check because they might be some information missing. If we could find a process to configure this it might be usefull for the user.
- for ft (only at the moment) we save the result of ft as a dictionary instead of a numpy array because several ft process cannot be executed (not enought valid 'EXAFSKValues' values for running). I guess it will be disturbing for the user. Maybe we could provide an of numpy.nan
- the output might be different from the internal representation which is not an issue but won't help for any external coder.
Maybe it would interesting to store all the properties of the spectra when saving it at the end ?