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
Resolve: Enable to use more than 3 wing guide curves #748
Conversation
Codecov Report
@@ Coverage Diff @@
## master #748 +/- ##
==========================================
+ Coverage 69.00% 69.42% +0.41%
==========================================
Files 423 425 +2
Lines 23177 23339 +162
==========================================
+ Hits 15994 16202 +208
+ Misses 7183 7137 -46
|
@joergbrech I know this PR is plenty of code, but could you have a look to it? |
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.
Nice! I still have a few small comments. What exactly is the purpose of approximating the input surfaces for the concatenation?
Addresses #687
Addresses #687
I also changed the tolerances slightly due to numerical issues.
The current implementation is a bit hacky, as we currently have to create a face to transform and then extract again the surface.
This commit concatenates the surfaces of a segment to provide a single surface to make the GetPoint functions work. Addresses #687
This checks, whether the mechanism is really independent of the order of guides.
This tests case check the get point functions on the guide curve case with four guide curves.
We had plenty of code disabled by the preprocessor flag NO_EXPLICIT_TE_MODELING. This code was not tested anymore and is probably buggy.
I also added a better doc string and improved the docstring of CTiglConcatSurfaces
1d31d1e
to
fcd82a3
Compare
@joergbrech All actions should be addressed now. I rebased finally onto master to be able to merge. |
Awesome! LGTM |
This PR enables to use more than 3 guide curves with TiGL.
Description
Several issues had been addressed:
How Has This Been Tested?
TODO: We still need a test example.xml file, that demonstrates the functionality. We might use the FFD or another aircraft.
Screenshots, that help to understand the changes(if applicable):
Checklist: