Skip to content

Notes on how agglomeration works in MLMG #4602

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

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

ajnonaka
Copy link
Contributor

@ajnonaka ajnonaka commented Aug 6, 2025

Summary

Notes on how agglomeration works in MLMG

Additional background

Checklist

The proposed changes:

  • fix a bug or incorrect behavior in AMReX
  • add new capabilities to AMReX
  • changes answers in the test suite to more than roundoff level
  • are likely to significantly affect the results of downstream AMReX users
  • [x ] include documentation in the code and/or rst files, if appropriate

@ajnonaka ajnonaka requested a review from asalmgren August 6, 2025 17:24
boxes. Two advantages of using this option is that the bottom solver will become
smaller, and communication overhead is reduced.

- :cpp:`LPInfo::setAgglomerationGridSize(int)` (by default 8 in 1D, 16 in 2D, 32 in 3D)
Copy link
Member

Choose a reason for hiding this comment

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

If it's a GPU build, it's 32 be default. If it's a CPU build, it's 32 in 1D, 16 in 2D and 8 in 3D. (The order in the original commit is incorrect.)

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