Draft: wing_design (schueltke): restructured wing design module
Description
According to task #185 (closed), the wing_design module was adapted/exchanged to handle both, C++- and Python-Code. This was done by taking the Python framework and adapting the wing_design_conf.xml structure to it. This required changing the registration process of the tube_and_wing strategy in C++ code. The C++ code is then compiled via CMakeLists.txt of wing_design as wing_design_taw next to wing_design.py. This executable is then called in the tube_and_wing strategy of the new wing design. For BWB, currently, the MATLAB code from aircraft-references#9 is taken and downloaded via the CMakeLists.txt next to the wing_design.py as wing_design_bwb and called in the blended_wing_body strategy.
Currently, a wrong path is used in wing_design_bwb for fidelity. This is mentioned in issue #189 (closed).
Related Issue(s)
- Closes #185 (closed)
Other Changes
- Changed folder structure of
wing_design
Screenshots/Logs
The tube_and_wing folder holds next to the fidelity level also the C++ wing design module wing_design_taw because this module could also contain other fidelity strategies:
![]()
Testing Instructions
- Download this branch and build
wing_design - Copy it into the workflow after installation of new workflow created with MR rce-workflow!xxx
- Execute the workflow for
tube_and_wing(standard case) andblended_wing_body
The standard case should change nothing and BWB should end with an error, because changes in fuselage_design(#188 (closed)) and wing_design_bwb(#189 (closed)) are required.
Developer Checklist
-
Code has been tested locally and/or in pipeline. -
(if applicable) documentation updated. -
Merge conflicts resolved with the target branch.
Additional Notes
This new module needs to be integrated into the RCE Workflow, which will be done with task rce-workflow#26

