Merge branch 'documentation/update_wing_design' of...

Merge branch 'documentation/update_wing_design' of git.rwth-aachen.de:unicado/unicado.gitlab.io into documentation/update_wing_design

docs/documentation/sizing/empennage_design/basic-concepts.md

@@ -2,31 +2,32 @@
 
 Designing an empennage for an aircraft is a challenging tasks. This topic provides basic information for empennages.
 
-If you are already familiar with the basic concepts, you can move on to the [Getting Started](getting-started.md).
+If you are already familiar with the basic concepts, you can move on to the [:octicons-arrow-right-16: Getting Started](getting-started.md).
 
 
 ### Available configurations
 Here you can find available empennage build methods from the _empennage\_design_ tool inside UNICADO.
+
 - _UNICADO is shipped natively with a conventional method for a tube and wing configuration._
 - _A basic Blended Wing body experimental method called vertical\_tails!_
 
-<pre class="mermaid">
+```mermaid
   graph LR;
     A[Empennage Design] -->B[Tube and Wing];
     B-->C[Conventional]
     B-->F[T-Tail]
     A-->D[Blended Wing body]
     D-->H[Vertical Tails]
-</pre>
+```
+
+!!! danger "Important"
+    Since the documentation might be delayed to the development progress - this graph might not have all information yet.
 
-<dl class="section bug">
-<dt>Important</dt>
-<dd>Since the documentation might be delayed to the development progress - this graph might not have all information yet</dd>
-</dl>
 ___
 
 ### Empennage Geometry
 Understanding the empennage geometry is an essential part. Below are key terms and their meanings:
+
 - Aspect Ratio (AR): The ratio of the span to the average chord length
   - _AR = b&sup2; / S_
   - _b : span_
@@ -49,6 +50,7 @@ Understanding the empennage geometry is an essential part. Below are key terms a
 
 ### Airfoil selection
 An airfoil defines the cross-sectional shape of an aerodynamic surface. The key characteristics include:
+
 - Camber: Airfoil curvature
   - _High camber  - generates more lift but comes with increased drag_
   - _No camber (symmetrical) often used for empennages_
@@ -58,4 +60,5 @@ An airfoil defines the cross-sectional shape of an aerodynamic surface. The key
 
 ### Spar Placements
 Spars are the one of the main structural elements inside the empennage to provide strength and rigidity
+
 - _Has effects on the control surface sizes_

docs/documentation/sizing/empennage_design/design-methods.md

+# Design methods
+On this page you get information about the methods used to design an empennage
+
+
+## Volume coefficient method
+The volume coefficient method which is used to generate the empennage. It is a classic method by selecting an appropriate Volumecoefficient where it creates a relation between the reference area and the empennage area.
+
+E.g. the volume coefficient for a conventional tail (vertical stabilizer ($vs$) and horizontal stabilizer ($hs$)) is given for the vertical stabilizer by:
+$$
+    C_{vs} = \frac{S_{vs}\cdot l_{vs}}{S_{ref}\cdot b} \qquad    C_{hs} = \frac{S_{hs}\cdot l_{hs}}{S_{ref}\cdot \overline{c}}
+$$
+
+where:
+
+- $C_{vs}$: Volumecoefficient
+- $S_{ref}$: Wing Reference Area
+- $S_{vs}$: Area vertical stabilizer
+- $b$: Wing span
+- $\overline{c}$: Wing Mac
+- $l_{vs}$: Distance between neutral point of wing and neutral point of vertical stabilizer
+
+This equation is the starting point for determining the geometry of a vertical stabilizer. A crucial part is to determine the root chord and the position of the neutral point of the vertical stabilizer based on it's geometry. In this case to keep the surface of the vertical stabilizer small to reduce the drag of the stabilizer, the leverarm $l_{vs}$ must be maximized. This leads to an root finding problem, when aspect ratio, taper ratio and sweep are predefined based on delta values or factors of the main wing properties.
+
+In this case the root chord is found by a newton algorithm, which maximizes the leverarm $l_{vs}$. As a predefined parameter, the maximum distance from the end of the fuselage most backward point which can be varied by the `rear_x_offset` parameter.
+
+From this point on, the geometry is fixed and the mass is computed by a method from the Flight Optimization System (Flops) which are empirical calculation methods. The spar positions and control device(s) positions can be determined by user in a relative position frame from the configuration file.
+
+!!! note
+    For a conventional tail or T-Tail, empirical volume coefficients are calculated when the volume coefficient of a tail element is set to a value of zero.

docs/documentation/sizing/empennage_design/getting-started.md

@@ -6,6 +6,7 @@ This guide gives you a step-by-step overview of the parameters which affects the
 The main method selection, _which_ empennage shall be designed comes from the _Aircraft Exchange File_. This is defined in the Block `requirements_and_specification` of the _Aircraft Exchange File_.
 
 Here you have a main element which will affect the empennage design inside `design_specification/configuration`:
+
 - `configuration_type`: This defines the aircraft configuration which the wing is build for
     - `tube_and_wing`
     - `blended_wing_body`
@@ -20,16 +21,18 @@ The configuration file of the Empennage Design tool `empennage\_design_conf.xml`
 The file comes with mode selectors and associated parameters to set which can vary.
 
 Parameters to chose:
+
 - `design_mode`:
     - `mode_0: design`: Designs an empennage from scratch
     - `mode_1: redesign`: Redesigns an existing empennage (not implemented - planned in a future release)
 
 As an example selection:
+
 - `configuration_type` → `tube_and_wing`
 - `empennage_type` → `conventional`
 
 This selects a conventional tail for a tube and wing configuration.
-<pre class="mermaid">
+```mermaid
 graph LR;
   A[Empennage Design] ==> B[Tube and Wing];
   B==>C[Conventional];
@@ -38,24 +41,23 @@ graph LR;
   D-->F[Vertical Tails];
   style B stroke-width:4px
   style C stroke:#0f0, stroke-width:4px
-</pre>
+```
 
 
 Each `empennage_type` will have it's own block to chose parameters from.
-<dl class="section todo">
-<dt>Note</dt>
-<dd>For default values or ranges, you should check the description of the parameters or the allowed ranges inside the configuration file</dd>
-</dl>
 
-<dl class="section invariant">
-<dt>Tip</dt>
-<dd>If you are missing some of the terms in here - take a look at [basic concepts](basic-concepts.md).</dd>
-</dl>
+!!! note
+    For default values or ranges, you should check the description of the parameters or the allowed ranges inside the configuration file
+
+!!! tip
+    If you are missing some of the terms in here - take a look at [:octicons-arrow-right-16: basic concepts](basic-concepts.md).
+
 
 ## Configuration parameters &rarr; General
 In this section you find parameters for an empennage. To keep it simple, a so called ID `tail_element` is part of each existing configuration. It defines basic parts for a classic volume coefficient method (low-fidelity).
 ### The Tail Elements parameters (ID Element)
 Each tail element has the following parameter which may differ from empennage type
+
 - `name`: Name of the element
 - `parameter`:
     - `offset`: Offset in multiple directions (differs for empennage type)
@@ -75,7 +77,7 @@ Each tail element has the following parameter which may differ from empennage ty
         - `param: deflection`: Set positive and negative deflection limits
         - `param: position`: Set position parameters like chordwise and spanwise position for inner and outer dimension of a control device
 
-### Tube and Wing: The Conventional Tail (low fidelity &rarr Volume Coefficient Method)
+### Tube and Wing: The Conventional Tail (low fidelity &rarr; Volume Coefficient Method)
 For a conventional tail, two tail elements are required! Here specific parts should be mentioned:
 
 - `tail_element ID="0"`:
@@ -91,17 +93,14 @@ For a conventional tail, two tail elements are required! Here specific parts sho
         - `centerline_y_offset`: Set offset from the centerline of the fuselage in y direction - should be zero
         - `centerline_z_offset`: Set offset from the centerline of the fuselage in z direction - should be zero
 
-<dl class="section todo">
-<dt>Note</dt>
-<dd>Control surfaces should be named here according to its usage e.g. horizontal stabilizer has an elevator and vertical stabilizer has a rudder.</dd>
-</dl>
+!!! note
+    Control surfaces should be named here according to its usage e.g. horizontal stabilizer has an elevator and vertical stabilizer has a rudder.
 
-<dl class="section bug">
-<dt>Important</dt>
-<dd>The user must be careful! You can choose values in a certain range, however always keep in mind _with great power comes great responsibility!_</dd>
-</dl>
+!!! danger "Important"
+    The user must be careful! You can choose values in a certain range, however always keep in mind _with great power comes great responsibility!_
 
-### Tube and Wing: The T-Tail (low fidelity &rarr Volume Coefficient Method)
+
+### Tube and Wing: The T-Tail (low fidelity &rarr; Volume Coefficient Method)
 For a T-tail, two tail elements are required! Here specific parts should be mentioned:
 
 - `tail_element ID="0"`:
@@ -117,20 +116,19 @@ For a T-tail, two tail elements are required! Here specific parts should be ment
         - `param: centerline_y_offset`: Set offset from the centerline of the fuselage in y direction - should be zero
         - `param: centerline_z_offset`: Set offset from the centerline of the fuselage in z direction - should be zero
 
-<dl class="section todo">
-<dt>Note</dt>
-<dd>Control surfaces should be named here according to its usage e.g. horizontal stabilizer has an elevator and vertical stabilizer has a rudder.</dd>
-</dl>
+!!! note
+    Control surfaces should be named here according to its usage e.g. horizontal stabilizer has an elevator and vertical stabilizer has a rudder.
+
 
-<dl class="section bug">
-<dt>Important</dt>
-<dd>The user must be careful! You can choose values in a certain range, however always keep in mind _with great power comes great responsibility!_</dd>
-</dl>
+!!! danger "Important"
+    The user must be careful! You can choose values in a certain range, however always keep in mind _with great power comes great responsibility!_.
 
 
-### Blended Wing Body: The Vertical Tails method (low fidelity &rarr Volume Coefficient Method)
+
+### Blended Wing Body: The Vertical Tails method (low fidelity &rarr; Volume Coefficient Method)
 For a blended wing body, only one tail element is required! This method is experimental and will only be applyable on the center body, so no checking of values is active to give you freedom to design!
 It will create a tail and it's symmetric partner mirrored on the centerline of the Blended Wing Body. So keep in mind to keep the `offset` section correctly.
+
 - `offset`:
     - `param: rear_x_offset`: Set offset between vertical stabilizer at root chord trailing edge to the end of the fuselage (center body wing) at specified y offset.
     - `param: centerline_y_offset`: Set offset from the centerline of the fuselage in y direction - should be NONE zero
@@ -138,37 +136,36 @@ It will create a tail and it's symmetric partner mirrored on the centerline of t
 
 A copied version will be generated automatically.
 
-<dl class="section warning">
-<dt>Warning</dt>
-<dd>Do not create a second element on the other side, it will be mirrored automatically.</dd>
-</dl>
+!!! warning
+    Do not create a second element on the other side, it will be mirrored automatically.
+
+!!! danger "Important"
+    The user must be careful! You can choose values in a certain range, however always keep in mind _with great power comes great responsibility!_.
 
-<dl class="section bug">
-<dt>Important</dt>
-<dd>The user must be careful! You can choose values in a certain range, however always keep in mind _with great power comes great responsibility!_</dd>
-</dl>
 
 
 ### Mass Calculation methods - general
 _Mass Calculation Methods_
+
 - `mass`: How to calculate the mass methods
     - `mode_0: flops`: Calculate the empennage mass according to FLOPS (_NASA Flight Optimization System_)
-    -
+
 ## Additional configurations
 Additionally, one has to define the common airfoil data paths inside the configuration file:
+
 - `common_airfoil_data_paths`: Defines the path, where to look for airfoils - normally a database
 
 ## Additional information and requirements
 The methods in the empennage design tool also require additional information on the wing and the fuselage from the requirements and specification block of the _Aircraft Exchange File_.
 
-<dl class="section bug">
-<dt>Important</dt>
-<dd>Keep in mind that the _empennage\_design_ tool generates an empennage as a part of an aircraft. This lets it rely on specific values, e.g. for defining the area inside the fuselage etc. This leads to mandatory items at this point:
+!!! danger "Important"
+    Keep in mind that the _empennage\_design_ tool generates an empennage as a part of an aircraft. This lets it rely on specific values, e.g. for defining the area inside the fuselage etc. This leads to mandatory items at this point:
+
     - A specified fuselage - here length and width and height are necessary to determine wing geometry and wing position
-- Initial Maximum Takeoff Mass (MTOM) - for determination of the wing area necessary based on the wing loading (only if method is selected)</dd>
-</dl>
+    - Initial Maximum Takeoff Mass (MTOM) - for determination of the wing area necessary based on the wing loading (only if method is selected)
+
 
 Please keep in mind, that the module is still in beta phase and you can gratefully contribute to the
 
 ## Next Steps
-The next step is to run the _empennage\_design_ tool. So let's get your wings from [Design your first empennage](dfe.md)
+The next step is to run the _empennage\_design_ tool. So let's get your empennage from [:octicons-arrow-right-16: Run your first   design](run-your-first-empennage-design.md)

docs/documentation/sizing/empennage_design/index.md

 # Introduction {#mainpage}
 The empennage is an essential part of the aircraft. The _empennage\_design_ tool is one of the core design tools in UNICADO and enables the workflow to design an empennage according to specified requirements and design specifications.
 
+According to the workflow, the tool requires a valid _Aircraft Exchange File_ with inputs from the tools _initial\_sizing_, _fuselage\_design_ and _wing\_design_.
+
+```mermaid
+	flowchart LR
+		A@{ shape: sm-circ } --> B["..."]
+		B --> D@{ shape: rounded, label: "Wing Design"}
+    D --> E@{ shape: rounded, label: "Empennage Design"} --> F["..."]
+
+		style F stroke: none, fill: none
+		style B stroke: none, fill: none
+    style D stroke: #9e0f0f,fill: #9e0f0f
+```
+
+
+## Summary of features
+Here is a quick overview of what the tool is currently capable of including a preview which is planned:
+
+| Configuration     | Empennage Type | Method            |                 Status                  |
+|-------------------|----------------|-------------------|:---------------------------------------:|
+| tube-and-wing     | Conventional   | Volumecoefficient | running :octicons-feed-issue-closed-16: |
+| tube-and-wing     | T-Tail         | Volumecoefficient | running :octicons-beaker-16: |
+| blended-wing-body | Vertical-Tails | Volumecoefficient |    running (experimental)  :octicons-beaker-16:    |
+
 ## A User's Guide to Empennage Design
 The _empennage\_design_ tool will help you design various empennages for classical configurations to blended wing body confiugartions. This user documentation will guide you through all necessary steps to understand the tool as well as the necessary inputs and configurations to create a new empennage from scratch.
 
 The following pages will guide you through the process of generating your first empennage within UNICADO:
 
-- [Basic Concepts](basic-concepts.md)
-- [Getting Started](getting-started.md)
-- [Design your first empennage](dfe.md)
+[:octicons-arrow-right-16: Basic Concepts](basic-concepts.md)   
+[:octicons-arrow-right-16: Getting Started](getting-started.md)   
+[:octicons-arrow-right-16: Design Methods](design-methods.md)   
+[:octicons-arrow-right-16: Design your first empennage](run-your-first-empennage-design.md)   
 
 So let's get started!
 
@@ -19,10 +43,9 @@ If you are familiar with these concepts and want to contribute - head over to th
 
 The following pages will help you understand the code structure:
 
-- [Prerequisites](prerequisites.md)
-- [Build the code](build-the-code.md)
-- [Empennage module structure](wing-module-structure.md)
-- [Available methods](available-methods.md)
-- [Method template](method-template.md)
+[:octicons-arrow-right-16: Prerequisites](prerequisites.md)   
+[:octicons-arrow-right-16: Build the code](build-the-code.md)   
+[:octicons-arrow-right-16: Empennage module structure](empennage-module-structure.md)   
+[:octicons-arrow-right-16: Method template](method-template.md)   
 
 We appreciate it!

docs/documentation/sizing/empennage_design/dfe.md → docs/documentation/sizing/empennage_design/run-your-first-empennage-design.md

 # Design your first empennage {#design-your-first-empennage}
 Let's dive into the fun part. In this guide we will create an empennage for a classic tube and wing configuration with a conventional empennage design method.
 
