Skip to content
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

EOSPAC backend with serialization/deserialization #408

Closed
Yurlungur opened this issue Aug 24, 2024 · 1 comment · Fixed by #417
Closed

EOSPAC backend with serialization/deserialization #408

Yurlungur opened this issue Aug 24, 2024 · 1 comment · Fixed by #417
Assignees
Labels
interface Library interface work

Comments

@Yurlungur
Copy link
Collaborator

I am able to get the EOSPAC backend to work with serialization/deserialization and shared memory with a single instance. However in the case where eospac is constructed for multiple materials, There will be problems, because the library backend is global while an EOS object is per material. Worse, the de-serialization operation is global. There is no way to deserialize for only one material.

I am not sure what the solution to this is. We may wish to extend the EOSPAC object to load multiple materials at once. Alternatively perhaps there's a way to serialize and de-serialize a set of EOS objects, all at once. That could get around this problem.

@Yurlungur Yurlungur added the interface Library interface work label Aug 24, 2024
@Yurlungur Yurlungur self-assigned this Aug 24, 2024
@jhp-lanl
Copy link
Collaborator

Let's try destroying just the tables that the class owns and see what happens. We'll discuss with EOSPAC team.

@Yurlungur Yurlungur linked a pull request Sep 11, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interface Library interface work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants