Fix marker engine inflow by BerkeCan97 · Pull Request #2278 · su2code/SU2
added 6 commits
May 10, 2024 10:12
Added mach number evaluation for the engine boundaries. Decoupled the engine marker evaluation frequency from screen write frequency
Defining the option BC_EVAL_FREQ, for setting the evaluation frequency for the Engine and Actuator markers
Defining option BC_EVAL_FREQ, to set the evaluation frequency for Engine and Actuator Disk Markers
Test case for marker_engine_inflow
…estCases/engine/marker_engine_inflow/inv_channel_engine_inflow.cfg
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Changed the mesh to an existing mesh in the repository
Changing the mesh file to an existing mesh
Co-authored-by: Nijso <nijso@hotmail.com>
Co-authored-by: Nijso <nijso@hotmail.com>
Co-authored-by: Nijso <nijso@hotmail.com>
Changed Case Description, Author, Date and File Version
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters