Closed svengoldberg closed 2 months ago
Attention: Patch coverage is 89.00000%
with 11 lines
in your changes missing coverage. Please review.
Project coverage is 70.03%. Comparing base (
8f02c5b
) to head (967c6c1
).
The following example is taken from the CPACS file uploaded in the issue. Here, the first picture is copied from the issue for reference. The second one is built from the same CPACS file, but the nodes fromRelativeCircumference
, toRelativeCircumference
are replaced by the new fromParameter
and toParameter
.
The kink is defined to be at parameter=0.3
, while the guide curve's respective argument is set to 0.28
. Nevertheless in the first picture, the guide curve appears after the kink on the profile.
In the second picture, the positions change. The yellow crosses mark the parameters 0.28
and 0.3
on the profile curve and that is just what is expected before.
Stabiler PR mein Bube!
Currently, the definition of (starting and end points of) fuselage guide curves is not consistent to user-defined parameterization for (e.g.) kinks. Those guide curve points are, up to now, defined based on the arc length of the start profile and end profile, respectively. While the user-defined parameterization can arbitrary differ from that (see issue #745).
This PR introduces the new CPACS nodes
fromParameter
andtoParameter
to account for this 'problem' to make it easier for users to sync guide curves with kinks. The node is implemented via achoice
element and the old implementation is kept as the default case to not get in the way with existing code, CPACS files and tests. Since the CPACS scheme is changed, it has to be thought about a CPACS PR, as well.TODO:
Fix issue #745
Checklist: