You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@lorisercole
Right now, the default binary output is a pickle dumped blob that, for a first time user, I think it is difficult to understand. Its content is:
Is it used by anyone or anywhere in the code? Is it safe to change the default binary output to the one equivalent to the human readable one but with numpy arrays?
The text was updated successfully, but these errors were encountered:
The content of the default bin format is simply an object with those attributes.
However, I would also avoid splitting the binary output in many files: it does not make sense.
I think we can simplify this by saving many arrays/variables in a numpy or json file (we need to test this). Like this:
Working on #37.
A first draft of SportranBinaryFile.
The useful storable attributes (input_parameters, settings, current,
current_resampled, output_results) should be further defined/corrected.
TODO:
- Define proper data structures: SportranInput, SportranSettings,
SportranOutput, ...
these can be seen as input/outputs of a "Workflow".
A workflow for example is defined in analysis.py
- Define functions that collect all the data useful to save the current
calculation/namespace and dumps it into a SportranBinaryFile.
- Define functions that extract and use the data of a SportranBinaryFile
to restore a calculation/data namespace.
@lorisercole
Right now, the default binary output is a pickle dumped blob that, for a first time user, I think it is difficult to understand. Its content is:
Is it used by anyone or anywhere in the code? Is it safe to change the default binary output to the one equivalent to the human readable one but with numpy arrays?
The text was updated successfully, but these errors were encountered: