Fix NLPP derivative in SoA #2179
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 tasks
|
After running similar I can reproduce the behavior in #2083, only this time I can use both SoA and AoS builds.
So I would consider the Li2 test passed and #2083 fixed by this PR. Thank you! Also, PR #2128 or something similar is needed to manage nonlocalpp_derivs with nexus, although it's good to have them now enabled by default. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Needs #2177 merged in first.
Close #2083.
I mostly relied on unit tests. The full simulation case I tried didn't make a significant difference using or not using NLPP derivatives.
@jtkrogel Could you check your Li2 case?