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

ReduceOps: reset result readiness flag #3545

Merged
merged 1 commit into from
Sep 15, 2023

Conversation

WeiqunZhang
Copy link
Member

In #3421, a change was made to avoid a common mistake of calling ReduceData::value multiple times. Unfortunately, it breaks codes that using one ReduceOps with multiple ReduceData objects. This PR fixes both cases.

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

@WeiqunZhang
Copy link
Member Author

AMReX-FHD/FHDeX#141

@jgalenwang
Copy link

Hi Weiqun,

It's working now on my test case. Now all three directions are getting non-zero rhs. Thank you.

In AMReX-Codes#3421, a change was made to avoid a common mistake of calling
ReduceData::value multiple times. Unfortunately, it breaks codes that using
one ReduceOps with multiple ReduceData objects. This PR fixes both cases.
@ajnonaka ajnonaka merged commit 078905a into AMReX-Codes:development Sep 15, 2023
66 checks passed
@WeiqunZhang WeiqunZhang deleted the reduceops_init branch October 13, 2023 16:05
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.

3 participants