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
But it could be easily replaced by other kind of key-value stores, e.g., on-disk or distributed stores for simulations dealing with very large amount of data.
A new store would be created and assigned to each process of a model when initializing a simulation.
All properties created in each process (see #19) would therefore be simple object-to-store mappers.
The text was updated successfully, but these errors were encountered:
Currently each
Variable
object hold its own data. With #19 this woudn't be the case anymore, so we need to find an alternative solution.A common, writeable key-value store for all simulation data seems a nice and clean approach.
It could be as simple as a dictionary (in-memory store), e.g.,
But it could be easily replaced by other kind of key-value stores, e.g., on-disk or distributed stores for simulations dealing with very large amount of data.
A new store would be created and assigned to each process of a model when initializing a simulation.
All properties created in each process (see #19) would therefore be simple object-to-store mappers.
The text was updated successfully, but these errors were encountered: