-
Notifications
You must be signed in to change notification settings - Fork 55
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
Adding sliding curves for DVGeoMulti #231
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #231 +/- ##
==========================================
+ Coverage 65.04% 65.18% +0.13%
==========================================
Files 47 47
Lines 12112 12123 +11
==========================================
+ Hits 7878 7902 +24
+ Misses 4234 4221 -13 ☔ View full report in Codecov by Sentry. |
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.
This is a great feature. Thanks for adding the test as well. I have a few minor comments
@sseraj, I addressed both of your comments. Also, thank you for spelling out pretty much all of the changes needed in the comments. Both things you said are correct. Please review my changes and mark the conversations as resolved. @bernardopacini, this PR is good for another round of reviews, correct? |
…pygeo into DVGeoMulti-SlidingCurves
I just updated the assertions as recommended by @sseraj, now should be good to go. |
Purpose
There are cases when using the intersection method in which a curve on a surface should be preserved to make sure that the patch does not change size or the curve is maintained to a certain shape. For example, maintaining the interface line between a propeller hub and nacelle is important to ensure a realistic boundary condition on each patch. This PR adds this sort of tracking.
These changes are actually made by @anilyil.
Expected time until merged
2 weeks.
Type of change
Testing
I have run this locally and also checked the derivatives to make sure the code is correct.
Checklist
flake8
andblack
to make sure the Python code adheres to PEP-8 and is consistently formattedfprettify
or C/C++ code withclang-format
as applicable