Skip to content
Snippets Groups Projects
Select Git revision
  • c067dadf345b4dce25144353c278d3c5adc41402
  • main default protected
  • fix/missing-api-documentation
  • feature/python_example_folder_update
  • beta_release protected
  • fix/revert-gitlab-config
  • fix/citationEcologicalAssessment
  • documentation/styleupdate
  • feature/lightMode
  • documentation/create_mission_xml
  • 28-empennage-design-update-documentation-according-to-workshop
  • documentation/fix-dot-equations
  • documentation/propulsion-design-module
  • documentation/gitlab-workflow
  • documentation/cost_estimation_update
  • documentation/mkdocs_python_update
  • documentation/tank_design_update
  • documentation/landing_gear_design_update
  • documentation/fuselage_design_update
  • documentation/global-header-file-setup
  • feature/mkdoxy
  • 0.5.0
22 results

software_architecture.md

Blame
  • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    software_architecture.md 1.08 KiB

    Software architecture {#softwarearchitecture}

    The software architecture is structured into various modules and packages, each handling specific tasks. Below is a description of the main components

    • strategies:

      • Strategies define the procedure of calculating the polars by initializing the aircraft geometry, calling methods and copying and processing data.
      • There are different strategies implemented, stored in the folders corresponding to the aircraft configuration (e.g., taw, bwb).
      • Each Strategy has a corresponding data.cpp for reading and writing data into the aircraft.xml and a config.cppfile for reading from the config.xml.
    • methods:

      • Methods are either derived from literature or rely on external calculation sofwares, data bases or surrogate models.
      • Methods are structured in a general way, so that they can be accessed by all strategies ranging over different aircraft configurations.
      • Methods are stored in the methods folder and need to be initialized, by geometry input, flight conditions and input parameters from the config file.