Currently the simulation results are stored inside of the simulation object (SimulatorBase). It would be much more sensible (and flexible) to store the simulation results in a special data storage object. Such objects even exists in Feeode: in the "storage" module
A minimal interface for storage classes, that meets the requirements of the simulator should be standardized. The necessary functionality would be:
- Put variables of one iteration (point in time) into storage.
- Put variables of one iteration (point in time) into storage.
- Put variables of one iteration (point in time) into storage.
- Maybe separate for state and algebraic variables
- Maybe separate for state and algebraic variables
- Get named variables out of storage (graph function)
- Get named variables out of storage (graph function)
- Get named variables out of storage (graph function)
- Store all data in a file (save function).
- Store all data in a file (save function).
- Store all data in a file (save function).
Look at library:
* http://pandas.pydata.org/ - However Pandas is from the finance industry.
See also:
Bug #603743 : Store program text with results
Bug #603596 : Store parameters with results
https://sourceforge.net/apps/trac/freeode/ticket/28
