From 8c57d83cc9651bf609a68c939ef8b4faebc3a394 Mon Sep 17 00:00:00 2001
From: tobi <tobias.weckenmann@tum.de>
Date: Thu, 6 Feb 2025 15:26:33 +0100
Subject: [PATCH] nnta ks
---
.../sizing/propulsion_design/engineering_principles.md | 6 +++---
.../sizing/propulsion_design/getting_started.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/documentation/sizing/propulsion_design/engineering_principles.md b/docs/documentation/sizing/propulsion_design/engineering_principles.md
index 4368d58..7d710eb 100644
--- a/docs/documentation/sizing/propulsion_design/engineering_principles.md
+++ b/docs/documentation/sizing/propulsion_design/engineering_principles.md
@@ -1,7 +1,7 @@
# Engineering principles {#engineeringprinciples}
-Designing the propulsion with this tool includes different engineering disciplines. Here a brief explanation (more information in their respective sections):
+Designing the propulsion with this tool includes different engineering disciplines. Here is a brief explanation (more information in their respective sections):
- [Engine designer](#enginedesigner): Calculates the performance of one individual engine based on the required thrust.
- [Propulsor integrator](#propulsionintegrator): Places the engine acc. to the user's settings.
- [Nacelle designer](#nacelledesigner): Calculates the nacelle geometry.
@@ -61,7 +61,7 @@ An exemplary simplified calculation (data from the V2527-A5): the current engine
The general scaling is therefore a linear scaling of the thrust. The fuel flow is scaled in the same way leading to a scaling approach with constant TSFC.
-So, again, the engine data is always accessed via the `engine` library to ensure that you have the correctly scaled data for every value. This is valid for both the non operating condition dependant variables and the values that are directly read from the deck -csv values.
+So, again, the engine data is always accessed via the `engine` library to ensure that you have the correctly scaled data for every value. This is valid for both the non operating condition dependent variables and the values that are directly read from the deck values.
@note Actually, the sea level static thrust is not at \f$N1=1\f$ if you compare the dataset for this engine (for 110.31kN around \f$N1=0.95\f$). So the scaling factor will be slightly lower.
@@ -73,7 +73,7 @@ The **engine designer** includes different methods which create/use this deck in
@note *empirical* and *propulsionsystem* is in preparation - not implemented yet!
-For all these methods, the approach of using the _scale factor_ is the same (see explanation [here](#generalprinciples)). A deck is either first created or assumed and then data is drawn with the `engine` library with the scaling approach.
+For these methods, the approach of using the _scale factor_ is the same (see explanation [here](#generalprinciples)). A deck is either first created or assumed and then data is drawn with the `engine` library with the scaling approach.
## Propulsion integrator {#propulsionintegrator}
Additionally to calculating the engine performance parameter, the engine has to be placed on the aircraft. The **propulsion integrator** uses the user settings from the aircraft exchange file - the following needs to be defined:
diff --git a/docs/documentation/sizing/propulsion_design/getting_started.md b/docs/documentation/sizing/propulsion_design/getting_started.md
index 64f7b18..85c94f5 100644
--- a/docs/documentation/sizing/propulsion_design/getting_started.md
+++ b/docs/documentation/sizing/propulsion_design/getting_started.md
@@ -42,7 +42,7 @@ Following is needed from the _acXML_:
2) the average system off-takes of the engines,
3) the user settings of the propulsion architecture.
-Naturally, the propulsion need an assumption for thrust or power to be designed. In the first iteration in UNICADO, the requirement is set via the tool _initialSizing_. It is then updated in _constraint_analysis_ in every loop to assure that the thrust that is fitted onto the aircraft assures enough thrust in all required flight stages. For this, **propulsion_design** currently assumes:
+Naturally, the propulsion needs an assumption for thrust or power to be designed. In the first iteration in UNICADO, the requirement is set via the tool _initialSizing_. It is then updated in _constraint_analysis_ in every loop to assure that the thrust that is fitted onto the aircraft assures enough thrust in all required flight stages. For this, **propulsion_design** currently assumes:
The sea level static thrust \f$ T_0 \f$ is given by:
--
GitLab