Boundary Markers

Generated from SU2 commit 6b54b78464 on 2026-10-23. Do not edit this page. Edit the comment above the option in Common/src/CConfig.cpp instead.

MARKER_PLOTTING

Marker(s) of the surface in the surface flow solution file

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.

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.

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)

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

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

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.

MARKER_FAR

Far-field boundary marker(s)

More in config_template.cfg: Far-field boundary marker(s) (NONE = no marker)

MARKER_SYM

Symmetry boundary condition

More in config_template.cfg: Symmetry boundary marker(s) (NONE = no marker) Implementation identical to MARKER_EULER.

MARKER_NEARFIELD

Near-Field boundary condition

More in config_template.cfg: Near-Field boundary marker(s) (NONE = no marker)

MARKER_FLUID_INTERFACE

Fluid interface boundary marker(s)

MARKER_DEFORM_MESH

Deformable marker(s) at the interface

More in config_template.cfg: Moving markers which deform the mesh

MARKER_DEFORM_MESH_SYM_PLANE

Symmetry plane for mesh deformation only

MARKER_DEFORM_MESH_INTERNAL

Internal marker for mesh deformation only

MARKER_FLUID_LOAD

Marker(s) in which the flow load is computed/applied

MARKER_ZONE_INTERFACE

ZONE interface boundary marker(s)

MARKER_CHT_INTERFACE

CHT interface boundary marker(s)

CHT_INTERFACE_CONTACT_RESISTANCE

: Thermal contact resistance values for each CHT inerface.

MARKER_INTERNAL

Internal boundary marker(s)

More in config_template.cfg: Internal boundary marker(s) e.g. no boundary condition (NONE = no marker)

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).

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, … )

MARKER_PYTHON_CUSTOM

Python customizable marker(s)

More in config_template.cfg: Marker(s) of the surface where custom thermal BC’s are defined.

PYTHON_CUSTOM_SOURCE

Python custom source

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-, … )

MARKER_SPECIES_STRONG_BC

Markers where a strong BC must be applied.

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)

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)

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.cpp line 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.cpp line 1679

ACTDISK_FILENAME

Input file for a specified actuator disk (w/ extension)

More in config_template.cfg: Actuator disk data input file name

INLET_TYPE

Inlet boundary type

More in config_template.cfg: Inlet boundary type (TOTAL_CONDITIONS, MASS_FLOW)

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.

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.

SPECIFIED_INLET_PROFILE

Read inlet profile from a file (YES, NO) default: NO (from config_template.cfg)

INLET_FILENAME

Input file for a specified inlet profile (w/ extension)

More in config_template.cfg: File specifying inlet profile

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.

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.

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))

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, …)

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)

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.

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)

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

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)

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)

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

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

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)

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

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)

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

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

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)

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

TURBULENT_MIXINGPLANE

Activate mixing plane also for turbulent quantities

More in config_template.cfg: Specify option for turbulent mixing-plane (YES, NO) default NO

RELATIVE_FRAME_SLIDINGPLANE

Activate sliding plane for relative frame

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)

NUM_SPANWISE_SECTIONS

Integer number of spanwise sections to compute 3D turbo BC and Performance for turbomachinery

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.

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)

TURBO_PERF_KIND

types of turbomachynery Performance Calculations.

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

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.

MARKER_SUPERSONIC_OUTLET

Supersonic outlet boundary marker(s)

More in config_template.cfg: Supersonic outlet boundary marker(s) (NONE = no marker)

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), … )

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

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), … )

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), … )

INTEGRATED_HEATFLUX

Prescribe Heatflux in [W] instead of [W/m^2] \default false

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) … )

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.cpp line 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.

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.cpp line 1811

HIGHLITE_AREA

Highlite area

More in config_template.cfg: Highlite area to compute MFR (1 in2 by default)

FAN_POLY_EFF

Fan poly efficiency

More in config_template.cfg: Fan polytropic efficiency (1.0 by default)

SUBSONIC_ENGINE

Engine subsonic intake region

More in config_template.cfg: Initialization with a subsonic flow around the engine.

ACTDISK_DOUBLE_SURFACE

Actuator disk double surface

BEM_PROP_BLADE_ANGLE

Propeller blade angle for actuator disk BEM.

More in config_template.cfg: Propeller blade angle (degrees) at (0.75 * radius)

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.cpp line 1824

BEM_FREQ

Frequency for updating actuator disk with BEM.

More in config_template.cfg: BEM calculation frequency

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)

ACTDISK_SU2_DEF

Actuator disk SU2_DEF

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.cpp line 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.cpp line 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.cpp line 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.cpp line 1844

MARKER_CLAMPED

Clamped boundary marker(s)

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.cpp line 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 )

MARKER_DAMPER

Load boundary marker(s)

  • Type: list of (string, real number) pairs
  • In config_template.cfg: MARKER_DAMPER= ( NONE )
  • Code: CConfig.cpp line 1852

MARKER_LOAD

Load boundary marker(s) Format: (inlet marker, load, multiplier, dir_x, dir_y, dir_z, … ), i.e. primitive variables specified.

MARKER_DISPLACEMENT

Load boundary marker(s) Format: (inlet marker, load, multiplier, dir_x, dir_y, dir_z, … ), i.e. primitive variables specified.

SINE_LOAD

option to apply the load as a sine

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.cpp line 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.cpp line 1865

BC_EVAL_FREQ

Evaluation frequency for Engine and Actuator disk markers.

DAMP_ENGINE_INFLOW

Damping factor for engine inlet condition

More in config_template.cfg: Damping factor for the engine inflow.

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.cpp line 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.cpp line 1874

ENGINE

Evaluate a problem with engines

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)

BUFFET_K

Sharpness coefficient for the buffet sensor

More in config_template.cfg: Sharpness coefficient for the buffet sensor Heaviside function

BUFFET_LAMBDA

Offset parameter for the buffet sensor

More in config_template.cfg: Offset parameter for the buffet sensor Heaviside function

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”.

NEWTON_KRYLOV_IPARAM

Integer parameters {startup iters, precond iters, initial tolerance relaxation}.

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.cpp line 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

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.



Improve this page