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

Use sparse communicator in distributed::Matrix #1549

Closed
wants to merge 2 commits into from

Conversation

MarcelKoch
Copy link
Member

@MarcelKoch MarcelKoch commented Feb 16, 2024

Based on: #1546

This PR enables using the sparse-communicator in the distributed::Matrix. It is only available if the C++17 standard is used, otherwise the old implementation will be used. But I will also deprecate the old implementation, so we won't maintain two separate code paths.

PR Stack:

@pratikvn
Copy link
Member

This probably needs to be rebased ?

@MarcelKoch MarcelKoch force-pushed the distributed-matrix-with-sparse-comm branch from f63b12a to 8efe6c2 Compare March 26, 2024 09:00
Comment on lines +526 to +530
[[deprecated(
"The pre-C++17 interface of the distributed::Matrix is "
"deprecated, please update your C++ standard to 17. ")]] mpi::request
communicate(const local_vector_type* local_b) const;
#endif
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the communicate function should be the responsibility of this class rather than the sparse_communicator class.

@MarcelKoch MarcelKoch force-pushed the distributed-matrix-with-sparse-comm branch 2 times, most recently from 17f51dc to 0f2abc1 Compare April 19, 2024 14:39
@MarcelKoch MarcelKoch force-pushed the distributed-matrix-with-sparse-comm branch from 0f2abc1 to 17f51dc Compare April 25, 2024 07:16
@MarcelKoch MarcelKoch closed this May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mod:core This is related to the core module.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants