-
Notifications
You must be signed in to change notification settings - Fork 97
Combined multifluid derivatives to reduce fluid kernel wrapper size #1779
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c928262
combined multifluid derivatives
francoishamon 73e01aa
fixed the testMultiFluid unit test
francoishamon 33f5c99
Merge branch 'develop' into refactor/hamon/multifluidDerivatives
francoishamon 6b2d7ca
Merge branch 'develop' into refactor/hamon/multifluidDerivatives
francoishamon 1609e7c
addressed review comments; no numerical diffs in integratedTests
francoishamon a5b5bd9
fixed unit test
francoishamon 3e72aad
fixed debug output
francoishamon fbf4f5d
Merge branch 'develop' into refactor/hamon/multifluidDerivatives
francoishamon 3910b37
Merge branch 'develop' into refactor/hamon/multifluidDerivatives
francoishamon b9b88e3
updated integratedTests submodule
francoishamon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Submodule integratedTests
updated
from 2e4590 to 25a069
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to bother you with this, but documenting why we need this
firstDerivcould be helpful (in which context we need this, e.g.)More important, instead of providing
firstDeriv, couldn'tv2be arange/sliceinstead? That would keep this function more mathematical and less implementation aware.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, as we discussed, it would be nice to passe a slice or range, but I don't know how to do it.
Here for example:
https://github.com/GEOSX/GEOSX/blob/3e72aadf62b7083dd7f434052f3d90c8f3470230/src/coreComponents/constitutive/fluid/MultiFluidBase.hpp#L722
my
phaseFrac.derivs[ip]is already a slice of sizenumComp+2, but I don't need first two entries (derivatives with respect to pressure and temperature). I would need a way to skip them, maybe by doing:Now that I am writing this, I should probably try that to see if it works.
For now, I added the Doxygen documentation in the
applyChainRulefunction to explain why we have to passDeriv::dC.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case
v2represents a general single-subscriptable entity, which may be a local array or anArraySlice. The latter may be not contiguous in memory, and in that case precomputing an offset pointer is not safe or correct. So we have to rely on the type'soperator[]to do the job at all times.Theoretically it's possible to write a
SubSlicetype which represents a sub-selection of anArraySlicealong one or more dimensions. The type would store the offset(s) internally and apply as needed. But we don't have it yet.