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.

Sign up for GitHub

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

Jump to bottom

move the implementation of getModeledComm into a separate load model #1837

Closed
cz4rs opened this issue Jun 1, 2022 · 0 comments · Fixed by #1842
Closed

move the implementation of getModeledComm into a separate load model #1837

cz4rs opened this issue Jun 1, 2022 · 0 comments · Fixed by #1842
Assignees
@cz4rs

Comments

@cz4rs
Copy link
Contributor

cz4rs commented Jun 1, 2022 •
edited
Loading

Create a separate load model that implements current version of RawData::getModeledComm.

I'm not sure that the RawData model is the right place to compute and return modeled communication. Any thoughts, @PhilMiller?

Originally posted by @nlslatt in #1695 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cz4rs cz4rs

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

1835: fix remaining issues in RawData::getModeledComm DARMA-tasking/vt
1 participant
@cz4rs