Skip to content

Conversation

@ax3l
Copy link
Member

@ax3l ax3l commented Nov 14, 2025

Summary

Seen on Frontier at 6000 nodes (of course): if the particle locator decides that a particle is out-of-bounds, it used an inconsistent level for the particle in restart.

Now, it uses the currently loaded level consistently, with an invalid-marked tile.

Additional background

First seen by @titoiride

Co-authored-by: @atmyers
Co-authored-by: @RemiLehe
Co-authored-by: @titoiride

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
  • include documentation in the code and/or rst files, if appropriate

Seen on Frontier at 6000 nodes (of course): if the
particle locator decides that a particle is out-of-bounds,
it used an inconsistent level for the particle in restart.

Now, it uses the currently loaded level consistently, with
an invalid-marked tile.

Co-authored-by: Andrew Myers <[email protected]>
Co-authored-by: Remi Lehe <[email protected]>
Co-authored-by: Davide Terzani <[email protected]>
@ax3l ax3l requested a review from atmyers November 14, 2025 18:51
@ax3l ax3l added the bug label Nov 14, 2025
@atmyers atmyers merged commit 15c4a2c into AMReX-Codes:development Nov 14, 2025
73 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants