-
Configuration File
Mesh File
Restart File
Solver Setup
Physical Definition
Markers and Boundary Conditions
Convective Schemes
Slope Limiters and Shock Resolution
History and Solution Output
Linear Solvers and Preconditioners
Basics of Multi-Zone Computations
Execution
Aeroacoustic analysis of unsteady pressure
Flamelet Solver — Python Wrapper Wall Boundary Conditions
Output Fields Reference
Error Messages
-
Setup Guide: Steady RANS for External Aerodynamics
Setup Guide: Incompressible Flows
Setup Guide: Unsteady Flows and DES
Setup Guide: Laminar-Turbulent Transition
Setup Guide: Turbomachinery
Setup Guide: Heat Transfer and Conjugate Heat Transfer
Setup Guide: Species Transport and Combustion
Setup Guide: Shape Optimization with the Discrete Adjoint
Setup Guide: Non-Ideal Compressible Flows
-
Option Reference
Problem Definition
FluidModel
Data-driven fluid model parameters
Freestream Conditions
Reference Conditions
Boundary Markers
Time-marching
Linear solver definition
Convergence
Multi-grid
Spatial Discretization
Adjoint and Gradient
Sobolev Gradient Solver Parameters
Input/output files and formats
Dynamic mesh definition
Aeroelastic Simulation (Typical Section Model)
Wind Gust
Equivalent Area
Grid deformation
Deformable mesh
FEM flow solver definition
FEA solver
Multizone definition
Radiation solver
Heat solver
Visualize Control Volumes
Inverse design problem
Unsupported options
FFD point inversion
Automatic Differentation options
Python Options
Hybrid_RANSLES Options
Output Options
libROM options
Renamed and Removed Options
-
GIT-ting Started
Developing SU2 on GitHub (Internal Developers)
Running Regression Tests
Code Review
Code Structure
Style Guide
Advanced AD Techniques
Containers for Development
Writing Unit Tests
Integrating Tracy Profiler with SU2
Automatic Differentiation (AD)
Code Reference (Doxygen)
Debugging SU2
Documentation Improvements and Status
Glossary
Docs Check
Boundary Markers
Generated from SU2 commit
6b54b78464on 2026-10-23. Do not edit this page. Edit the comment above the option inCommon/src/CConfig.cppinstead.
MARKER_PLOTTING
Marker(s) of the surface in the surface flow solution file
- Type: list of strings
- In config_template.cfg:
MARKER_PLOTTING = ( airfoil ) - Mentioned in: History and Solution Output, Setup Guide: Laminar-Turbulent Transition, Setup Guide: Shape Optimization with the Discrete Adjoint, Setup Guide: Steady RANS for External Aerodynamics, Setup Guide: Unsteady Flows and DES, Aachen turbine stage with Mixing-plane and 1 more
- Used in 312 test case files, for example:
aeroelastic_NACA64A010.cfg(( airfoil )),backwardStep.cfg(( WALL_BOTTOM )),config.cfg(( InnerWall )) - Code:
CConfig.cppline 1603
MARKER_MONITORING
Marker(s) of the surface where evaluate the non-dimensional coefficients
More in config_template.cfg: Marker(s) of the surface where the non-dimensional coefficients are evaluated.
- Type: list of strings
- In config_template.cfg:
MARKER_MONITORING = ( airfoil ) - Mentioned in: Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Incompressible Flows, Setup Guide: Laminar-Turbulent Transition, Setup Guide: Shape Optimization with the Discrete Adjoint, Setup Guide: Steady RANS for External Aerodynamics, Setup Guide: Unsteady Flows and DES and 4 more
- Used in 321 test case files, for example:
aeroelastic_NACA64A010.cfg(( airfoil )),air_nozzle_restart.cfg((WALL)),config.cfg(( InnerWall )) - Code:
CConfig.cppline 1605
MARKER_CREATE_COPY
Marker(s) for which to create copies when reading the mesh
More in config_template.cfg: Duplicate markers while reading the mesh. Currently this is only used for thermoelastic simulations to allow specifying two boundary conditions (thermal and structural) on the same boundary.
- Type: list of strings
- In config_template.cfg:
MARKER_CREATE_COPY= ( original_1, copy_1, ..., original_n, copy_n ) - Mentioned in: Changes in Version 8
- Used in 4 test case files, for example:
configBeamNonlinear_3d.cfg(( left, left_heat, right, right_heat )),configFEA.cfg(( clamped, isothermal )) - Code:
CConfig.cppline 1608
MARKER_ANALYZE
Marker(s) of the surface in the surface flow solution file
More in config_template.cfg: Marker(s) of the surface that is going to be analyzed in detail (massflow, average pressure, distortion, etc)
- Type: list of strings
- In config_template.cfg:
MARKER_ANALYZE = ( airfoil ) - Mentioned in: Setup Guide: Incompressible Flows, Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Shape Optimization with the Discrete Adjoint, Setup Guide: Species Transport and Combustion, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane and 1 more
- Used in 62 test case files, for example:
inv_wedge_ROE.cfg((outlet)),fluid.cfg(( cylinder_fluid )),Arina2KRS.cfg(( WALL1 )) - Code:
CConfig.cppline 1611
MARKER_DESIGNING
Marker(s) of the surface where objective function (design problem) will be evaluated
More in config_template.cfg: Marker(s) of the surface where obj. func. (design problem) will be evaluated
- Type: list of strings
- In config_template.cfg:
MARKER_DESIGNING = ( airfoil ) - Used in 60 test case files, for example:
inv_ONERAM6.cfg(( WING )),def_cylindrical.cfg(( CYLINDER )),def_NACA0012.cfg(( airfoil )) - Code:
CConfig.cppline 1613
GEO_MARKER
Marker(s) of the surface where evaluate the geometrical functions
More in config_template.cfg: Marker(s) of the surface where geometrical based function will be evaluated
- Type: list of strings
- In config_template.cfg:
GEO_MARKER= ( airfoil ) - Mentioned in: Setup Guide: Shape Optimization with the Discrete Adjoint, Constrained shape design of a transonic inviscid wing at a cte. CL
- Used in 20 test case files, for example:
turb_ONERAM6.cfg(( wing )),naca0012.cfg(( airfoil )),Arina2KRS.cfg(( WALL1 )) - Code:
CConfig.cppline 1615
MARKER_EULER
Euler wall boundary marker(s)
More in config_template.cfg: Euler wall boundary marker(s) (NONE = no marker) Implementation identical to MARKER_SYM.
- Type: list of strings
- In config_template.cfg:
MARKER_EULER= ( airfoil ) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Shape Optimization with the Discrete Adjoint, Inviscid Bump in a Channel, Inviscid Hydrofoil and 1 more
- Used in 135 test case files, for example:
aeroelastic_NACA64A010.cfg(( airfoil )),inv_ONERAM6.cfg(( WING )),inv_wedge_ROE.cfg(( upper, lower )) - Code:
CConfig.cppline 1617
MARKER_FAR
Far-field boundary marker(s)
More in config_template.cfg: Far-field boundary marker(s) (NONE = no marker)
- Type: list of strings
- In config_template.cfg:
MARKER_FAR= ( farfield ) - Mentioned in: Markers and Boundary Conditions, Physical Definition, Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Incompressible Flows, Setup Guide: Laminar-Turbulent Transition, Setup Guide: Non-Ideal Compressible Flows and 5 more
- Used in 189 test case files, for example:
aeroelastic_NACA64A010.cfg(( farfield )),config.cfg(( Inlet, Outlet )),inv_ONERAM6.cfg(( FARFIELD )) - Code:
CConfig.cppline 1619
MARKER_SYM
Symmetry boundary condition
More in config_template.cfg: Symmetry boundary marker(s) (NONE = no marker) Implementation identical to MARKER_EULER.
- Type: list of strings
- In config_template.cfg:
MARKER_SYM= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Shape Optimization with the Discrete Adjoint, Setup Guide: Species Transport and Combustion, Setup Guide: Steady RANS for External Aerodynamics and 3 more
- Used in 118 test case files, for example:
air_nozzle_restart.cfg(( SYMMETRY )),backwardStep.cfg(( SYMMETRY_TOP, SYMMETRY_BOTTOM )),turb_ONERAM6.cfg(( symmetry )) - Code:
CConfig.cppline 1621
MARKER_NEARFIELD
Near-Field boundary condition
More in config_template.cfg: Near-Field boundary marker(s) (NONE = no marker)
- Type: list of strings
- In config_template.cfg:
MARKER_NEARFIELD= ( NONE ) - Used in 3 test case files, for example:
Arina2KRS.cfg(( NONE )),BIPARABOLIC.cfg(( upper_nearfield, lower_nearfield )),NACA64206.cfg(( Nearfield )) - Code:
CConfig.cppline 1623
MARKER_FLUID_INTERFACE
Fluid interface boundary marker(s)
- Type: list of strings
- In config_template.cfg:
MARKER_FLUID_INTERFACE= ( NONE ) - Mentioned in: Setup Guide: Turbomachinery
- Used in 25 test case files, for example:
Arina2KRS.cfg(( NONE )),circles.cfg((OUTMIX, INMIX)),bars.cfg((outflow_bars, inflow_channel)) - Code:
CConfig.cppline 1625
MARKER_DEFORM_MESH
Deformable marker(s) at the interface
More in config_template.cfg: Moving markers which deform the mesh
- Type: list of strings
- In config_template.cfg:
MARKER_DEFORM_MESH = ( airfoil ) - Mentioned in: Setup Guide: Shape Optimization with the Discrete Adjoint, Dynamic Fluid-Structure Interaction (FSI) using the Python wrapper and a Nastran structural model, Static Fluid-Structure Interaction (FSI)
- Used in 13 test case files, for example:
configFlow.cfg(( leading_edge, pressure_side, suction_side )),configFlow.cfg(( UpperWall, LowerWall )),configFlow.cfg((wallUpwF, wallDownF, wallUpperF)) - Code:
CConfig.cppline 1627
MARKER_DEFORM_MESH_SYM_PLANE
Symmetry plane for mesh deformation only
- Type: list of strings
- In config_template.cfg:
MARKER_DEFORM_MESH_SYM_PLANE = ( wall ) - Mentioned in: Dynamic Fluid-Structure Interaction (FSI) using the Python wrapper and a Nastran structural model
- Used in 2 test case files, for example:
configFlow.cfg(( upper )) - Code:
CConfig.cppline 1629
MARKER_DEFORM_MESH_INTERNAL
Internal marker for mesh deformation only
- Type: list of strings
- Not in config_template.cfg.
- Code:
CConfig.cppline 1631
MARKER_FLUID_LOAD
Marker(s) in which the flow load is computed/applied
- Type: list of strings
- In config_template.cfg:
MARKER_FLUID_LOAD= ( NONE ) - Mentioned in: Static Fluid-Structure Interaction (FSI)
- Used in 10 test case files, for example:
configFEA.cfg(( pressure_side_s, suction_side_s )),configFEA.cfg(( LowerWallS, UpperWallS)),configFEA.cfg(( pressure_side_s, suction_side_s, clamped )) - Code:
CConfig.cppline 1633
MARKER_ZONE_INTERFACE
ZONE interface boundary marker(s)
- Type: list of strings
- In config_template.cfg:
MARKER_ZONE_INTERFACE= ( NONE ) - Mentioned in: Basics of Multi-Zone Computations, Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane, Solid-to-Solid Conjugate Heat Transfer with Contact Resistance, Static Conjugate Heat Transfer (CHT) and 1 more
- Used in 50 test case files, for example:
cht_2d_3cylinders.cfg((cylinder_outer1, cylinder_inner1, cylinder_outer2, cylinder_inner2, cylinder_outer3, cylinder_inner3)),chtMaster.cfg(( cylinder_fluid, cylinder_solid )),circles.cfg((OUTMIX, INMIX)) - Code:
CConfig.cppline 1635
MARKER_CHT_INTERFACE
CHT interface boundary marker(s)
- Type: list of strings
- In config_template.cfg:
MARKER_CHT_INTERFACE= ( NONE ) - Mentioned in: Setup Guide: Heat Transfer and Conjugate Heat Transfer, Solid-to-Solid Conjugate Heat Transfer with Contact Resistance, Static Conjugate Heat Transfer (CHT)
- Used in 15 test case files, for example:
cht_2d_3cylinders.cfg((cylinder_outer1, cylinder_inner1, cylinder_outer2, cylinder_inner2, cylinder_outer3, cylinder_inner3)),chtMaster.cfg(( cylinder_fluid, cylinder_solid )),configFEA.cfg(( wallS )) - Code:
CConfig.cppline 1637
CHT_INTERFACE_CONTACT_RESISTANCE
: Thermal contact resistance values for each CHT inerface.
- Type: list of real numbers
- Not in config_template.cfg.
- Mentioned in: Changes in Version 8, Setup Guide: Heat Transfer and Conjugate Heat Transfer, Solid-to-Solid Conjugate Heat Transfer with Contact Resistance
- Code:
CConfig.cppline 1639
MARKER_INTERNAL
Internal boundary marker(s)
More in config_template.cfg: Internal boundary marker(s) e.g. no boundary condition (NONE = no marker)
- Type: list of strings
- In config_template.cfg:
MARKER_INTERNAL= ( NONE ) - Used in 4 test case files, for example:
Arina2KRS.cfg(( NONE )),naca0012.cfg(( FWH1 )) - Code:
CConfig.cppline 1641
MARKER_CUSTOM
Custom boundary marker(s)
More in config_template.cfg: Custom boundary marker(s) (this has to be implemented by users in the code).
- Type: list of strings
- In config_template.cfg:
MARKER_CUSTOM= ( NONE ) - Used in 18 test case files, for example:
Ringleb.cfg(( BottomBoundary, LeftBoundary, RightBoundary, TopBoundary )),Ringleb_WallBC.cfg(( BottomBoundary, TopBoundary )),lam_mms_dg_3d.cfg(( PlaneZ0 )) - Code:
CConfig.cppline 1643
MARKER_PERIODIC
Periodic boundary marker(s) Format: ( periodic marker, donor marker, rotation_center_x, rotation_center_y, rotation_center_z, rotation_angle_x-axis, rotation_angle_y-axis, rotation_angle_z-axis, translation_x, translation_y, translation_z, … )
More in config_template.cfg: Periodic boundary marker(s) (NONE = no marker) Format: ( periodic marker, donor marker, rotation_center_x, rotation_center_y, rotation_center_z, rotation_angle_x-axis, rotation_angle_y-axis, rotation_angle_z-axis, translation_x, translation_y, translation_z, … )
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_PERIODIC= ( NONE ) - Mentioned in: Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Incompressible Flows, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane, Streamwise Periodic Flow
- Used in 32 test case files, for example:
backwardStep.cfg(( Y-2, Y2, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.05, 0.0)),circles.cfg(( PER1, PER2, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 20.0, 0.0, PER3, PER4, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 20.0, 0.0)),Axial_stage2D.cfg(( periodic1, periodic2, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.04463756775, 0.0, periodic3, periodic4, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.04463756775, 0.0)) - Code:
CConfig.cppline 1648
MARKER_PYTHON_CUSTOM
Python customizable marker(s)
More in config_template.cfg: Marker(s) of the surface where custom thermal BC’s are defined.
- Type: list of strings
- In config_template.cfg:
MARKER_PYTHON_CUSTOM = ( NONE ) - Mentioned in: Flamelet Solver — Python Wrapper Wall Boundary Conditions, User Defined combustion model with Python
- Used in 2 test case files, for example:
Arina2KRS.cfg(( NONE )),unsteady_CHT_FlatPlate_Conf.cfg((plate)) - Code:
CConfig.cppline 1652
PYTHON_CUSTOM_SOURCE
Python custom source
- Type: YES / NO
- Default:
NO - Not in config_template.cfg.
- Mentioned in: Changes in Version 8, User Defined combustion model with Python, Wind velocity and pollutant dispersion in a city
- Used in 2 test case files, for example:
lam_buoyancy_cavity.cfg(YES) - Code:
CConfig.cppline 1655
MARKER_WALL_FUNCTIONS
Viscous wall markers for which wall functions must be applied. Format: (Wall function marker, wall function type, …)
More in config_template.cfg: Viscous wall markers for which wall functions must be applied. (NONE = no marker) Format: ( marker name, wall function type -NO_WALL_FUNCTION, STANDARD_WALL_FUNCTION, ADAPTIVE_WALL_FUNCTION, SCALABLE_WALL_FUNCTION, EQUILIBRIUM_WALL_MODEL, NONEQUILIBRIUM_WALL_MODEL-, … )
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_WALL_FUNCTIONS= ( airfoil, NO_WALL_FUNCTION ) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Steady RANS for External Aerodynamics, Setup Guide: Turbomachinery, Wall Treatment: Wall Functions and Roughness, Aachen turbine stage with Mixing-plane, Turbulent Bend with wall functions
- Used in 6 test case files, for example:
aachen_3D_MP_restart.cfg(( BLADE1, STANDARD_WALL_FUNCTION , BLADE2, STANDARD_WALL_FUNCTION , BLADE3, STANDARD_WALL_FUNCTION , HUB1, STANDARD_WALL_FUNCTION , SHROUD1, STANDARD_WALL_FUNCTION , HUB2, STANDARD_WALL_FUNCTION , SHROUD2, STANDARD_WALL_FUNCTION , HUB3, STANDARD_WALL_FUNCTION , SHROUD3, STANDARD_WALL_FUNCTION )),turb_SA_flatplate.cfg(( wall, STANDARD_WALL_FUNCTION )) - Code:
CConfig.cppline 1659
MARKER_SPECIES_STRONG_BC
Markers where a strong BC must be applied.
- Type: list of strings
- Not in config_template.cfg.
- Mentioned in: Changes in Version 8, Setup Guide: Species Transport and Combustion, Composition-Dependent model for Species Transport equations, Incompressible, Laminar Combustion Simulation, Species Transport
- Used in 12 test case files, for example:
lam_prem_ch4_cfd.cfg((inlet, outlet, wall)),lam_prem_ch4_hx_ad.cfg((inlet, wall_burner, wall_hx)),lam_prem_ch4_cht_cfd_fluid.cfg((inlet, outlet, wall_burner)) - Code:
CConfig.cppline 1663
ACTDISK_TYPE
Actuator Disk boundary type
More in config_template.cfg: Actuator disk boundary type (VARIABLE_LOAD, VARIABLES_JUMP, BC_THRUST, DRAG_MINUS_THRUST, BLADE_ELEMENT)
- Type: one of the values below
- Values:
VARIABLES_JUMP,BC_THRUST,NET_THRUST,DRAG_MINUS_THRUST,MASSFLOW,POWER,VARIABLE_LOAD,BLADE_ELEMENT - Default:
VARIABLES_JUMP - In config_template.cfg:
ACTDISK_TYPE= VARIABLES_JUMP - Mentioned in: Changes in Version 8, Actuator Disk With Variable Load
- Used in 3 test case files, for example:
actuatordisk_bem.cfg(BLADE_ELEMENT),propeller_variable_load.cfg(VARIABLE_LOAD),propeller.cfg(VARIABLES_JUMP) - Code:
CConfig.cppline 1666
MARKER_ACTDISK
Actuator disk boundary marker(s) with the following formats (NONE = no marker) Variable Load: (inlet face marker, outlet face marker, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0) Variables Jump: ( inlet face marker, outlet face marker, Takeoff pressure jump (psf), Takeoff temperature jump (R), Takeoff rev/min, Cruise pressure jump (psf), Cruise temperature jump (R), Cruise rev/min ) BC Thrust: ( inlet face marker, outlet face marker, Takeoff BC thrust (lbs), 0.0, Takeoff rev/min, Cruise BC thrust (lbs), 0.0, Cruise rev/min ) Drag-Thrust: ( inlet face marker, outlet face marker, Takeoff Drag-Thrust (lbs), 0.0, Takeoff rev/min, Cruise Drag-Thrust (lbs), 0.0, Cruise rev/min ) Blade element: ( inlet face marker, outlet face marker, Takeoff Drag-Thrust (lbs), 0.0, Takeoff rev/min, Cruise Drag-Thrust (lbs), 0.0, Cruise rev/min ) (from config_template.cfg)
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_ACTDISK= ( NONE ) - Mentioned in: Actuator Disk With Variable Load
- Used in 3 test case files, for example:
actuatordisk_bem.cfg(( ACTDISK_IN, ACTDISK_OUT , 0.0, 0.0, 12715.2, 0.0, 0.0, 12715.2)),propeller_variable_load.cfg(( DISK, DISK_BACK, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0 )),propeller.cfg(( ACTDISK, ACTDISK_BACK, 70.5, 10, 0, 70.5, 10, 0 )) - Code:
CConfig.cppline 1669
MARKER_ACTDISK_BEM_CG
Actuator disk CG for blade element momentum (BEM) method.
More in config_template.cfg: Blade element: ( inlet face marker, outlet face marker, X_CG of inlet, Y_CG of inlet, Z_CG of inlet, X_CG of outlet, Y_CG of outlet, Z_CG of outlet )
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_ACTDISK_BEM_CG= ( NONE ) - Used in 1 test case file, for example:
actuatordisk_bem.cfg(( ACTDISK_IN, ACTDISK_OUT, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0 )) - Code:
CConfig.cppline 1674
MARKER_ACTDISK_BEM_AXIS
Actuator disk axis for blade element momentum (BEM) method.
More in config_template.cfg: Blade element: ( inlet face marker, outlet face marker, X_Axis of inlet, Y_Axis of inlet, Z_Axis of inlet, X_Axis of outlet, Y_Axis of outlet, Z_Axis of outlet )
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_ACTDISK_BEM_AXIS= ( NONE ) - Used in 1 test case file, for example:
actuatordisk_bem.cfg(( ACTDISK_IN, ACTDISK_OUT, 1.0, 0.0, 0.0, 1.0, 0.0, 0.0 )) - Code:
CConfig.cppline 1679
ACTDISK_FILENAME
Input file for a specified actuator disk (w/ extension)
More in config_template.cfg: Actuator disk data input file name
- Type: string
- Default:
string("actdiskinput.dat") - In config_template.cfg:
ACTDISK_FILENAME= actuatordisk.dat - Mentioned in: Actuator Disk With Variable Load
- Used in 1 test case file, for example:
propeller_variable_load.cfg(ActuatorDisk.dat) - Code:
CConfig.cppline 1684
INLET_TYPE
Inlet boundary type
More in config_template.cfg: Inlet boundary type (TOTAL_CONDITIONS, MASS_FLOW)
- Type: one of the values below
- Values:
TOTAL_CONDITIONS,MASS_FLOW,INPUT_FILE,VELOCITY_INLET,PRESSURE_INLET - Default:
TOTAL_CONDITIONS - In config_template.cfg:
INLET_TYPE= TOTAL_CONDITIONS - Mentioned in: Markers and Boundary Conditions, Inviscid Bump in a Channel
- Used in 12 test case files, for example:
Arina2KRS.cfg(TOTAL_CONDITIONS),inv_cylinder3D.cfg(MASS_FLOW) - Code:
CConfig.cppline 1687
INLET_USE_NORMAL
Use the local boundary normal for the flow direction with pressure inlets.
More in config_template.cfg: Impose inlet velocity magnitude in the direction of the normal of the inlet face. used for incompressible velocity inlet and for compressible pressure and mass flow inlets.
- Type: YES / NO
- Default:
NO - In config_template.cfg:
INLET_USE_NORMAL= NO - Mentioned in: Changes in Version 8
- Code:
CConfig.cppline 1689
INC_INLET_TYPE
List of inlet types for incompressible flows. List length must match number of inlet markers. Options: VELOCITY_INLET, PRESSURE_INLET, INPUT_FILE.
- Type: list of the values below
- Values:
TOTAL_CONDITIONS,MASS_FLOW,INPUT_FILE,VELOCITY_INLET,PRESSURE_INLET - In config_template.cfg:
INC_INLET_TYPE= VELOCITY_INLET - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Setup Guide: Species Transport and Combustion, Composition-Dependent model for Species Transport equations, Inviscid Hydrofoil, Turbulent Bend with wall functions
- Used in 53 test case files, for example:
backwardStep.cfg(VELOCITY_INLET),lam_partial_prem_ch4_cfd.cfg(VELOCITY_INLET,VELOCITY_INLET),inv_nozzle.cfg(PRESSURE_INLET) - Code:
CConfig.cppline 1691
SPECIFIED_INLET_PROFILE
Read inlet profile from a file (YES, NO) default: NO (from config_template.cfg)
- Type: YES / NO
- Default:
NO - In config_template.cfg:
SPECIFIED_INLET_PROFILE= NO - Mentioned in: Setup Guide: Incompressible Flows, Composition-Dependent model for Species Transport equations, Laminar Backward-facing Step, Turbulent Bend with wall functions
- Used in 25 test case files, for example:
def_intersect.cfg(NO),config.cfg(YES) - Code:
CConfig.cppline 1692
INLET_FILENAME
Input file for a specified inlet profile (w/ extension)
More in config_template.cfg: File specifying inlet profile
- Type: string
- Default:
string("inlet.dat") - In config_template.cfg:
INLET_FILENAME= inlet.dat - Mentioned in: Setup Guide: Incompressible Flows, Laminar Backward-facing Step, Turbulent Bend with wall functions
- Used in 23 test case files, for example:
def_intersect.cfg(inletVelocity.dat),config.cfg(inlet.dat),profile_poiseuille.cfg(inlet_poiseuille.dat) - Code:
CConfig.cppline 1694
INLET_MATCHING_TOLERANCE
If a file is provided to specify the inlet profile, this tolerance will be used to match the coordinates in the input file to the points on the grid.
- Type: real number
- Default:
1e-6 - In config_template.cfg:
% INLET_MATCHING_TOLERANCE= 1e-6 - Used in 4 test case files, for example:
def_intersect.cfg(1e-5),psi.cfg(1e-4) - Code:
CConfig.cppline 1699
MARKER_INLET
Inlet boundary marker(s) with the following formats, Total Conditions: (inlet marker, total temp, total pressure, flow_direction_x, flow_direction_y, flow_direction_z, … ) where flow_direction is a unit vector. Mass Flow: (inlet marker, density, velocity magnitude, flow_direction_x, flow_direction_y, flow_direction_z, … ) where flow_direction is a unit vector.
More in config_template.cfg: Inlet boundary marker(s) with the following formats (NONE = no marker) Total Conditions: (inlet marker, total temp, total pressure, flow_direction_x, flow_direction_y, flow_direction_z, … ) where flow_direction is a unit vector. Mass Flow: (inlet marker, density, velocity magnitude, flow_direction_x, flow_direction_y, flow_direction_z, … ) where flow_direction is a unit vector. Inc. Velocity: (inlet marker, temperature, velocity magnitude, flow_direction_x, flow_direction_y, flow_direction_z, … ) where flow_direction is a unit vector. Inc. Pressure: (inlet marker, temperature, total pressure, flow_direction_x, flow_direction_y, flow_direction_z, … ) where flow_direction is a unit vector.
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_INLET= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Species Transport and Combustion, Setup Guide: Turbomachinery, Setup Guide: Unsteady Flows and DES and 9 more
- Used in 93 test case files, for example:
backwardStep.cfg(( INLET, 298.333, 44.316, 1.0, 0.0, 0.0 )),ddes_flatplate.cfg(( inlet, 302.4, 118309.784, 1.0, 0.0, 0.0 )),def_intersect.cfg((inlet, 300.0, 1.0, 1.0, 0.0, 0.0)) - Code:
CConfig.cppline 1707
MARKER_INLET_SPECIES
Inlet Species boundary marker(s) with the following format Inlet Species: (inlet_marker, Species1, Species2, …, SpeciesN-1, inlet_marker2, Species1, Species2, …)
More in config_template.cfg: Inlet Species boundary marker(s) with the following format: (inlet_marker, Species1, Species2, …, SpeciesN-1, inlet_marker2, Species1, Species2, …) For N species, N-1 transport equations are solved, the last one Y_N is solved algebraically as 1-(sum of the species 1 to (N-1))
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_INLET_SPECIES= (inlet, 0.5, ..., inlet2, 0.6, ...) - Mentioned in: Setup Guide: Species Transport and Combustion, Composition-Dependent model for Species Transport equations, Incompressible, Laminar Combustion Simulation, Incompressible, Laminar counterflow diffusion flame, Species Transport
- Used in 31 test case files, for example:
air_nozzle_species.cfg(( INFLOW, 0.5 )),lam_prem_ch4_cfd.cfg((inlet, 0, -193600.0, 0.0, 0.0)),lam_prem_ch4_hx_ad.cfg((inlet, 0.0, 0.0, 0.0, 0.0)) - Code:
CConfig.cppline 1710
MARKER_INLET_TURBULENT
Inlet Turbulence boundary marker(s) with the following format Inlet Turbulent: (inlet_marker, TurbulentIntensity1, ViscosityRatio1, inlet_marker2, TurbulentIntensity2, ViscosityRatio2, …)
More in config_template.cfg: Inlet Turbulent boundary marker(s) with the following format: SA Model: (inlet_marker1, NuFactor1, inlet_marker2, NuFactor2, …) SST Model: (inlet_marker1, TurbIntensity1, RatioTurbLamViscosity1, inlet_marker2, TurbIntensity2, RatioTurbLamViscosity2, …)
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_INLET_TURBULENT= (inlet1, 0.05, 15, inlet2, 0.02, ...) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Transition Models, Turbulence Models, Composition-Dependent model for Species Transport equations, Turbulent Bend with wall functions
- Used in 4 test case files, for example:
psi.cfg((inlet, 0.10, 15)),species2_primitiveVenturi_mixingmodel_TURBULENT_MARKERS.cfg((gas_inlet, 0.05, 15\),species2_primitiveVenturi_mixingmodel_viscosity.cfg((gas_inlet, 5.0, \) - Code:
CConfig.cppline 1714
MARKER_RIEMANN
Riemann boundary marker(s) with the following formats, a unit vector.
More in config_template.cfg: Riemann boundary marker(s) (NONE = no marker) Format: (marker, data kind flag, list of data)
- Type: special format, see config_template.cfg
- Values: See Riemann_Map. The variables indicated by the option and the flow direction unit vector must be specified.
- In config_template.cfg:
MARKER_RIEMANN= ( NONE ) - Mentioned in: Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Turbomachinery, Non-ideal compressible flow in a supersonic nozzle
- Used in 27 test case files, for example:
air_nozzle_restart.cfg(( INFLOW, TOTAL_CONDITIONS_PT, 1400000.0, 373.15, 1.0, 0.0, 0.0, \),turb_SA_PR.cfg((inflow, TOTAL_CONDITIONS_PT, 13.8686E+05, 592.295, 1.0, 0.0, 0.0, outflow, STATIC_PRESSURE, 11.00E+05, 0.0, 0.0, 0.0, 0.0)),fluidModel.cfg(( INFLOW, TOTAL_CONDITIONS_PT, 904388, 542.13, 1.0, 0.0, 0.0, OUTFLOW, STATIC_PRESSURE, 200000.0, 0.0, 0.0, 0.0, 0.0 )) - Code:
CConfig.cppline 1717
MARKER_WALL_SPECIES
Wall species boundary marker(s) with the following format: (marker_name, BC_TYPE, value, BC_TYPE, value, …) where BC_TYPE is either FLUX (Neumann) or VALUE (Dirichlet). Each marker must specify the same number of species (N species per marker).
More in config_template.cfg: Wall species boundary condition marker(s) for species transport (NONE = no marker) Specify either a Neumann flux boundary condition (FLUX) or a Dirichlet value boundary condition (VALUE) for each species independently. All markers must specify the same number of species. Format: ( marker_name, BC_TYPE_1, value_1, BC_TYPE_2, value_2, …, BC_TYPE_N, value_N, … ) where BC_TYPE is either FLUX (Neumann) or VALUE (Dirichlet) for each species Example for 3 species: MARKER_WALL_SPECIES= (wall1, FLUX, 0.0, VALUE, 0.3, VALUE, 0.2, wall2, VALUE, 0.1, VALUE, 0.4, FLUX, 0.0) If MARKER_WALL_SPECIES is not specified, a zero-flux boundary condition will be used.
- Type: special format, see config_template.cfg
- Values: See Wall_Map.
- In config_template.cfg:
MARKER_WALL_SPECIES= ( NONE ) - Mentioned in: Changes in Version 8, Flamelet Solver — Python Wrapper Wall Boundary Conditions, Setup Guide: Species Transport and Combustion, Incompressible, Laminar counterflow diffusion flame
- Used in 1 test case file, for example:
species3_primitiveVenturi_flux_value.cfg(( wall, VALUE, 1.0, FLUX, 0.01 )) - Code:
CConfig.cppline 1722
MARKER_GILES
Giles boundary marker(s) with the following formats, a unit vector.
More in config_template.cfg: Giles boundary condition for inflow, outflow and mixing-plane Format inlet: ( marker, TOTAL_CONDITIONS_PT, Total Pressure , Total Temperature, Flow dir-norm, Flow dir-tang, Flow dir-span, under-relax-avg, under-relax-fourier) Format outlet: ( marker, STATIC_PRESSURE, Static Pressure value, -, -, -, -, under-relax-avg, under-relax-fourier) Format mixing-plane in and out: ( marker, MIXING_IN or MIXING_OUT, -, -, -, -, -, -, under-relax-avg, under-relax-fourier)
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_GILES= ( NONE ) - Mentioned in: Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 9 test case files, for example:
Arina2KRS.cfg(( NONE )),circles.cfg((INFLOW, TOTAL_CONDITIONS_PT, 1E6, 300, 1.0, 0.0, 0.0,1.0,1.0, OUTMIX, MIXING_OUT, 0.0, 0.0, 0.0, 0.0, 0.0,1.0,1.0, INMIX, MIXING_IN, 0.0, 0.0, 0.0, 0.0, 0.0,1.0, 1.0, OUTFLOW, STATIC_PRESSURE, 9E5, 0.0, 0.0, 0.0, 0.0,1.0,1.0)),Axial_stage2D.cfg((inflow, TOTAL_CONDITIONS_PT, 169623.33, 305.76, 1.0, 0.0, 0.0,1.0,1.0, outmix, MIXING_OUT, 0.0, 0.0, 0.0, 0.0, 0.0,1.0,1.0, inmix, MIXING_IN, 0.0, 0.0, 0.0, 0.0, 0.0,1.0, 1.0 outflow, STATIC_PRESSURE, 99741.00, 0.0, 0.0, 0.0, 0.0,1.0,1.0)) - Code:
CConfig.cppline 1725
SPATIAL_FOURIER
Option to compute the spatial fourier trasformation for the Giles BC.
More in config_template.cfg: YES Non reflectivity activated, NO the Giles BC behaves as a normal 1D characteristic-based BC
- Type: YES / NO
- Default:
NO - In config_template.cfg:
SPATIAL_FOURIER= NO - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 8 test case files, for example:
circles.cfg(YES),Jones_restart.cfg(NO) - Code:
CConfig.cppline 1727
GILES_EXTRA_RELAXFACTOR
the 1st coeff the value of the under relaxation factor to apply to the shroud and hub, the 2nd coefficient is the the percentage of span-wise height influenced by this extra under relaxation factor.
More in config_template.cfg: This option insert an extra under relaxation factor for the Giles BC at the hub and shroud (under relax factor applied, span percentage to under relax)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
GILES_EXTRA_RELAXFACTOR= ( 0.05, 0.05) - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 3 test case files, for example:
Jones_restart.cfg((0.05, 0.05)) - Code:
CConfig.cppline 1731
MIXINGPLANE_INTERFACE_KIND
types of mixing process for averaging quantities at the boundaries.
More in config_template.cfg: Specify kind of interpolation for the mixing-plane (LINEAR_INTERPOLATION, NEAREST_SPAN, MATCHING)
- Type: one of the values below
- Values:
MATCHING,NEAREST_SPAN,LINEAR_INTERPOLATION - Default:
NEAREST_SPAN - In config_template.cfg:
MIXINGPLANE_INTERFACE_KIND= LINEAR_INTERPOLATION - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 3 test case files, for example:
Jones_restart.cfg(LINEAR_INTERPOLATION) - Code:
CConfig.cppline 1734
AVERAGE_PROCESS_KIND
types of mixing process for averaging quantities at the boundaries.
More in config_template.cfg: Specify Kind of average process for linearizing the Navier-Stokes equation at inflow and outflow BCs included at the mixing-plane interface (ALGEBRAIC, AREA, MASSSFLUX, MIXEDOUT) default AREA
- Type: one of the values below
- Values:
ALGEBRAIC,AREA,MIXEDOUT,MASSFLUX - Default:
AREA - In config_template.cfg:
AVERAGE_PROCESS_KIND= MIXEDOUT - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 8 test case files, for example:
circles.cfg(MIXEDOUT) - Code:
CConfig.cppline 1737
PERFORMANCE_AVERAGE_PROCESS_KIND
types of mixing process for averaging quantities at the boundaries for performance computation.
More in config_template.cfg: Specify Kind of average process for computing turbomachinery performance parameters (ALGEBRAIC, AREA, MASSSFLUX, MIXEDOUT) default AREA
- Type: one of the values below
- Values:
ALGEBRAIC,AREA,MIXEDOUT,MASSFLUX - Default:
AREA - In config_template.cfg:
PERFORMANCE_AVERAGE_PROCESS_KIND= MIXEDOUT - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 8 test case files, for example:
circles.cfg(MIXEDOUT) - Code:
CConfig.cppline 1740
MIXEDOUT_COEFF
the 1st coeff is an under relaxation factor for the Newton method, the 2nd coefficient is the tolerance for the Newton method, 3rd coefficient is the maximum number of iteration for the Newton Method.
More in config_template.cfg: Parameters of the Newton method for the MIXEDOUT average algorithm (under relaxation factor, tollerance, max number of iterations)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
MIXEDOUT_COEFF= (1.0, 1.0E-05, 15) - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 8 test case files, for example:
circles.cfg((1.0, 1.0E-05, 15)),multi_interface_rst.cfg((1.0, 1.0E-05, 100)) - Code:
CConfig.cppline 1745
RAMP_MOTION_FRAME
option to ramp up or down the frame of motion velocity value
More in config_template.cfg: Specify ramp option for frame of motion (YES, NO) default NO
- Type: YES / NO
- Default:
NO - In config_template.cfg:
RAMP_MOTION_FRAME= YES - Mentioned in: Changes in Version 8, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 3 test case files, for example:
rotor.cfg(YES),rotor_restart.cfg(NO) - Code:
CConfig.cppline 1747
RAMP_MOTION_FRAME_COEFF
the 1st coeff is the staring outlet value, the 2nd coeff is the number of iterations for the update, 3rd is the number of total iteration till reaching the final outlet pressure value
More in config_template.cfg: Parameters of the frame of motion ramp (starting frame of motion speed, updating-iteration-frequency, total number of iteration for the ramp)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
RAMP_MOTION_FRAME_COEFF= (0.0, 39.0, 500) - Mentioned in: Changes in Version 8, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 3 test case files, for example:
rotor.cfg((0.0, 39.0, 500)) - Code:
CConfig.cppline 1751
AVERAGE_MACH_LIMIT
AVERAGE_MACH_LIMIT is a limit value for average procedure based on the mass flux.
More in config_template.cfg: Limit of Mach number below which the mixedout algorithm is substituted with a AREA average algorithm to avoid numerical issues
- Type: real number
- Default:
0.03 - In config_template.cfg:
AVERAGE_MACH_LIMIT= 0.05 - Mentioned in: Setup Guide: Turbomachinery
- Used in 8 test case files, for example:
circles.cfg(0.05),transonic_stator.cfg(0.03) - Code:
CConfig.cppline 1753
RAMP_OUTLET
option to ramp up or down the Giles outlet value
More in config_template.cfg: Specify ramp option for Outlet Giles value (YES, NO) default NO
- Type: YES / NO
- Default:
NO - In config_template.cfg:
RAMP_OUTLET= NO - Mentioned in: Changes in Version 8, Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 7 test case files, for example:
Axial_stage2D.cfg(NO) - Code:
CConfig.cppline 1755
RAMP_OUTLET_COEFF
the 1st coeff is the staring outlet value, the 2nd coeff is the number of iterations for the update, 3rd is the number of total iteration till reaching the final outlet pressure value
More in config_template.cfg: Parameters of the outlet Giles ramp (starting outlet value, updating-iteration-frequency, total number of iteration for the ramp)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
RAMP_OUTLET_COEFF= (400000.0, 10.0, 500) - Mentioned in: Changes in Version 8, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 6 test case files, for example:
Axial_stage2D.cfg((140000.0, 10.0, 2000)),transonic_stator.cfg((700000.0, 10.0, 500)),Jones_restart.cfg((400000.0, 10.0, 500)) - Code:
CConfig.cppline 1759
MARKER_MIXINGPLANE_INTERFACE
Identify the boundaries in which the mixing plane is applied.
More in config_template.cfg: Mixing-plane interface markers must be specified to activate the transfer of information between zones
- Type: list of strings
- In config_template.cfg:
MARKER_MIXINGPLANE_INTERFACE= ( NONE ) - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 7 test case files, for example:
Arina2KRS.cfg(( NONE )),circles.cfg((OUTMIX, INMIX)),Axial_stage2D.cfg((outmix, inmix)) - Code:
CConfig.cppline 1761
TURBULENT_MIXINGPLANE
Activate mixing plane also for turbulent quantities
More in config_template.cfg: Specify option for turbulent mixing-plane (YES, NO) default NO
- Type: YES / NO
- Default:
NO - In config_template.cfg:
TURBULENT_MIXINGPLANE= YES - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 6 test case files, for example:
circles.cfg(YES) - Code:
CConfig.cppline 1763
RELATIVE_FRAME_SLIDINGPLANE
Activate sliding plane for relative frame
- Type: YES / NO
- Default:
NO - Not in config_template.cfg.
- Code:
CConfig.cppline 1765
MARKER_TURBOMACHINERY
Identify the boundaries for which the turbomachinery settings are applied.
More in config_template.cfg: Inflow and Outflow markers must be specified, for each blade (zone), following the natural groth of the machine (i.e, from the first blade to the last)
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_TURBOMACHINERY= ( NONE ) - Mentioned in: Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 9 test case files, for example:
Arina2KRS.cfg(( NONE )),circles.cfg((INFLOW, OUTMIX, INMIX, OUTFLOW)),Axial_stage2D.cfg((inflow, outmix, inmix, outflow)) - Code:
CConfig.cppline 1767
NUM_SPANWISE_SECTIONS
Integer number of spanwise sections to compute 3D turbo BC and Performance for turbomachinery
- Type: integer
- Default:
1 - In config_template.cfg:
NUM_SPANWISE_SECTIONS= 1 - Mentioned in: Setup Guide: Turbomachinery
- Code:
CConfig.cppline 1769
SPANWISE_KIND
type of algorithm to identify the span-wise sections at the turbo boundaries.
More in config_template.cfg: type of algorithm to identify the span-wise sections at the turbo boundaries. 1 means automatic.
- Type: one of the values below
- Values:
AUTOMATIC,EQUISPACED - Default:
AUTOMATIC - In config_template.cfg:
SPANWISE_KIND= 1 - Mentioned in: Setup Guide: Turbomachinery
- Code:
CConfig.cppline 1772
TURBOMACHINERY_KIND
types of turbomachinery architecture.
More in config_template.cfg: Specify kind of architecture for each zone (AXIAL, CENTRIPETAL, CENTRIFUGAL, CENTRIPETAL_AXIAL, AXIAL_CENTRIFUGAL)
- Type: list of the values below
- Values:
AXIAL,CENTRIFUGAL,CENTRIPETAL,CENTRIPETAL_AXIAL,AXIAL_CENTRIFUGAL - Default:
AXIAL - In config_template.cfg:
TURBOMACHINERY_KIND= CENTRIPETAL CENTRIPETAL_AXIAL - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 8 test case files, for example:
circles.cfg(AXIAL AXIAL),transonic_stator.cfg(AXIAL),Jones_restart.cfg(CENTRIPETAL CENTRIPETAL_AXIAL) - Code:
CConfig.cppline 1775
TURBO_PERF_KIND
types of turbomachynery Performance Calculations.
- Type: list of the values below
- Values:
TURBINE,COMPRESSOR,PROPELLOR - Default:
TURBINE - In config_template.cfg:
TURBO_PERF_KIND = TURBINE TURBINE - Mentioned in: Changes in Version 8, Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 10 test case files, for example:
circles.cfg(TURBINE TURBINE),transonic_stator.cfg(TURBINE),aachen_3D_MP_restart.cfg((TURBINE, TURBINE, TURBINE)) - Code:
CConfig.cppline 1778
MARKER_SHROUD
markers in which velocity is forced to 0.0. Format: (shroud1, shroud2, …)
More in config_template.cfg: Shroud boundary marker(s) (NONE = no marker) Format: (marker) If the ROTATING_FRAME option is activated, this option force the velocity on the boundaries specified to 0.0
- Type: list of strings
- In config_template.cfg:
MARKER_SHROUD= (NONE) - Mentioned in: Setup Guide: Turbomachinery, Aachen turbine stage with Mixing-plane
- Used in 2 test case files, for example:
Arina2KRS.cfg((NONE)),aachen_3D_MP_restart.cfg((SHROUD1, SHROUD2, SHROUD3)) - Code:
CConfig.cppline 1781
MARKER_SUPERSONIC_INLET
Supersonic inlet boundary marker(s) Format: (inlet marker, temperature, static pressure, velocity_x, velocity_y, velocity_z, … ), i.e. primitive variables specified.
More in config_template.cfg: Supersonic inlet boundary marker(s) (NONE = no marker) Format: (inlet marker, temperature, static pressure, velocity_x, velocity_y, velocity_z, … ), i.e. primitive variables specified.
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_SUPERSONIC_INLET= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Inviscid Supersonic Wedge
- Used in 15 test case files, for example:
inv_wedge_ROE.cfg(( inlet, 300.0, 100000.0, 695.4290761824674, 0.0, 0.0 )),invwedge_ss_inlet.cfg(( Inlet, 288.15, 101325.0, 1705.16, 0.0, 0.0 )),NACA64206.cfg((Inlet,216.6499,11662.0,472.1153,0,0)) - Code:
CConfig.cppline 1784
MARKER_SUPERSONIC_OUTLET
Supersonic outlet boundary marker(s)
More in config_template.cfg: Supersonic outlet boundary marker(s) (NONE = no marker)
- Type: list of strings
- In config_template.cfg:
MARKER_SUPERSONIC_OUTLET= ( NONE ) - Used in 4 test case files, for example:
flatplate_supersonic.cfg(( OUTLET )),NACA64206.cfg((Outlet)),turb_SST_flatplate_compressibility_Sarkar.cfg((outlet, 34384.76396)) - Code:
CConfig.cppline 1786
MARKER_OUTLET
Outlet boundary marker(s) Format: ( outlet marker, back pressure (static), … )
More in config_template.cfg: Outlet boundary marker(s) (NONE = no marker) Compressible: ( outlet marker, back pressure (static thermodynamic), … ) Inc. Pressure: ( outlet marker, back pressure (static gauge in Pa), … ) Inc. Mass Flow: ( outlet marker, mass flow target (kg/s), … )
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_OUTLET= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Setup Guide: Non-Ideal Compressible Flows, Setup Guide: Species Transport and Combustion, Setup Guide: Turbomachinery, Setup Guide: Unsteady Flows and DES and 6 more
- Used in 114 test case files, for example:
backwardStep.cfg(( OUTLET, 500.0 )),inv_wedge_ROE.cfg(( outlet, 10000.0 )),ddes_flatplate.cfg(( outlet, 115056.0, farfield, 115056.0 )) - Code:
CConfig.cppline 1789
INC_OUTLET_TYPE
List of outlet types for incompressible flows. List length must match number of inlet markers. Options: PRESSURE_OUTLET, MASS_FLOW_OUTLET.
More in config_template.cfg: List of outlet types for incompressible flows. List length must match number of outlet markers. Options: PRESSURE_OUTLET, MASS_FLOW_OUTLET
- Type: list of the values below
- Values:
PRESSURE_OUTLET,MASS_FLOW_OUTLET - In config_template.cfg:
INC_OUTLET_TYPE= PRESSURE_OUTLET - Mentioned in: Markers and Boundary Conditions, Setup Guide: Incompressible Flows, Setup Guide: Species Transport and Combustion, Composition-Dependent model for Species Transport equations, Inviscid Hydrofoil, Turbulent Bend with wall functions
- Used in 50 test case files, for example:
backwardStep.cfg(PRESSURE_OUTLET),inv_nozzle.cfg(MASS_FLOW_OUTLET),cylinder_split.cfg(( PRESSURE_OUTLET )) - Code:
CConfig.cppline 1791
MARKER_ISOTHERMAL
Isothermal wall boundary marker(s) Format: ( isothermal marker, wall temperature (static), … )
More in config_template.cfg: Navier-Stokes (no-slip), isothermal wall marker(s) (NONE = no marker) Format: ( marker name, constant wall temperature (K), … )
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_ISOTHERMAL= ( NONE ) - Mentioned in: Flamelet Solver — Python Wrapper Wall Boundary Conditions, Markers and Boundary Conditions, Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Incompressible Flows, Setup Guide: Species Transport and Combustion, Setup Guide: Steady RANS for External Aerodynamics and 5 more
- Used in 48 test case files, for example:
solid_cylinder1.cfg(( core1, 350.0 )),solid_cylinder2.cfg(( core2, 350.0 )),solid_cylinder3.cfg(( core3, 350.0 )) - Code:
CConfig.cppline 1794
MARKER_HEATFLUX
Specified heat flux wall boundary marker(s) Format: ( Heat flux marker, wall heat flux (static), … )
More in config_template.cfg: Navier-Stokes (no-slip), constant heat flux wall marker(s) (NONE = no marker) Format: ( marker name, constant heat flux (J/m^2), … )
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_HEATFLUX= ( NONE ) - Mentioned in: Flamelet Solver — Python Wrapper Wall Boundary Conditions, Markers and Boundary Conditions, Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Incompressible Flows, Setup Guide: Laminar-Turbulent Transition, Setup Guide: Non-Ideal Compressible Flows and 14 more
- Used in 183 test case files, for example:
air_nozzle_restart.cfg(( WALL, 0.0 )),backwardStep.cfg(( WALL_TOP, 0.0, WALL_BOTTOM, 0.0 )),config.cfg(( OuterWall, 0.0, InnerWall, 0.0 )) - Code:
CConfig.cppline 1797
INTEGRATED_HEATFLUX
Prescribe Heatflux in [W] instead of [W/m^2] \default false
- Type: YES / NO
- Default:
NO - Not in config_template.cfg.
- Mentioned in: Markers and Boundary Conditions, Setup Guide: Heat Transfer and Conjugate Heat Transfer
- Used in 1 test case file, for example:
configSolid.cfg(YES) - Code:
CConfig.cppline 1799
MARKER_HEATTRANSFER
Heat flux with specified heat transfer coefficient boundary marker(s) Format: ( Heat transfer marker, heat transfer coefficient, wall temperature (static), … )
More in config_template.cfg: Navier-Stokes (no-slip), heat-transfer/convection wall marker(s) (NONE = no marker) Available for compressible and incompressible flow. Format: ( marker name, constant heat-transfer coefficient (J/(K*m^2)), constant reservoir Temperature (K) … )
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_HEATTRANSFER= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Setup Guide: Heat Transfer and Conjugate Heat Transfer, Setup Guide: Incompressible Flows, Wall Treatment: Wall Functions and Roughness
- Used in 1 test case file, for example:
BC_HeatTransfer.cfg(( fluid_pin1_interface, 100000000.0, 400, \) - Code:
CConfig.cppline 1802
MARKER_SMOLUCHOWSKI_MAXWELL
moluchowski/Maxwell wall boundary marker(s) Slip velocity and temperature jump wall boundary marker(s) Format: ( Heat flux marker, wall temperature (static), momentum accomodation coefficient, thermal accomodation coefficient … )
More in config_template.cfg: Smoluchowski/Maxwell slip wall boundary marker(s)
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_SMOLUCHOWSKI_MAXWELL= ( NONE ) - Code:
CConfig.cppline 1805
WALL_ROUGHNESS
Specified roughness heights at wall boundary marker(s) Format: ( Wall marker, roughness_height (static), … )
More in config_template.cfg: The equivalent sand grain roughness height (k_s) on each of the wall. This must be in m. This is a list of (string, double) each element corresponding to a wall marker.
- Type: list of (string, real number) pairs
- In config_template.cfg:
WALL_ROUGHNESS = (wall1, ks1, wall2, ks2) - Mentioned in: Changes in Version 8, Hybrid RANS/LES (DES), Setup Guide: Steady RANS for External Aerodynamics, Wall Treatment: Wall Functions and Roughness
- Used in 5 test case files, for example:
pb_rough_flatplate_incomp.cfg((wall, 0.000246)),turb_SST_flatplate_roughBCAupoix.cfg((wall, 400e-6)) - Code:
CConfig.cppline 1808
MARKER_ENGINE_INFLOW
Engine inflow boundary marker(s) Format: ( nacelle inflow marker, fan face Mach, … )
More in config_template.cfg: Engine inflow boundary marker(s) (NONE = no marker) Format: (engine inflow marker, fan face Mach, … )
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_ENGINE_INFLOW= ( NONE ) - Used in 1 test case file, for example:
MFR_coupling.cfg(( FAN_IN, 140.0 )) - Code:
CConfig.cppline 1811
HIGHLITE_AREA
Highlite area
More in config_template.cfg: Highlite area to compute MFR (1 in2 by default)
- Type: real number
- Default:
1.0 - In config_template.cfg:
HIGHLITE_AREA= 1.0 - Used in 3 test case files, for example:
actuatordisk_bem.cfg(0.04411429),propeller_variable_load.cfg(19.8649),propeller.cfg(1.0) - Code:
CConfig.cppline 1813
FAN_POLY_EFF
Fan poly efficiency
More in config_template.cfg: Fan polytropic efficiency (1.0 by default)
- Type: real number
- Default:
1.0 - In config_template.cfg:
FAN_POLY_EFF= 1.0 - Code:
CConfig.cppline 1815
SUBSONIC_ENGINE
Engine subsonic intake region
More in config_template.cfg: Initialization with a subsonic flow around the engine.
- Type: YES / NO
- Default:
NO - In config_template.cfg:
SUBSONIC_ENGINE= NO - Code:
CConfig.cppline 1817
ACTDISK_DOUBLE_SURFACE
Actuator disk double surface
- Type: YES / NO
- Default:
NO - In config_template.cfg:
ACTDISK_DOUBLE_SURFACE= NO - Mentioned in: Actuator Disk With Variable Load
- Used in 2 test case files, for example:
actuatordisk_bem.cfg(YES) - Code:
CConfig.cppline 1819
BEM_PROP_BLADE_ANGLE
Propeller blade angle for actuator disk BEM.
More in config_template.cfg: Propeller blade angle (degrees) at (0.75 * radius)
- Type: real number
- Default:
23.9 - In config_template.cfg:
BEM_PROP_BLADE_ANGLE = 25.0 - Used in 1 test case file, for example:
actuatordisk_bem.cfg(23.9) - Code:
CConfig.cppline 1822
BEM_PROP_FILENAME
Propeller file name for actuator disk BEM.
More in config_template.cfg: Propeller blade element section and aerodynamic data input file name
- Type: string
- Default:
string("prop_geom_alfclcd_data.txt") - In config_template.cfg:
BEM_PROP_FILENAME = prop_geom_alfclcd_data.txt - Used in 1 test case file, for example:
actuatordisk_bem.cfg(prop_geom_alfclcd_data.txt) - Code:
CConfig.cppline 1824
BEM_FREQ
Frequency for updating actuator disk with BEM.
More in config_template.cfg: BEM calculation frequency
- Type: integer
- Default:
40 - In config_template.cfg:
BEM_FREQ = 40 - Used in 1 test case file, for example:
actuatordisk_bem.cfg(40) - Code:
CConfig.cppline 1826
ENGINE_HALF_MODEL
Only half engine is in the computational grid
More in config_template.cfg: Only half engine is in the computational grid (NO, YES)
- Type: YES / NO
- Default:
NO - In config_template.cfg:
ENGINE_HALF_MODEL= NO - Code:
CConfig.cppline 1829
ACTDISK_SU2_DEF
Actuator disk SU2_DEF
- Type: YES / NO
- Default:
NO - Not in config_template.cfg.
- Code:
CConfig.cppline 1831
DISTORTION_RACK
Definition of the distortion rack (radial number of proves / circumferential density (degree)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
DISTORTION_RACK= (0.0, 0.0) - Code:
CConfig.cppline 1834
SUBSONIC_ENGINE_VALUES
Values of the box to impose a subsonic nacellle (mach, Pressure, Temperature)
More in config_template.cfg: Flow variables that define the subsonic region (Mach, Alpha, Beta, Pressure, Temperature)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
SUBSONIC_ENGINE_VALUES= ( 0.4, 0.0, 0.0, 2116.216, 518.67 ) - Code:
CConfig.cppline 1837
SUBSONIC_ENGINE_CYL
Coordinates of the box to impose a subsonic nacellle cylinder (Xmin, Ymin, Zmin, Xmax, Ymax, Zmax, Radius)
More in config_template.cfg: Axis of the cylinder that defines the subsonic region (A_X, A_Y, A_Z, B_X, B_Y, B_Z, Radius)
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
SUBSONIC_ENGINE_CYL= ( 0.0, 0.0, 0.0, 1.0, 0.0 , 0.0, 1.0 ) - Code:
CConfig.cppline 1841
MARKER_ENGINE_EXHAUST
Engine exhaust boundary marker(s) Format: (nacelle exhaust marker, total nozzle temp, total nozzle pressure, … )
More in config_template.cfg: Engine exhaust boundary marker(s) with the following formats (NONE = no marker) Format: (engine exhaust marker, total nozzle temp, total nozzle pressure, … )
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_ENGINE_EXHAUST= ( NONE ) - Used in 1 test case file, for example:
MFR_coupling.cfg(( FAN_OUT, 289.761088684333, 103321.726628227, CORE_OUT, 289.761088684333, 103321.726628227 )) - Code:
CConfig.cppline 1844
MARKER_CLAMPED
Clamped boundary marker(s)
- Type: list of strings
- In config_template.cfg:
MARKER_CLAMPED= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Linear Elasticity, Non-linear Elasticity
- Used in 24 test case files, for example:
configAD_fem.cfg(( Clamped )),configFEA.cfg(( clamped )),configFEA.cfg(( Clamped_Right, Clamped_Left )) - Code:
CConfig.cppline 1846
MARKER_NORMAL_DISPL
Displacement boundary marker(s)
More in config_template.cfg: Displacement boundary marker(s) (NONE = no marker) Format: ( displacement marker, displacement value normal to the surface, … )
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_NORMAL_DISPL= ( NONE ) - Code:
CConfig.cppline 1848
MARKER_PRESSURE
Load boundary marker(s) - uniform pressure in Pa
More in config_template.cfg: Pressure boundary marker(s) (NONE = no marker) Format: ( pressure marker )
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_PRESSURE= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Linear Elasticity, Non-linear Elasticity
- Used in 17 test case files, for example:
configAD_fem.cfg(( LowerBeamS, 0.0, UpperBeamS, 1.00, RightBeamS, 0.0)),configBeam_2d.cfg(( lower, 0 )),config.cfg(( RightBeamS , 0, LowerBeamS, 0, UpperBeamS, 0)) - Code:
CConfig.cppline 1850
MARKER_DAMPER
Load boundary marker(s)
- Type: list of (string, real number) pairs
- In config_template.cfg:
MARKER_DAMPER= ( NONE ) - Code:
CConfig.cppline 1852
MARKER_LOAD
Load boundary marker(s) Format: (inlet marker, load, multiplier, dir_x, dir_y, dir_z, … ), i.e. primitive variables specified.
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_LOAD= ( NONE ) - Mentioned in: Markers and Boundary Conditions, Linear Elasticity
- Used in 12 test case files, for example:
configBeam_2d.cfg(( upper, 1, 1000, 0, -1, 0 )),config.cfg(( load,1,0.1,1,0,0 )),linear_plane_strain_2d.cfg(( x_plus, 1, 1000, 0, -1, 0 )) - Code:
CConfig.cppline 1855
MARKER_DISPLACEMENT
Load boundary marker(s) Format: (inlet marker, load, multiplier, dir_x, dir_y, dir_z, … ), i.e. primitive variables specified.
- Type: special format, see config_template.cfg
- In config_template.cfg:
MARKER_DISPLACEMENT= ( NONE ) - Mentioned in: Markers and Boundary Conditions
- Code:
CConfig.cppline 1858
SINE_LOAD
option to apply the load as a sine
- Type: YES / NO
- Default:
NO - In config_template.cfg:
SINE_LOAD= NO - Mentioned in: Linear Dynamics
- Code:
CConfig.cppline 1860
SINE_LOAD_COEFF
the 1st coeff is the amplitude, the 2nd is the frequency, 3rd is the phase in radians
More in config_template.cfg: the 1st coeff is the amplitude, the 2nd is the frequency, the 3rd is the phase in radians
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
SINE_LOAD_COEFF= (0.0, 0.0, 0.0) - Mentioned in: Linear Dynamics
- Code:
CConfig.cppline 1863
RAMP_AND_RELEASE_LOAD
release the load after applying the ramp
- Type: YES / NO
- Default:
NO - In config_template.cfg:
RAMP_AND_RELEASE_LOAD= NO - Code:
CConfig.cppline 1865
BC_EVAL_FREQ
Evaluation frequency for Engine and Actuator disk markers.
- Type: integer
- Default:
40 - In config_template.cfg:
BC_EVAL_FREQ = 40 - Code:
CConfig.cppline 1868
DAMP_ENGINE_INFLOW
Damping factor for engine inlet condition
More in config_template.cfg: Damping factor for the engine inflow.
- Type: real number
- Default:
0.95 - In config_template.cfg:
DAMP_ENGINE_INFLOW= 0.95 - Used in 1 test case file, for example:
MFR_coupling.cfg(0.01) - Code:
CConfig.cppline 1870
DAMP_ENGINE_EXHAUST
Damping factor for engine exhaust condition
More in config_template.cfg: Damping factor for the engine exhaust.
- Type: real number
- Default:
0.95 - In config_template.cfg:
DAMP_ENGINE_EXHAUST= 0.95 - Code:
CConfig.cppline 1872
ENGINE_INFLOW_TYPE
Inlet boundary type
More in config_template.cfg: Engine Inflow boundary type (FAN_FACE_MACH, FAN_FACE_PRESSURE, FAN_FACE_MDOT)
- Type: one of the values below
- Values:
FAN_FACE_MACH,FAN_FACE_MDOT,FAN_FACE_PRESSURE - Default:
FAN_FACE_MACH - In config_template.cfg:
ENGINE_INFLOW_TYPE= FAN_FACE_MACH - Used in 1 test case file, for example:
MFR_coupling.cfg(FAN_FACE_MDOT) - Code:
CConfig.cppline 1874
ENGINE
Evaluate a problem with engines
- Type: YES / NO
- Default:
NO - In config_template.cfg:
ENGINE= NO - Code:
CConfig.cppline 1876
ENGINE_EXHAUST_TO_INLET
Use exhaust mass flow as inlet mass flow.
More in config_template.cfg: Flag to allow mass-flow rate coupling between all exhaust surfaces and the engine inlet (YES, NO)
- Type: YES / NO
- Default:
NO - In config_template.cfg:
ENGINE_EXHAUST_TO_INLET= NO - Mentioned in: Changes in Version 8
- Used in 1 test case file, for example:
MFR_coupling.cfg(YES) - Code:
CConfig.cppline 1878
BUFFET_K
Sharpness coefficient for the buffet sensor
More in config_template.cfg: Sharpness coefficient for the buffet sensor Heaviside function
- Type: real number
- Default:
10.0 - In config_template.cfg:
BUFFET_K= 10.0 - Code:
CConfig.cppline 1881
BUFFET_LAMBDA
Offset parameter for the buffet sensor
More in config_template.cfg: Offset parameter for the buffet sensor Heaviside function
- Type: real number
- Default:
0.0 - In config_template.cfg:
BUFFET_LAMBDA= 0.0 - Code:
CConfig.cppline 1883
NEWTON_KRYLOV
Use a Newton-Krylov method.
More in config_template.cfg: Use a Newton-Krylov method on the flow equations, see TestCases/rans/oneram6/turb_ONERAM6_nk.cfg For multizone discrete adjoint it will use FGMRES on inner iterations with restart frequency equal to “QUASI_NEWTON_NUM_SAMPLES”.
- Type: YES / NO
- Default:
NO - In config_template.cfg:
NEWTON_KRYLOV= NO - Mentioned in: Setup Guide: Steady RANS for External Aerodynamics
- Used in 9 test case files, for example:
configFlow.cfg(YES),config_sst.cfg(NO) - Code:
CConfig.cppline 1886
NEWTON_KRYLOV_IPARAM
Integer parameters {startup iters, precond iters, initial tolerance relaxation}.
- Type: fixed-size list of integers
- Default: Not extracted; see the code.
- In config_template.cfg:
NEWTON_KRYLOV_IPARAM= (20, 3, 2) - Used in 6 test case files, for example:
inv_ramp.cfg((0, 1, 1)),inv_ramp_msw.cfg((0, 0, 1)),turb_ONERAM6_nk.cfg((200, 0, 1)) - Code:
CConfig.cppline 1888
NEWTON_KRYLOV_DPARAM
Double parameters {startup residual drop, precond tolerance, full tolerance residual drop, findiff step, NK relaxation}.
More in config_template.cfg: Double parameters {startup residual drop, precond tolerance, full tolerance residual drop, findiff step, and MUSCL relaxation for the finite difference products}.
- Type: fixed-size list of real numbers
- Default: Not extracted; see the code.
- In config_template.cfg:
NEWTON_KRYLOV_DPARAM= (-2.0, 0.1, -6.0, 1e-5, 1.0) - Used in 6 test case files, for example:
inv_ramp.cfg((0.0, 1e-20, -2.0, 1e-5, 1.0)),inv_ramp_msw.cfg((0, 1e-20, -2.0, 1e-5, -1.0)),turb_ONERAM6_nk.cfg((0, 0, 0, 1e-5, -1)) - Code:
CConfig.cppline 1890
QUASI_NEWTON_NUM_SAMPLES
Number of samples for quasi-Newton methods.
More in config_template.cfg: Enable (if != 0) quasi-Newton acceleration/stabilization of discrete adjoints
- Type: integer
- Default:
0 - In config_template.cfg:
QUASI_NEWTON_NUM_SAMPLES= 20 - Mentioned in: Setup Guide: Shape Optimization with the Discrete Adjoint
- Used in 6 test case files, for example:
configFlow.cfg(999),turb_naca0012_sst.cfg(30),transonic_stator.cfg(20) - Code:
CConfig.cppline 1893
USE_VECTORIZATION
Whether to use vectorized numerical schemes, less robust against transients.
More in config_template.cfg: Use the vectorized version of the selected numerical method (available for JST family and Roe). SU2 should be compiled for an AVX or AVX512 architecture for best performance. NOTE: Currently vectorization always used for schemes that support it.
- Type: YES / NO
- Default:
NO - In config_template.cfg:
USE_VECTORIZATION= YES - Mentioned in: Setup Guide: Laminar-Turbulent Transition
- Used in 1 test case file, for example:
config.cfg(YES) - Code:
CConfig.cppline 1895