-  - [Requirements:](#requirements) - Information on tool requirements
-  - [Design parameters:](#design-parameters) - Information on design parameters
-  - [Tool execution:](#tool-execution) - Tool execution information
-  - [Reporting](#reporting) - Wing Design tool report information
-  - [Changing parameters](#changing-parameters) - The fun part! Let's change parameters
-  - [Troubleshooting](#troubleshooting) - Something went wrong? Maybe you are not the first one!
+[:octicons-arrow-right-16: Requirements:](#requirements) - Information on tool requirements
 
-The empennage will be part of a generic tube and wing aircraft which is a look-a-like A320.
+[:octicons-arrow-right-16: Design parameters:](#design-parameters) - Information on design parameters
+
+[:octicons-arrow-right-16: Tool execution:](#tool-execution) - Tool execution information
+
+[:octicons-arrow-right-16: Reporting](#reporting) - Wing Design tool report information
 
-The wing will be part of a generic tube and wing aircraft which is a look-a-like A320.
+[:octicons-arrow-right-16: Changing parameters](#changing-parameters) - The fun part! Let's change parameters
+
+[:octicons-arrow-right-16: Troubleshooting](#troubleshooting) - Something went wrong? Maybe you are not the first one!
+
+The empennage will be part of a generic tube and wing aircraft which is a look-a-like A320.
 
 ## Requirements
-Therefor we use an _Aircraft Exchange File_ where the tools _initial\_sizing_ and _fuselage\_design_ already run.
+Therefor we use an _Aircraft Exchange File_ where the tools _initial\_sizing_, _fuselage\_design_ and _wing\_design_ already run.
+
+```mermaid
+	flowchart LR
+		A@{ shape: sm-circ } --> B["..."]
+		B --> D@{ shape: rounded, label: "Wing Design"}
+    D --> E@{ shape: rounded, label: "Empennage Design"} --> F["..."]
+
+		style F stroke: none, fill: none
+		style B stroke: none, fill: none
+    style D stroke: #9e0f0f,fill: #9e0f0f
+```
 
 From the _Aircraft Exchange File_ we have the following information:
 
 From the Requirements block:
+
 Parameter            |         Value
 :--------------------|-------------:
 A/C Type             |         CeraS
@@ -43,21 +58,22 @@ Taper Ratio | 0.17
 Quarter-Chord Sweep | 27°
 Dihedral | 5°
 
-<dl class="section todo">
-<dt>Note</dt>
-<dd>Parameters of the fuselage arenot listed - however, it has a length of ~37m and a width of ~4m.</dd>
-</dl>
+!!! note
+    Parameters of the fuselage are not listed - however, it has a length of ~37m and a width of ~4m.
+
  
 ## Design parameters
 Empennage Design tool parameters for conventional low method
 
 _Design and mass mode_
+
 Parameter     |                    Value
 :-------------|------------------------:
 `design_mode` | `mode_0` &rarr; `design`
 `mass_mode`   |  `mode_0` &rarr; `flops`
 
 _Tail Element `ID = 0`_
+
 Parameter | Value
 :-- | --:
 `name` | `vertical_stabilizer`
@@ -73,6 +89,7 @@ Parameter | Value
 `control_devices` | `((rudder, -25°, 25°,0.2,0.7,1.0,0.9,0.7,1.0))`
 
 _Tail Element `ID = 1`_
+
 Parameter | Value
 :-- | --:
 `name` | `horizontal_stabilizer`
@@ -88,7 +105,7 @@ Parameter | Value
 `control_devices` | `((elevator, -25°, 25°,0.2,0.7,1.0,0.9,0.7,1.0))`
 
 ## Tool execution
-The tool can be executed from console directly if all paths are set (see [How to run a tool](howToRunATool.md)).
+The tool can be executed from console directly if all paths are set (see [:octicons-arrow-right-16: How to run a tool](howToRunATool.md)).
 
 We go through the tool output step by step
 ```
@@ -169,15 +186,12 @@ The resulted output in the console will not change, however you see that the rud
 
 Soo .... Now it is your turn!
 
-<dl class="section invariant">
-<dt>Tip</dt>
-<dd>Start by changing only one parameter at once. There might be interactions with other parameters, so don't rush!</dd>
-</dl>
+!!! tip
+    Start by changing only one parameter at once. There might be interactions with other parameters, so don't rush!
+
 
 ## Troubleshooting
 - Tool does not run properly:
   - Make sure you have all the paths set up correctly and the specified elements exist!
 - Tool is not there:
-  - You can build the tool directly from scratch - see therefor [How to build a tool](howToBuildATool.md)
-
-
+  - You can build the tool directly from scratch - see therefor [:octicons-arrow-right-16: How to build a tool](howToBuildATool.md)
\ No newline at end of file

docs/documentation/sizing/systems_design/getting-started.md

 # Getting Started
-This guide will show you how to use **systems_design**, which requires you to define a [system architecture](\ref defining_architecture) and to define [specific parameters for each system](systems.md) in the the configuration file `systems_design_conf.xml` (also _configXML_). Since the required power of the systems is calculated for each mission step, **systems_design** requires a mission file (e.g. `design_mission.xml`). Additionally, input parameters from the aircraft exchange file (or _acXML_) from the following areas are required:
-* paths to mission files
-* overall masses (MTOM, OME, MME, wing loading)
-* performance data (maximum operating velocity, maximum operating mach number, maximum operating altitude, design range)
-* landing gear
-* wing
-* empennage
-* fuselage
-* nacelles
-* tank
-* propulsion
-* number of flight and cabin crew
-
-**systems_design** has three modes, which are explained [here](\ref modes) in more detail. The mode can be selected in `module_configuration_file/program_settings/mission_mode` and defines which mission file is used for the calculation of the required power (design, study or requirement mission). For the design mission the systems are also sized, i.e. their masses are calculated.
-
-\anchor defining_architecture
+This guide will show you how to use **systems_design**.
+
+## Step-by-step
+
+It is assumed that you have the `UNICADO Package` installed including the executables and the engine database. In case you are a developer, you need to build the tool first (see [build instructions on UNICADO website](../../../get-involved/build/cpp/)).
+
+1. Create a dummy `aircraft_exchange_file` (minimal required input see [here](#settings-and-outputs-settingsandoutputs))
+2. Fill out the configuration file - change at least:
+    - in `control_settings` 
+        - `aircraft_exchange_file_name` and `aircraft_exchange_file_directory` to your respective settings
+        - `console_output` at least to `mode_1`
+        - `plot_output` to false or make sure gnuplot can be found (`gnuplot_path`)
+3. Open terminal and run **systems_design**
+
+The following will happen:
+- you see output in the console window
+- a HTML report is created in the directory of `aircraft_exchange_file_directory` (no plots if they are turned off)
+- results are saved in the _acXML_ file
+
+## Settings and outputs
+
+Three input files are required for **systems_design**:
+
+- the aircraft exchange file (or _acXML_) with values for the following areas:
+    - paths to mission files
+    - overall masses (MTOM, OME, MME, wing loading)
+    - performance data (maximum operating velocity, maximum operating mach number, maximum operating altitude, design range)
+    - landing gear
+    - wing
+    - empennage
+    - fuselage
+    - nacelles
+    - tank
+    - propulsion
+    - number of flight and cabin crew
+- the configuration file `initial_sizing_conf.xml` (or _configXML_) includes
+    - control settings (e.g. enable/disable generating plots)
+    - program settings (e.g. define system architecture, set parameters for individual systems)
+- the mission file (`design_mission.xml`, `study_mission.xml` or `requirement_mission.xml`) is required since **systems_design** calculates the required system power for each mission step.
+
+!!! note
+    When the UNICADO workflow is executed the tool is run automatically. In this case, all the required data should be available anyway. 
+  
+!!! note
+    _acXML_ is an exchange file - we agreed on that only data will be saved as output which is needed by another tool!
+
+**systems_design** has three modes, which are explained [here](software_architecture.md#run) in more detail. The mode can be selected in `module_configuration_file/program_settings/mission_mode` and defines which mission file is used for the calculation of the required power (design, study or requirement mission). For the design mission the systems are also sized, i.e. their masses are calculated.
+
 ## Defining the System Architecture
+![](figures/architecture_definition.png)
+
 The system architecture is defined in the _configXML_ of systemsDesign in the node `module_configuration_file/program_settings/aircraft_systems`. Here the systems are grouped into consumer (or sink) systems, conducting systems, and source systems. (This grouping is also used during calculation.) Energy sinks are systems that consume energy. The environmental control system is considered separately to iterate between the heat created by the systems and the sizing of the environmental control system. Energy sources provide energy. Energy conductors conduct electric or hydraulic energy or bleed air. Virtual systems are used for adding systems that will not be designed (for example if there are no sizing methods implemented for this system). For each group the number of systems in the group is defined, followed by the individual system description. A minimal example of the architecture definition is given below.
 
 ```xml
@@ -93,24 +127,25 @@ The system architecture is defined in the _configXML_ of systemsDesign in the no
 ```
 
 By including or excluding these systems, you can choose which systems are implemented. By default the following systems are included in the architecture (name for configXML given in brackets):
-* energy sinks:
-  * [conventional furnishing system](\ref ATA25-furnishing) (conventionalFurnishing)
-  * [conventional fuel system](\ref ATA28-fuel) (conventionalFuel)
-  * [conventional ice and rain protection system](\ref ATA30-ice-conventional) (conventionalIceRainProtection)
-  * [conventional lighting system](\ref ATA33-lighting) (conventionalLighting)
-  * [conventional fire protection system](\ref ATA26-fire) (conventionalFireProtection)
-  * [conventional oxygen system](\ref ATA35-oxygen) (conventionalOxygenSystem)
-  * [conventional landing gear system](\ref ATA32-gear) (conventionalGear)
-  * [conventional flight control system](\ref ATA27-flight-control) (conventionalFlightControl)
-  * [remaining consumer systems](\ref ATAXX-remaining) (reminingConsumers)
-* [environmental control system](\ref ATA21-ECS) (conventionalECS)
-* energy sources:
-  * [conventional propulsion](\ref ATA70-engine) (conventionalPropulsion)
-  * [conventional APU](\ref ATA49-APU) (conventionalAPU)
-* energy conductors:
-  * [bleed air system](\ref ATA36-bleed) (BleedAirSystem)
-  * [hydraulic system](\ref ATA29-hydraulic) (HydraulicSystem)
-  * [electric system](\ref ATA24-electric) (ElectricSystem)
+
+- energy sinks:
+    - [conventional furnishing system](systems.md#ata-25-furnishing-system) (conventionalFurnishing)
+    - [conventional fuel system](systems.md#ata-28-fuel-system) (conventionalFuel)
+    - [conventional ice and rain protection system](systems.md#ata-30-ice-and-rain-protection-system) (conventionalIceRainProtection)
+    - [conventional lighting system](systems.md#ata-33-lighting-system) (conventionalLighting)
+    - [conventional fire protection system](systems.md#ata-26-fire-protectrion-system) (conventionalFireProtection)
+    - [conventional oxygen system](systems.md#ata-35-oxygen-system) (conventionalOxygenSystem)
+    - [conventional landing gear system](systems.md#ata-32-landing-gear-system) (conventionalGear)
+    - [conventional flight control system](systems.md#ata-27-flight-control-system) (conventionalFlightControl)
+    - [remaining consumer systems](systems.md#ata-xx-remaining-consumers) (reminingConsumers)
+- [environmental control system](systems.md#ata-21-environmental-control-system) (conventionalECS)
+- energy sources:
+    - [conventional propulsion](systems.md#ata-70-engine) (conventionalPropulsion)
+    - [conventional APU](systems.md#ata-49-auxiliary-power-unit-apu) (conventionalAPU)
+- energy conductors:
+    - [bleed air system](systems.md#ata-36-bleed-air-system) (BleedAirSystem)
+    - [hydraulic system](systems.md#ata-29-hydraulic-system) (HydraulicSystem)
+    - [electric system](systems.md#ata-24-electric-system) (ElectricSystem)
 
 Some systems have several implementations (e.g. ATA30 has a conventional and an electric implementation). Which one is used is specified by the node `system_description`. Sticking to the ATA30 example, the conventional implementation would be set like this:
 ```xml
@@ -152,3 +187,14 @@ Additionally, [system-specific parameters](systems.md) can be set in the node `<
 
 ## Output
 **systems_design** will generate a report containing system masses (if run in sizing mode) and the electric, hydraulic and bleed air power profile over the mission for each system. Additionally, the section `systems` of the component design in the _acXML_ is updated (if **systems_design** was run in design mode) and the bleed air and shaft power offtakes from the engine for each mission step are written to the mission file (for any mode).
+
+Here are some examples of what you can expect to see in the report:
+
+![](figures/system-masses.png){width=500}
+
+The mission power shown here is for the propulsion unit. It is negative since the propulsion unit provides power instead of requiring it. Additionally to the plots displayed in the report, csv-files with the plot data can be found in the project folder: `reporting/plots/csv_files`.
+
+![](figures/mission-power-ATA70.png)
+
+!!! note
+    Some systems will not show anything in these graphs. That means they do not require power (e.g. [oxygen system](systems.md#ata-35-oxygen-system)). The graph of the [APU](systems.md#ata-49-auxiliary-power-unit-apu) is also empty because it is only sized for ground operations and those are not considered in the mission shown in these graphs.
\ No newline at end of file

docs/documentation/sizing/systems_design/index.md

 # Introduction {#mainpage}
-The systems design module calculates the mass and power requirement of the aircraft onboard systems. The systems are divided according to the ATA chapters. Models for the following systems exist:
+The systems design module calculates the mass and power requirement of the aircraft onboard systems. The current version supports a conventional power supply architecture shown in the picture below. An update that will allow other power sources is on its way :construction:.
 
-* [ATA 21: Environmental Control System](\ref ATA21-ECS)
-* [ATA 24: Electric System](\ref ATA24-electric)
-* [ATA 25: Furnishing System](\ref ATA25-furnishing)
-* [ATA 26: Fire Protectrion System](\ref ATA26-fire)
-* [ATA 27: Flight Control System](\ref ATA27-flight-control)
-* [ATA 28: Fuel System](\ref ATA28-fuel)
-* [ATA 29: Hydraulic System](\ref ATA29-hydraulic)
-* [ATA 30: Ice and Rain Protection System](\ref ATA30-ice-conventional)
-* [ATA 32: Landing Gear System](\ref ATA32-gear)
-* [ATA 33: Lighting System](\ref ATA33-lighting)
-* [ATA 35: Oxygen System](\ref ATA35-oxygen)
-* [ATA 36: Bleed Air System](\ref ATA36-bleed)
-* [ATA 49: Auxiliary Power Unit (APU)](\ref ATA49-APU)
-* [ATA 70: Engine (only used to account for power extraction efficiencies of the engine)](\ref ATA70-engine)
-* [ATA XX: Remaining Consumers](\ref ATAXX-remaining)
+![](figures/overall_structure.png)
+
+ The systems are divided according to the ATA chapters. Models for the following systems exist:
+
+* [ATA 21: Environmental Control System](systems.md#ata-21-environmental-control-system)
+* [ATA 24: Electric System](systems.md#ata-24-electric-system)
+* [ATA 25: Furnishing System](systems.md#ata-25-furnishing-system)
+* [ATA 26: Fire Protectrion System](systems.md#ata-26-fire-protectrion-system)
+* [ATA 27: Flight Control System](systems.md#ata-27-flight-control-system)
+* [ATA 28: Fuel System](systems.md#ata-28-fuel-system)
+* [ATA 29: Hydraulic System](systems.md#ata-29-hydraulic-system)
+* [ATA 30: Ice and Rain Protection System](systems.md#ata-30-ice-and-rain-protection-system)
+* [ATA 32: Landing Gear System](systems.md#ata-32-landing-gear-system)
+* [ATA 33: Lighting System](systems.md#ata-33-lighting-system)
+* [ATA 35: Oxygen System](systems.md#ata-35-oxygen-system)
+* [ATA 36: Bleed Air System](systems.md#ata-36-bleed-air-system)
+* [ATA 49: Auxiliary Power Unit (APU)](systems.md#ata-49-auxiliary-power-unit-apu)
+* [ATA 70: Engine (only used to account for power extraction efficiencies of the engine)](systems.md#ata-70-engine)
+* [ATA XX: Remaining Consumers](systems.md#ata-xx-remaining-consumers)
 
 [Getting Started](getting_started.md) will show you how to define the system architecture. The settings and calculation methods for the individual aircraft systems are explained in [Systems](systems.md) or you can follow one of the links above directly to the system. If you want to know how the systems design module works have a look at the [Software Architecture](software_architecture.md).

docs/documentation/sizing/systems_design/software_architecture.md

 # Systems Design Software Architecture 
-If you are interested in how **systems_design** performs the system sizing and power requirment calculation, this page will give you an overview. 
+If you are interested in how **systems_design** performs the system sizing and power requirment calculation, this page will give you an overview. The following UNICADO libraries are used:
+
+* atmosphere: determines atmospheric conditions at given altitudes
+* engine: access to engine data (max. available bleed air and shaft power)
+* aircraftGeometry2: used for geometry measurements
+* energyCarriers: accessing energy carrier information (e.g. densities)
+* aixml: handling of xml
+* moduleBasics: used for basic program functions
+* runtimeInfo: terminal outputs
+* unitConversion: converting units
+* standardFiles: file handling
+
 ## Module Structure
 Currently **systems_design** only has one strategy - the `STANDARD` strategy implemented in `standardSystemsDesign.cpp`. In **systems_design** each system is represented by an instance of the class `aircraftSystem`. Its properties include the point mass and CoG of the system, the required power, and the heat load emitted by the system. Each aircraftSystem has functions for calculating these properties. The power of a system is not constant throughout the mission but calculated for each mission step. These values are stored in objects of the class `powerProfile`. This class stores the design power, used for system sizing, and the mission power. The mission power is further divided into the base load during this mission step and potential peak loads, e.g. resulting from the retraction or extension of the landing gear. Heat loads occurring due to energy losses in the systems are also calculated for each mission step and stored in a powerProfile.
 
+![](figures/system_class.png){width=500 style="display: block; margin: auto;"}
+
 If a new aircraftSystem is implemented, its header file has to be included in `standardSystemsDesign.cpp` and an else-if-statement calling its constructor according to the system name has to be added to `standardSystemsDesign::initializeSystems()`.
 
 ## Calculation
+The calculation methodology is shown in this flow chart and explained in detail below.
+
+![](figures/flow-chart.png){width=400 style="display: block; margin: auto;"}
+
 #### Initialize
 The system design module starts with `standardSystemsDesign::initialize()` by initializing all aircraft systems using the user-provided data from the configuration file. The config file is read when the `data_` object is created. Additionally, required aircraft parameters from the aircraft exchange file are read. This includes geometry data (fuselage, nacelles, wing, empennage), propulsion data, mass and performance and accomodation data. This data are required for the power and mass calculations of specific systems. However, all data are read centrally by the `systemsIOData` class during initialization. Lastly checks for the user input and the geometry from the acxml are performed.
 
-**systems_design** considers the temperature offset to the International Standard Atmosphere (ISA) defined in the _acXML_. The resulting temperature changes in the atmospheric conditions are applied to the mission steps and affect the power demand and thus the mass properties of systems depending on atmospheric conditions ([environmental control system](\ref ATA21-ECS), [flight control system](\ref ATA27-flight-control), [ice and rain protection system](\ref ATA30-ice-conventional)).
+!!! note 
+    **systems_design** considers the temperature offset to the International Standard Atmosphere (ISA) defined in the _acXML_. The resulting temperature changes in the atmospheric conditions are applied to the mission steps and affect the power demand and thus the mass properties of systems depending on atmospheric conditions ([environmental control system](systems.md#ata-21-environmental-control-system), [flight control system](systems.md#ata-27-flight-control-system), [ice and rain protection system](systems.md#ata-30-ice-and-rain-protection-system)).
 
 #### Run
-\anchor modes
 The strategy standard systems design contains three modes, which can be selected in the configuration file. The sizing mode calculates the required system power and based on that the system masses. The study and requirment mode can be used to calculate the required system power for different missions (either the study or requirments mission) and do not resize the systems (i.e., no mass calculation is performed).
 
 **Sizing Mode**
 
 First, the module calculates the performance profile of each system (with the function `standardSystemsDesign::calculatePerformanceProfile()`). This involves calling the respective power calculation function for each system in a specific order: consumer systems, the environmental control system (ECS), conducting systems, and source systems. The calculation order is crucial because the power requirements of consumer systems are necessary to calculate the conducting and source power. At first, the power profiles of all consumer systems are calculated (`standardSystemsDesign::getSinkEnergyConsumption()`) except for the ECS. It is treated separately because its power requirement depends on the heat loads generated by other systems, including conducting systems. Therefore, it is calculated later in the process.
 
-After each consumer system power calculation, the power is accumulated in a global power profile that stores the combined power requirement and heat loads of all consumer systems. Conductor systems can provide power to other conducting systems, e.g. through the conversion of electrical power to hydraulic power. The power used for these conversions is calculated next (with `transferElec2HydPower` (electric driven hydraulic pumps) and `transferHyd2ElecPower` (only for failure cases)) and stored in the global sink power profile.
+After each consumer system power calculation, the power is accumulated in a global power profile that stores the combined power requirement and heat loads of all consumer systems.
+
+![](figures/power_summation.png){width=400 style="display: block; margin: auto;"}
+
+Conductor systems can provide power to other conducting systems, e.g. through the conversion of electrical power to hydraulic power. The power used for these conversions is calculated next (with `transferElec2HydPower` (electric driven hydraulic pumps) and `transferHyd2ElecPower` (only for failure cases)) and stored in the global sink power profile.
 
 Next, an iteration loop is required because the ECS power requirement depends on the heat load of the sinks and conductors and the conducting power depends on the power requirement of the ECS. At the beginning of each loop the power profiles `data_->data.ECSConsumption` and `data_->data.conductorConsumption` are cleared from the values of the previous iteration loop and the global power profiles of the conductors are initialized (`data_->Systems.energyConductor`). In each iteration loop, the ECS power is calculated (`standardSystemsDesign::getECSEnergyConsumption()`) based on the heat loads of the consumer systems stored in the global sink power profile. The power requirements for conducting systems are then calculated or updated (`standardSystemsDesign::getConductorEnergyConsumption()`) to reflect the new ECS consumption, including any power transfers, such as from hydraulic to electrical power. The iteration continues until the average bleed load of the ECS converges. The convergence criterion is set to a difference of less than 10<sup>-4</sup> between iterations.
 
@@ -27,7 +48,8 @@ After achieving convergence, the module calculates the power the sources (`stand
 
 Finally, with the power profiles established, the module calculates the mass of each system (`standardSystemsDesign::getSystemsMass()`) based on the design power requirements and specific characteristics of each system by calling the mass calculation method of each system. For virtual systems no method is called, rather the user definded values are copied from the configuration file. After the individual system masses are calculated, the function `weightsAndCGs::getWeights()` calculates the masses and CGs of system groups and the mass of some operator items. In UNICADO only the residual oil and fuel as well as water and toilet chemicals are considered part of the systems. Other operator items are calculated in fuselage design and mission analysis.
 
-**Note**: The currently implemented methods for the operator items (Torenbeek) do not calculate the residual oil mass!
+!!! note
+    The currently implemented methods for the operator items (Torenbeek) do not calculate the residual oil mass!
 
 **Study Mode**
 
@@ -45,4 +67,4 @@ The function `systemsIOData::updateMissionXML()` updates all values calculated w
 
 #### Report
 This section is used to create the plots and html and tex report of the module.
-Plots are generated using matplot++. Additionally, csv files with the plot data are written.
+Plots are generated using matplot++. Additionally, csv files with the plot data are written. More information on the outputs can be found [here](getting-started.md#output).

docs/documentation/sizing/systems_design/systems.md

 # Implemented Aircraft System Models
 
-\anchor ATA21-ECS
 ## ATA 21: Environmental Control System
 The environmental control system model implemented is powered by electric power and bleed air from the engines.
 
@@ -8,7 +7,7 @@ The environmental control system model implemented is powered by electric power
 
 The power required by the environmental control system is calculated based on the heat loads of all systems, the heat from the sun and from the passengers. The ECO-Mode allows to reduce the required bleed air by 25%. Air conditioning is switched off during takeoff.
 
-The mass of the ECS depends on the bleed air mass flow in the design point. Calculation method from LTH and Howe. The mass is broken down into the components ducts, air conditioning pack, outlet, ram inlet, vents, and misc. according to factors determined by Koeppen.
+The mass of the ECS depends on the bleed air mass flow in the design point. Calculation method from LTH and Howe. The mass is broken down into the components ducts, air conditioning pack, outlet, ram inlet, vents, and misc. according to factors determined by Koeppen[^1].
 
 The CoG of the ECS is determined with the assumption that its located in the belly fairing.
 
@@ -27,7 +26,6 @@ The CoG of the ECS is determined with the assumption that its located in the bel
 * Off Take Off: Switch to turn of ACP during take off
 * ECO Mode: Switch for ECO Mode reduces bleed air requirement by 25%
 
-\anchor ATA24-electric
 ## ATA 24: Electric System
 
 **Methods**
@@ -53,7 +51,6 @@ The mass calculation method from Steinke is based on the maximum required electr
     * efficiency
     * operation factor (share of total power in normal operation)
 
-\anchor ATA25-furnishing
 ## ATA 25: Furnishing System
 
 Furnishing system includes the power required for the galleys and the inflight entertainment system (IFE). The mass of all furnishing is calculated in fuselage design and read from the aircraft exchange file.
@@ -65,22 +62,24 @@ Power calculation is done based on user inputs.
 **Required Input Parameters**
 
 * Galley Load Fraction during Takeoff [-]:
-    Electric Load Analysis for A320 suggest a value of 0.2 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 0.2[^1]
+
+[^1]: Source documents are available in German and can be requested from the RWTH Aachen.
+
 * Galley Load Fraction during Cruise [-]:
-    Electric Load Analysis for A320 suggest a value of 0.7 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 0.7[^1]
 * Galley Load Fraction during Descent [-]:
-    Electric Load Analysis for A320 suggest a value of 0.2 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 0.2[^1]
 * Galley Location [m]
 * Non Personal IFE Power [W]: General power for IFE
 * Personal IFE Power [W]: Power for IFE per PAX
 * Personal IFE Load Fraction Climb [-]:
-    Electric Load Analysis for A320 suggest a value of 0.58 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 0.58[^1]
 * Personal IFE Load Fraction Cruise [-]:
-    Electric Load Analysis for A320 suggest a value of 1 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 1[^1]
 * Personal IFE Load Fraction Descent [-]:
-    Electric Load Analysis for A320 suggest a value of 0.5 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 0.5[^1]
 
-\anchor ATA26-fire
 ## ATA 26: Fire Protectrion System
 
 Does not require power!
@@ -93,7 +92,6 @@ Mass calculation is based on propulsion type and MTOM (Torenbeek Tab. 8-12).
 
 None.
 
-\anchor ATA27-flight-control
 ## ATA 27: Flight Control System
 
 The flight control system is modeled in great detail down to the individual actuators of the control surfaces. The calculation is devided into segments according to the control surfaces:
@@ -160,7 +158,6 @@ Acceptable control surface names are:
 
 **Note**: not all of these devices are implemented. If they aren't implemented a default will be used and a warning issued.
 
-\anchor ATA28-fuel
 ## ATA 28: Fuel System
 
 **The fuel system does not contain the tank mass!**
@@ -177,7 +174,6 @@ The CoG is assumed to be the same as that of the wing.
 
 None
 
-\anchor ATA29-hydraulic
 ## ATA 29: Hydraulic System
 
 **Methods**
@@ -186,7 +182,7 @@ None
 
 The required power of the hydraulic system is the power lost through inefficiencies. The efficiency factor for the hydraulic system and for the pumps are considered.
 
-The mass calculation method from [Steinke](\ref additional_sources) is based on the maximum required hydraulic power, the OME, the fluid mass and the ducting length. The ducting length is composed of the lengths from the engines to the belly fairing, the front gear to the back gear, 2 * the length of the wing trailing edge, 2 * the trailing edges of the horizontal and vertical tail plane. The total length is then doubled to account for the backflow.
+The mass calculation method from Steinke[^1] is based on the maximum required hydraulic power, the OME, the fluid mass and the ducting length. The ducting length is composed of the lengths from the engines to the belly fairing, the front gear to the back gear, 2 * the length of the wing trailing edge, 2 * the trailing edges of the horizontal and vertical tail plane. The total length is then doubled to account for the backflow.
 
 **Required Input Parameters**
 
@@ -210,7 +206,6 @@ The mass calculation method from [Steinke](\ref additional_sources) is based on
 
 There are two implemented models for the ice and rain protection system - a conventional one powered by bleed air and an electric one.
 
-\anchor ATA30-ice-conventional
 ### Conventional ATA 30
 
 **Methods**
@@ -230,7 +225,6 @@ Anti-Icing is typically applied from the kink of the wing and ends at the outer
 * Drop Diameter [micro meter]
 * Mass Percentage of OME [-]
 
-\anchor ATA30-ice-electric
 ### Electric ATA 30
 
 Mass is calculated as a percentage of the OME defined by the user.
@@ -244,16 +238,15 @@ Same calculation for the external heat flux. From there the required electric po
 Same as for conventional +
 
 * Electric Power Consumption Departure [W]:
-    Electric Load Analysis for A320 suggest a value of 14026.9 W [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 14026.9 W[^1]
 * Electric Power Consumption Cruise [W]:
-    Electric Load Analysis for A320 suggest a value of 13070.9 W [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 13070.9 W[^1]
 * Electric Power Consumption Approach [W]:
-    Electric Load Analysis for A320 suggest a value of 14026.9 W [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 14026.9 W[^1]
 * Electric Power Consumption Land [W]
-    Electric Load Analysis for A320 suggest a value of 7192.9 W [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 7192.9 W[^1]
 * Efficiency Electro Thermic Anti-Icing [-]
 
-\anchor ATA32-gear
 ## ATA 32: Landing Gear System
 
 **Methods**
@@ -269,7 +262,6 @@ The retraction and extension power are calculated based on the mass of the landi
 * Extension Time [s]
 * Power Source(s)
 
-\anchor ATA33-lighting
 ## ATA 33: Lighting System
 
 **Methods**
@@ -297,14 +289,13 @@ The design electric power is calculated assuming all lights are on. For the miss
 * Logo Light Power [W]
 * Strobe Light Power [W]
 * Specific Emergency Light Power [W/m^3]
-    Electric Load Analysis for A320 suggest a value of 1.46 W/m^3 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 1.46 W/m^3[^1]
 * Specific Cabin Light Power [W/m^3]
-    Electric Load Analysis for A320 suggest a value of 18.04 W/m^3 [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 18.04 W/m^3[^1]
 * Flight Deck Light Power [W]
-    Electric Load Analysis for A320 suggest a value of 904.4 W [[1]](\ref additional_sources)
+    Electric Load Analysis for A320 suggest a value of 904.4 W[^1]
 * Power Sources
 
-\anchor ATA35-oxygen
 ## ATA 35: Oxygen System
 
 The oxygen system does not require power.
@@ -317,7 +308,6 @@ The mass is calculated according to Torenbeek based on the number of PAX and dep
 
 None.
 
-\anchor ATA36-bleed
 ## ATA 36: Bleed Air System
 
 **Methods**
@@ -334,7 +324,6 @@ Bleed air required by the bleed air system is based on the efficiency losses in
 * Efficiency Factor [-]
 * Specific Ducting Mass [kg/m]
 
-\anchor ATA49-APU
 ## ATA 49: Auxiliary Power Unit (APU)
 
 The APU is the only power source sized within systems design. However, it is only operated on ground. Ground operations are not included in the mission analysis in UNICADO, thus, the kerosene required by the APU is neglected.
@@ -355,7 +344,6 @@ The power provided by the APU is calculated with the user defined percentages an
 * Installation factor for attached parts such as fire protection, noise protection, etc. [-]
 * Percentages of power provided by APU for design case (bleed air, electric power, hydraulic power) [-]
 
-\anchor ATA70-engine
 ## ATA 70: Engine
 
 This model is only used to account for power extraction efficiencies of the engine. The engine is sized in the engine design module. The powere required by the systems from the engine is checked against the maximum power the engine can provide before updating the xml files. If at power peaks more power is required than available the less power over a longer amount of time will be written to the xml.
@@ -371,7 +359,6 @@ The efficiency factors for the shaft power extraction (electric + hydraulic powe
 * Percentage of hydraulic power provided by the engine [-]
 * Efficiency factor for the bleed air extraction [-]
 
-\anchor ATAXX-remaining
 ## ATA XX: Remaining Consumers
 
 The remaining consumers are the avionics and their power requirement is derived as a percentage of the power required by all other sink systems.
@@ -394,6 +381,5 @@ The CoG is calculated assuming the instruments are placed at the end of the cock
 * Mass percentage of ATA XX for navigation [-]
 * Mass percentage of ATA XX for communication [-]
 
-\anchor additional_sources
 ### Additional Sources
-[1] Source documents are available in German and can be requested from the RWTH Aachen.
\ No newline at end of file
+[^1] Source documents are available in German and can be requested from the RWTH Aachen.
\ No newline at end of file

mkdocs.yml

@@ -24,6 +24,7 @@ markdown_extensions:
   - attr_list                             # Allows adding HTML attributes to Markdown elements (like classes).
   - admonition                            # Enables note/warning/admonition boxes with custom styling.
   - md_in_html                            # Allows writing Markdown inside HTML tags for flexibility.
+  - footnotes                             # Allows footnotes
   - pymdownx.tabbed:                      # Enables tabbed content blocks, allowing content to be organized in tabs.
       alternate_style: true               # Uses an alternate style for tabbed blocks.
   - pymdownx.emoji:                       # Adds support for emojis using the Material theme’s emoji set.
@@ -227,8 +228,9 @@ nav:                                      # Customizes the main navigation struc
           - Empennage Design:
             - Introduction: documentation/sizing/empennage_design/index.md
             - Getting Started: documentation/sizing/empennage_design/getting-started.md
+            - Design Method: documentation/sizing/empennage_design/design-methods.md
             - Basic Concepts: documentation/sizing/empennage_design/basic-concepts.md
-            - Run your First Design: documentation/sizing/empennage_design/dfe.md
+            - Run your First Design: documentation/sizing/empennage_design/run-your-first-empennage-design.md
             - API Reference:
               - empennage_design/classes.md
               - empennage_design/namespaces.md