Engine mass-flow rate coupling for zero-thrust simulation#2753
Conversation
Added flag to allow mass-flow rate coupling between all exhaust boundaries towards the engine inlet.
pcarruscag
left a comment
There was a problem hiding this comment.
Can you add a test? The engine features are not covered very well.
|
We use the testcases repo for meshes, but that is pretty large even by those standards. |
|
I understand. Just uploaded a coarser mesh in the testcases repo. Please let us know if you need additional input. |
|
Yes, please modify parallel_regression.py to add your test so that it runs in the github actions and set suitable regression values |
|
ok, done. |
|
In .github/workflows/regression.yml you can change this line to point to the testcase branch m-minervino:develop : Else it cannot find the mesh since it is not in develop yet. |
|
I just modified the file, hope in the correct way. |
|
I just cleaned the .cfg file. |

Added flag to allow mass-flow rate coupling between all exhaust boundaries towards the engine inlet.
Proposed Changes
When simulating a turbofan engine in idle regime (no thrust), total free-stream conditions can be imposed at fan and core exhaust boundaries (i.e. no energy variation by the engine), but no information is usually available at the fan inlet boundary (for example, the target mass-flow rate to be used).
Assuming that both engine bleed and fuel addition are negligible, the sum of mass-flow rates computed at all exhaust boundaries can be specified as a target for the inlet (ENGINE_INFLOW_TYPE= FAN_FACE_MDOT).
The proposed modification, then, changes the target value at run-time (instead of using a fixed pre-defined value specified in the configuration file) to match the overall outlet mass-flow rates.
by: Angelo Passariello and Mauro Minervino (Italian Aerospace Research Centre).
Related Work
None.
PR Checklist
pre-commit run --allto format old commits.