-
Notifications
You must be signed in to change notification settings - Fork 33
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
precompute natural coodinates. #300
precompute natural coodinates. #300
Conversation
Codecov Report
@@ Coverage Diff @@
## master #300 +/- ##
==========================================
- Coverage 98.98% 98.98% -0.01%
==========================================
Files 74 74
Lines 4155 4142 -13
==========================================
- Hits 4113 4100 -13
Misses 42 42
Continue to review full report at Codecov.
|
|
…re loop and pass it as a value.
f77f358
to
f981a57
Compare
I think this pull request is also good to go. Thanks for suggesting this @bangerth! Also related to the work done in #264 |
It is important to note that this pull request doesn't affect individual plugins at all, just plugin systems. Individual plugins still only get the Cartesian point. |
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, that's exactly what I had in mind. Nice to see that it makes a difference!
Found in #219. Moves the computation of the natural coordinates outside the feature loop and pass it as a reference. This will also contain a commit later to pass the natural coordinates by reference to the distance from curved planes function.
Although it currently looks kinda inconsistent to have a value called point and one called natural_coordinate, I don't think it is a good idea to make them consistent in this pull request, and focus here on the functional change.
edit: although I am open to changing the names in a last seperate commit here or in a new pull request.