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

Fixes for nodegroups running on multiple nodes #6285

Merged
merged 4 commits into from
Sep 14, 2024

Conversation

nilsdeppe
Copy link
Member

Proposed changes

There's still some issue I need to resolve, but these were the easy ones to find.

Upgrade instructions

Code review checklist

  • The code is documented and the documentation renders correctly. Run
    make doc to generate the documentation locally into BUILD_DIR/docs/html.
    Then open index.html.
  • The code follows the stylistic and code quality guidelines listed in the
    code review guide.
  • The PR lists upgrade instructions and is labeled bugfix or
    new feature if appropriate.

Further comments

Copy link
Contributor

@knelli2 knelli2 left a comment

Choose a reason for hiding this comment

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

Squash directly if you decide to change anything

Comment on lines -27 to +28
auto my_proxy = Parallel::get_parallel_component<ParallelComponent>(cache);
auto my_proxy = Parallel::get_parallel_component<ParallelComponent>(
cache)[Parallel::my_node<size_t>(cache)];
Copy link
Contributor

Choose a reason for hiding this comment

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

Just for my understanding, this used to do a broadcast to the whole collection for every element on this node? But that didn't matter because you only ran on a single node? And now you only send the messages to the local node?

Copy link
Member Author

Choose a reason for hiding this comment

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

Right, and the issue was that it would try to run an element that wasn't on its node and would then fail with "I can't find this element!"

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the explanation!

@nilsdeppe
Copy link
Member Author

I squashed the move of my_node. I agree, that's cleaner. I also rebased on develop. Thank you for the review!!

Comment on lines -27 to +28
auto my_proxy = Parallel::get_parallel_component<ParallelComponent>(cache);
auto my_proxy = Parallel::get_parallel_component<ParallelComponent>(
cache)[Parallel::my_node<size_t>(cache)];
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the explanation!

@nilsdeppe nilsdeppe merged commit 56f59bc into sxs-collaboration:develop Sep 14, 2024
21 of 23 checks passed
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

Successfully merging this pull request may close these issues.

2 participants