Skip to content

Use a common key-value store for simulation data #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
benbovy opened this issue Mar 6, 2018 · 1 comment
Closed

Use a common key-value store for simulation data #31

benbovy opened this issue Mar 6, 2018 · 1 comment
Milestone

Comments

@benbovy
Copy link
Member

benbovy commented Mar 6, 2018

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.,

store = {
    ('process_foo', 'param1'): 2,
    ('process_foo', 'var1'): np.array([2, 3, 4, 5]),
    ('process_bar', 'baz'): 4e-5
}

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.

@benbovy
Copy link
Member Author

benbovy commented May 7, 2018

Closed in #33

@benbovy benbovy closed this as completed May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant