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

MultiAppNearestNodeTransfer bug with a target boundary when use mutilpe MPI ranks #18730

Closed
fdkong opened this issue Aug 30, 2021 · 0 comments · Fixed by #18731
Closed

MultiAppNearestNodeTransfer bug with a target boundary when use mutilpe MPI ranks #18730

fdkong opened this issue Aug 30, 2021 · 0 comments · Fixed by #18731
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.
Projects
FY21 NEAMS MultiApp Transfers

Comments

@fdkong
Copy link
Contributor

fdkong commented Aug 30, 2021

Bug Description

MultiAppNearestNodeTransfer did not transfer any data to a subapp which was not on rank 0 when we specify a target boundary.

Steps to Reproduce

Use something like the following block should reproduce the issue with multiple MPI ranks

[flux]
  type = MultiAppNearestNodeTransfer
  source_variable = flux
  direction = to_multiapp
  multi_app = sub
  variable = avg_flux
  target_boundary = 'surface'
[]

Impact

Can not run MultiAppNearestNodeTransfer with a target boundary when use mutilpe MPI ranks
@fdkong fdkong added T: defect An anomaly, which is anything that deviates from expectations. P: normal A defect affecting operation with a low possibility of significantly affects. labels Aug 30, 2021
@fdkong fdkong added this to TO DO in FY21 NEAMS MultiApp Transfers via automation Aug 30, 2021
fdkong added a commit to fdkong/moose that referenced this issue Aug 30, 2021
@fdkong
MultiAppNearestNodeTransfer: Check with its communicator when we want…
8b2ee97 
… to check if a boundary node is owned locally.

Closes idaholab#18730
@fdkong fdkong mentioned this issue Aug 30, 2021
Merged
fdkong added a commit to fdkong/moose that referenced this issue Aug 30, 2021
@fdkong
Added more tests when use source boundary and target boundary in tran…
92f981d 
…sfer

Closes idaholab#18730
FY21 NEAMS MultiApp Transfers automation moved this from TO DO to Done Aug 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.
Projects
No open projects
FY21 NEAMS MultiApp Transfers
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check a boundary node against its communicator in MultiAppNearestNodeTransfer fdkong/moose
2 participants
@fdkong @loganharbour