Engine mass-flow rate coupling for zero-thrust simulation by m-minervino · Pull Request #2753 · su2code/SU2 · GitHub
Skip to content

Engine mass-flow rate coupling for zero-thrust simulation#2753

Merged
pcarruscag merged 11 commits into
su2code:developfrom
m-minervino:develop
Mar 17, 2026
Merged

Engine mass-flow rate coupling for zero-thrust simulation#2753
pcarruscag merged 11 commits into
su2code:developfrom
m-minervino:develop

Conversation

@m-minervino

@m-minervino m-minervino commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

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

  • I am submitting my contribution to the develop branch.
  • My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
  • My contribution is commented and consistent with SU2 style (https://su2code.github.io/docs_v7/Style-Guide/).
  • I used the pre-commit hook to prevent dirty commits and used pre-commit run --all to format old commits.
  • I have added a test case that demonstrates my contribution, if necessary.
  • I have updated appropriate documentation (Tutorials, Docs Page, config_template.cpp), if necessary.

Added flag to allow mass-flow rate coupling between all exhaust
boundaries towards the engine inlet.

@pcarruscag pcarruscag left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a test? The engine features are not covered very well.

@m-minervino

Copy link
Copy Markdown
Contributor Author

@pcarruscag

Copy link
Copy Markdown
Member

We use the testcases repo for meshes, but that is pretty large even by those standards.
Can you create a simpler case? Or coarser mesh.

@m-minervino

Copy link
Copy Markdown
Contributor Author

I understand. Just uploaded a coarser mesh in the testcases repo. Please let us know if you need additional input.

@pcarruscag

Copy link
Copy Markdown
Member

Yes, please modify parallel_regression.py to add your test so that it runs in the github actions and set suitable regression values

@m-minervino

Copy link
Copy Markdown
Contributor Author

ok, done.

@bigfooted

Copy link
Copy Markdown
Contributor

In .github/workflows/regression.yml you can change this line to point to the testcase branch m-minervino:develop :
# -t -c
args: -b ${{github.ref}} -t develop -c develop -s ${{matrix.testscript}}

Else it cannot find the mesh since it is not in develop yet.

@m-minervino

Copy link
Copy Markdown
Contributor Author

I just modified the file, hope in the correct way.

Comment thread TestCases/euler/turbofan_MFR_coupling/MFR_coupling.cfg Outdated
Comment thread TestCases/euler/turbofan_MFR_coupling/MFR_coupling.cfg Outdated
Comment thread TestCases/euler/turbofan_MFR_coupling/MFR_coupling.cfg Outdated
Comment thread TestCases/euler/turbofan_MFR_coupling/MFR_coupling.cfg Outdated
Comment thread TestCases/euler/turbofan_MFR_coupling/MFR_coupling.cfg Outdated
@m-minervino

m-minervino commented Mar 16, 2026

Copy link
Copy Markdown
Contributor Author

I just cleaned the .cfg file.
Concerning regression.yml, instead, I modified line 214 specifying "m-minervino:develop" as testcases-branch, but regression tests failed on Saturday. Then I modified it again into "m-minervino/TestCases:develop" but tests failed again on yesterday.
Could you please tell me how to correctly modify this file? thanks

@pcarruscag

Copy link
Copy Markdown
Member

@pcarruscag pcarruscag merged commit dcb9f14 into su2code:develop Mar 17, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants