This subsection is used to specify the expert settings that are available. Expert settings provide you with additional advanced controls for many of the settings available in the Outline and Properties views under the Setup branch.
• General Expert Settings
– DumpInterfaceMeshes (string)
The only valid value for this setting is CFDPost. When this expert setting is used, files named
<Name of Data Transfer>source.csv or <Name of Data Transfer>target.csv are generated during the mapping process. These files report values of 0 and 1 for unmapped and mapped nodes, respectively. These files are appropriate for import into CFD-Post as user defined surfaces for the visualization of mapping data.
– MeshSyncOption (integer)
Value is 0, 1, 2, or 3 (default: 0). This setting is only relevant for coupled analyses with a participant that consumes geometric data (for example, the Fluids solver in a Fluid Structure Interaction ana-lysis, which receives displacement data). This setting can be used when the solution of the participant consuming geometrical data is either sequenced identically as, or sequenced before, the solution of the participant that provides the geometric data. Available options are:
→ 0 (default): If the maximum number of coupling iterations per coupling step is 1, then the solution sequence is changed so that the participant that consumes geometrical data is solved last. If the maximum number of coupling iterations per coupling step is greater than 1, then one additional coupling iteration is performed at the end of the coupling step and only the participant that consumes geometrical data is re-solved.
→ 1: Regardless of the maximum number of coupling iterations per coupling step, the solution sequence is changed so that within each coupling iteration, the participant that consumes geo-metrical data is solved last.
→ 2: Regardless of the maximum number of coupling iterations per coupling step, one additional coupling iteration is performed at the end of the coupling step and only the participant that consumes geometrical data is re-solved.
→ 3: No setup modifications are applied, and the solution proceeds with the specified participant sequencing.
– GeneralAnalysis_IncrDisp_InitIterationValue_Zero (integer)
Value is 0 or 1 (default: 1). This setting is only relevant in a general coupled analysis, when displace-ment is transferred, and when the solver receiving the displacedisplace-ment (such as Fluent) solves before or simultaneously to the solver sending the displacement data (such as Mechanical).
→ 1: During the first coupling iteration of each coupling step the displacement transferred to the target is 0 [m] (irrespective of the value provided by the source). This override of the transfer value is to avoid possible double displacement, which could create folding of the mesh.
→ 0: The value for displacement provided by the source is transferred with no interference by this expert setting (this value transferred may be modified by other settings such as ramping).
• Participant Variable Initial Value Settings
The following expert settings are useful for overriding the default initial values of variables of a given type for all participants. These initial values are currently used in the ramping as well as the under-relaxation of data transfers. Note that for the ramping algorithm, the reference target-side value for displacement is always 0.0 [m]. The expert settings below will have no effect on the value used in this case.
– Participant_Variable_InitValue_IncrDisp_X (real) Participant_Variable_InitValue_IncrDisp_Y (real) Participant_Variable_InitValue_IncrDisp_Z (real)
Replace initial value for Cartesian components of all variables of type "Incremental Displacement"
for all coupling participants. Default is 0.0 [m].
– Participant_Variable_InitValue_Force_X (real) Participant_Variable_InitValue_Force_Y (real) Participant_Variable_InitValue_Force_Z (real)
Replace initial value for Cartesian components of all variables of type "Force" for all coupling parti-cipants. Default is 0.0 [N].
– Participant_Variable_InitValue_Temperature (real)
Replace initial value for all variables of type "Temperature" for all coupling participants (variables include temperature and near wall temperature). Default is 295.15 [K].
– Participant_Variable_InitValue_HeatRate (real)
Replace initial value for all variables of type "Heat Rate" for all coupling participants. Default is 0.0 [W].
– Participant_Variable_InitValue_HeatTransferCoef (real)
Replace initial value for all variables of type "Heat Transfer Coefficient" for all coupling participants.
Default is 0.0 [W m^-2 K^-1].
• Data Transfer Control Settings
The following expert settings are useful for controlling the behavior of data transfers.
– DataTransfer_ScaleFactor_Force (double)
Scale, by the factor specified, source values for all data transfers of Force variables. Default value is 1.0.
– DataTransfer_ScaleFactor_HeatRate (double)
Settings for Completing a System Coupling Setup
Scale, by the factor specified, source values for all data transfers of Heat Rate variables. Default value is 1.0.
– DataTransfer_ScaleFactor_HeatTransferCoef (double)
Scale, by the factor specified, source values for all data transfers of Heat Transfer Coefficient variables.
Default value is 1.0.
– DataTransfer_ScaleFactor_IncrDisp (double)
Scale, by the factor specified, source values for all data transfers of Incremental Displacement variables. Default value is 1.0.
– DataTransfer_ScaleFactor_Temperature (double)
Scale, by the factor specified, source values for all data transfers of Temperature variables. Default value is 1.0.
• SC Log Output Control Settings
The following expert settings are useful for controlling the output of various supplemental diagnostics to the SC log file:
– DTDiagShowRMSChange (string)
Activates reporting of RMS change in data transfers if set to true. Default is ‘False’.
When RMS change is the type of data checked against the convergence target (this is the default), this expert setting does nothing.
– DTDiagShowMaxChange (string)
Activates reporting of Max change in data transfers if set to true. Default is ‘False’.
If Max change is the type of data checked against the convergence target, this expert setting does nothing. Note that the type of data checked (RMS change or Max change) can only be changed through the System Coupling Input File.
– DTDiagShowMinValue (string)
Activates reporting of minimum nodal value in data transfers if set to true. Default is ‘False’.
– DTDiagShowMaxValue (string)
Activates reporting of maximum nodal value in data transfers if set to true. Default is ‘False’.
– DTDiagShowAvgValue (string)
Activates reporting of average nodal value in data transfers if set to true. Default is ‘False’.
– DTDiagShowSum (string)
Activates reporting of sum of nodal values in data transfers if set to true. Default is ‘False’.
– DTDiagShowAll (string)
Activates reporting of all diagnostics of nodal values in data transfers if set to true. Default is ‘False’.
• Expert Settings Related to Mapping
The coupling service uses a Profile Preserving mapping (ProfMap) for non-conservative quantities (for example, displacement) data transfers, and a Conservative mapping (ConsMap) for conservative quantities (for example, forces).
– ProfMapBucketScale (integer)
Value (ranging from 0 to 100, default: 50) that represents the number of discrete search ‘buckets’, as a percentage of the number of nodes, to use during mapping. The objective is to generate
‘buckets’ that will contain roughly equal numbers of nodes. This setting will affect the speed of the mapping, but it should not affect the outcome.
– ProfMapBucketTol (double)
Value (ranging from 0 to 1, default: 1e-4) that is used to create a bounding region around each target node. The bounding region is used to increase the number of buckets that will be included in the Bucket Surface Algorithm's search, which in some cases will improve the number of mapped nodes.
– ProfMapEdgeTol (double)
Value (ranging from 0 to 1, default: 0.05 in natural coordinate space) that specifies the tolerance within which a target node may be found in a source element. See the discussion on Bucket Sur-face (p. 48) mapping algorithm in the section Mapping Algorithms (p. 46) for more information regarding this tolerance setting.
– ProfMapTolOption (integer)
Value is either 0 or 1 (default: 0), where 0 indicates that the specified tolerance is relative to the maximum Cartesian extent of the region being mapped, and 1 indicates that the specified tolerance is absolute (using the same units as the mesh coordinates).
– ProfMapTol (double)
Value (ranging from 0 to 1, default: 1e-6) that specifies the tolerance for the 'gap' distance between a target node and the source element that it is mapped to.
– ProfMapEnforceTol (integer)
Value is either 0 or 1 (default: 0), where 0 indicates that the distance between a target node and the source element that it is mapped to (also known as the ‘gap’ distance) is not checked against the tolerance specified with the expert setting ProfMapTol. Target nodes with final ‘gap’ distances larger than the specified tolerance will be reported as mapped in the SCL file. These nodes are mapped to the source nodes like all of the other mapped nodes and given a value accordingly.
A setting of 1 (which means on) indicates that such a check is performed. Target nodes with final
‘gap’ distances larger than the specified tolerance will be reported as unmapped in the SCL file.
These nodes are mapped to the source nodes like all of the other mapped nodes and given a value accordingly.
– ConsMapPixelRes (integer)
Settings for Completing a System Coupling Setup
Value, (ranging from 10 to 256, default: 100), that indicates the number of pixels to use when forming the surfaces of intersection for each pair of source and target mesh element faces on the interface. Larger values are needed if interface mesh lines are very nearly coincident. Any value entered that is less than 10 or greater than 256 will be reset to 100 automatically.
– ConsMapTol (double)
Value, (ranging from 0.1 and 1, default: 0.1), that specifies the tolerance, in the element-face-normal direction, to use when determining whether the source and target meshes map to one another.
This tolerance is normalized by the local element size. Any value entered that is less than 0.1 or greater than 1 will be reset to 0.1 automatically.