Conditions

Conditions are all properties of a problem (except Materials and Boundaries , see below) that can be assigned to an entity, in order to define the basic boundary conditions of a problem. Conditions should be used to define inflow and outflow boundary conditions, and symmetry or far field conditions.

In Tdyn conditions are available through the menu option Data>Conditions .

Remarks:

The complex boundary conditions, like body wall type (i.e. law of the wall) or free surface, can be easily imposed by using the Boundaries options.

If a mesh has already been generated, any change in the condition assignments, requires meshing again to transfer these new conditions to the mesh. If the conditions were changed and a new mesh was not generated, the user will be warned, when the data for the analysis is being written.

Conditions available in module RANSOL

The following boundary conditions, are available in the RANSOL module of Tdyn.

Fix Pressure

This condition is assigned to geometrical/mesh entities or layers and is used to fix the pressure at the given value.

Remarks :

When the selected flow model is PrCompressible (compressible based on pressure) both pressure and density are prescribed when this condition is applied.

Fields :

Value : Value (real) of the pressure.

Remarks :

For most of the problems it is strongly recommended to fix the pressure in at least one point of the domain.

When the pressure is not specified in the analysis either directly or indirectly, no reference for the pressure exists, and the resulting distribution can only be used with relative values.

The pressure can be specified at a far field boundary (i.e. at the outflow boundary of the domain, when the boundary is far enough from the region of interest).

The pressure can also be specified at the inlet boundary. If the conditions at inlet are not well known, it is effective to move the boundary as far from the region of interest as possible.

When the selected flow model is PrCompressible (compressible based on pressure) both pressure and density are prescribed when this condition is applied.

Units of the pressure boundaries may be defined in Data > Units Data | General .

Pressure Field

This condition is assigned to geometrical/mesh entities and is used to fix the pressure at the value given by the Pressure Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15.

Remarks:

When the selected flow model is PrCompressible (compressible based on pressure) both pressure and density are prescribed when this condition is applied.

Fields :

Fix Initial : The pressure will be fixed to the initial value (evaluated in t=0) of the function inserted in the Pressure Field entry of the Tdyn Initial and Conditional Data window. Pressure Field entry is evaluated at the initial step (t=0) and pressure is fixed to the resulting value for the rest of the execution.

Fix Field : The pressure will be fixed to the value (for every time step) of the function inserted in the Initial Pressure field of the Tdyn Initial and Conditional Data window. Pressure Field entry is evaluated every step and pressure is fixed to the resulting value.

Remarks :

In most of the problems, it is recommended to fix the pressure in at least one point of the domain. When the pressure is not specified in the analysis either directly or indirectly, no reference for the pressure exists, and the resulting distribution can only be used with relative values.

When Pressure Field condition is assigned, Pressure Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Pressure Field value is common for every Pressure Field condition and can only be modified in the Tdyn Initial and Conditional Data window.

Sometimes the pressure is specified at a far field boundary (i.e. at the outflow boundary of the domain, when the boundary is far enough from the region of interest).

Sometimes the pressure is specified also at the inlet boundary. If the conditions at inlet are not well known, it is effective to move the boundary as far from the region of interest as possible.

This condition allows a definition of transient boundary conditions for the pressure. The analytical functions defining transient boundary conditions will be specified in the corresponding function inserted in the Pressure Field entry of the Tdyn Initial and Conditional Data window.

If the boundary conditions for the pressure are steady, this condition can be substituted by the Fix Pressure condition. The only difference between these two options in this case is, that when using Pressure Field , the value of the fixed pressure can be changed automatically in every entity by updating the corresponding function inserted in the Pressure Field entry of the Tdyn Initial and Conditional Data window.

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

Units of the pressure boundaries may be defined in Data > Units Data | General .

Conditional Pressure

This condition is assigned to geometrical/mesh entities and layers and is used to specify the pressure at the value given by the Pressure Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15 only if the Pressure FuncCond data field is greater than 0.

If the evaluation of the Pressure FuncCond field results in a value less than 0, the boundary conditions will not be applied. If the value is 0, the boundary condition will be applied only if it was applied in the previous time step.

Remarks :

When the selected flow model is PrCompressible (compressible based on pressure) both pressure and density are prescribed when this condition is applied.

When ConditionalPressure condition is assigned, Pressure Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

Pressure FuncCond and Pressure Field entries are common for every Conditional Pressure condition and can only be modified in the Tdyn Initial and Conditional Data.

In most of the problems, it is recommended to fix the pressure in at least one point of the domain. When the pressure is not specified in the analysis either directly or indirectly, no reference for the pressure exists, and the resulting distribution can only be used with relative values.

Sometimes the pressure is specified at a far field boundary (i.e. at the outflow boundary of the domain, when the boundary is far enough from the region of interest).

Sometimes the pressure is specified also at the inlet boundary. If the conditions at inlet are not well known, it is effective to move the boundary as far from the region of interest as possible.

Units of the pressure boundaries may be defined in Data > Units Data | General .

Fix Velocity

This condition is assigned to geometrical/mesh entities or layers and is used to fix the velocity at the given value.

Fields :

X Component : Value (real) of the OX component of the velocity.

Fix X : Only if marked the OX component of the velocity will be fixed.

Y Component : Value (real) of the OY component of the velocity.

Fix Y : Only if marked the OY component of the velocity will be fixed.

Z Component : Value (real) of the OZ component of the velocity.

Fix Z : Only if marked the OZ component of the velocity will be fixed.

Remarks :

The velocity has to be prescribed at the inlet boundary. If the conditions at inlet are not well known, it is effective to move the boundary as far from the region of interest as possible.

Units of the velocity boundaries may be defined in Data > Units Data | GENERAL .

Fix Velocity Component

This condition is assigned to geometrical/mesh and is used to specify the value of a component of the velocity vector.

Fields :

Local Axes : Orientation of the Cartesian axes used to define the direction of the component of the velocity vector. These can be local axes of the geometry (-Automatic- option) or any user defined system.

Type : Axis of the Local Axes definition. The component of the velocity vector, parallel to this axis, will be fixed to the given value. The normal velocity component to a line or a surface can be fixed by selecting Y_Axis or Z_Axis. To see the defined Local Axes , press the button Draw.

Value : Value of the component of the velocity in the direction given by Type axis.

Remarks :

This option is used to prescribe slipping boundary conditions on a velocity field. Since the normal vector is sometimes undefined in some complex areas (i.e. dihedral angles) of the geometry, in some cases it is better to use the Body Boundary options instead.

Units of the velocity boundaries may be defined in Data > Units Data | GENERAL .

Fix Velocity Direction

This condition is assigned to geometrical/mesh entities and may be used to define the direction of the velocity, according to the orientation of the skew system.

Fields :

Local Axes : Orientation of the Cartesian axes used to define the direction of the component of the velocity vector. These can be local axes of the geometry (-Automatic- option) or any user defined system.

Type : Axis of the Local Axes definition. The component of the velocity vector, parallel to this axis, will be fixed to the given value. The normal velocity component to a line or a surface can be fixed by selecting Y_Axis or Z_Axis. To see the defined Local Axes , press the button Draw.

Remarks :

Usually, the direction of the velocity has to be prescribed in someedges or areas with strong geometrical changes of the geometry.

The direction of the velocity can be automatically imposed by using the Body Boundary options (see Fix Angle option, Figure 13).

Remove Velocity Conditions

This condition is assigned to geometrical/mesh entities and layers and makes the program to ignore any specification on the velocity field.

Fields :

Free Velocity : The velocity will be removed only if this field is marked.

Remarks :

This option allows the solver to accomplish the Kutta-Jukowsky condition. In these cases the Remove Velocity condition will be assigned to the extreme point of the tail of a profile. It is also possible to automatically correct velocity impositions in these areas by using the Body Boundary options (see Sharp Angle option, Figure 12).

Velocity Field

This condition is assigned to geometrical/mesh entities and layers and is used to specify the velocity at the value given by the corresponding functions of the Tdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15.

Remarks :

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

Fields :

Fix Initial X : The OX component of the velocity will be fixed to the initial value (evaluated in t=0) of the corresponding function of the Tdyn Initial and Conditional Data window (Velocity X Field entry) only if the field is marked. Velocity X Field is evaluated at the initial step (t=0) and velocity component is fixed to the resulting value for the rest of the execution.

Fix Initial Y : The OY component of the velocity will be fixed to the initial value (evaluated in t=0) of the corresponding function of the Tdyn Initial and Conditional Data window (Velocity Y Field entry) only if the field is marked. Velocity Y Field is evaluated at the initial step (t=0) and velocity component is fixed to the resulting value for the rest of the execution.

Fix Initial Z : The OZ component of the velocity will be fixed to the initial value (evaluated in t=0) of the corresponding function of the Tdyn Initial and Conditional Data window (Velocity Z Field entry) only if the field is marked. Velocity Z Field is evaluated at the initial step (t=0) and velocity component is fixed to the resulting value for the rest of the execution.

Fix Field X : The OX component of the velocity will be fixed to the value (for every time step) of the corresponding function of Tdyn Initial and Conditional Data window (Velocity X Field entry) only if the field is marked. Velocity X Field is evaluated every step and the corresponding velocity component is fixed to the resulting value.

Fix Field Y : The OY component of the velocity will be fixed to the value (for every time step) of the corresponding function of the Tdyn Initial and Conditional Data window (Velocity Y Field entry) only if the field is marked. Velocity Y Field is evaluated every step and the corresponding velocity component is fixed to the resulting value.

Fix Field Z : The OZ component of the velocity will be fixed to the value (for every time step) of the corresponding function of the Tdyn Initial and Conditional Data window (Velocity Z Field entry) only if the field is marked. Velocity Z Field is evaluated every step and the corresponding velocity component is fixed to the resulting value.

Remarks :

The velocity has to be prescribed at every inlet boundary. If the conditions at inlet are not well known, it is effective to move the boundary as far from the region of interest as possible.

When Velocity Field condition is assigned, Velocity X/Y/Z Field entries are used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

This condition allows definitions of transient boundary conditions for the velocity. The analytical functions defining transient boundary conditions will be specified in the corresponding Tdyn Initial and Conditional Data window.

If the boundary conditions for the velocity are steady, this condition can be substituted by the Fix Velocity condition. The only difference between these two options in this case is, that when using the Velocity Field, the value of the fixed velocity can be changed automatically in every entity by updating the corresponding Tdyn Initial and Conditional Data window.

Units of the velocity boundaries may be defined in Data > Units Data | GENERAL .

Conditional Velocity

This condition is assigned to geometrical/mesh entities and layers and is used to specify the velocity at the value given by the corresponding Velocity X/Y/Z Field entries of the Tdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15 only if the given conditional data field is greater than 0 (see Velocity X/Y/Z FuncCond fields in Figure 15).

If the evaluation of the corresponding Velocity X/Y/Z FuncCond field results in a value less than 0, the boundary conditions will not be applied. If the value is 0, the boundary condition will be applied only if it was applied in the previous time step.

Remarks :

When Conditional Velocity condition is assigned, Velocity X/Y/Z Field entries are used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

Velocity X/Y/Z FuncCond entries are common for every Conditional Velocity condition and can only be modified in the Tdyn Initial and Conditional Data.

The velocity has to be prescribed at every inlet boundary. If the conditions at inlet are not well known, it is effective to move the boundary as far from the region of interest as possible.

Units of the velocity boundaries may be defined in Data > Units Data | GENERAL .

Fix Turbulence

This condition is assigned to geometrical/mesh entities and layers and is used to fix the turbulence variables for those turbulence models based on the Reynolds extended analogy, at the initial (evaluated for t=0) value given by the corresponding functions (EddyKEner Field and EddyLength Field ) of the Tdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15.

Fields :

Fix : The turbulence will be fixed to the initial value (evaluated in t=0) of the corresponding function of the Tdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15 only if this field is marked. EddyKEner Field and EddyLength Field give the value of the eddy energy and turbulence length scale or mixing length (see Turbulence modelling section), respectively.

Remarks :

The turbulence variables have to be prescribed at every inlet boundary. In those entities where all components of the velocity have been prescribed, Tdyn automatically fixes all turbulence variables at the initial (evaluated for t=0) value given in the EddyKEner Field and EddyLength Field entries of theTdyn Initial and Conditional Data window (Data>Initial Data ) shown in Figure 15. Therefore, assignment of this condition should not be necessary in most of the cases.

Fix Turbulence condition will only be useful for those turbulence models based on Reynolds extended analogy (see Turbulence Modelling section for further information).

Conditions available in module HEATRANS

The following boundary conditions are available in the HEATRANS module of Tdyn.

Fix Temperature

This condition is assigned to geometrical/mesh entities and layers and is used to fix the temperature in a geometrical entity or layer at the given value.

Fields :

Value : Value of the temperature.

Remarks :

Units of the temperature boundaries may be defined in Data>Units Data | General .

Temperature Field

This condition is assigned to geometrical/mesh entities and layers and is used to fix the temperature at the value given by the function inserted in the Temperature Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ).

Fields :

Fix Initial : The temperature will be fixed to the initial value (evaluated in t=0) of the function inserted in the Temperature Field entry of the Tdyn Initial and Conditional Data window only if the field is marked.

Temperature Field is evaluated initial step (t=0) and temperature is fixed to the resulting value for the rest of the execution.

Fix Field : The temperature will be fixed to the value (for every time step) of the function inserted in the Temperature Field entry of the Tdyn Initial and Conditional Data window. Temperature Field entry is evaluated every step and temperature is fixed to the resulting value.

Remarks :

This condition allows definitions of transient boundary conditions for temperature. The analytical functions defining transient boundary conditions will be specified in the Temperature Field entry of the Tdyn Initial and Conditional Data window.

If the boundary conditions for the temperature are steady, this condition can be substituted by the Fix Temperature condition. The only difference between these two options in this case is, that when using the Temperature Field, the value of the fixed temperature can be changed automatically in every entity by updating the Temperature Field entry of the Tdyn Initial and Conditional Data window.

When Temperature Field condition is assigned, Temperature Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units of the temperature boundaries may be defined in Data > Units Data | General .

Conditional Temperature

This condition is assigned to geometrical/mesh entities and layers and is used to specify the temperature at the value given by the Temperature Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ) only if the TemperatureFuncCond data field is greater than 0.

If the evaluation of the Temperature FuncCond field results in a value less than 0, the boundary conditions will not be applied. If the value is 0, the boundary condition will be applied only if it was applied in the previous time step.

Remarks :

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

Temperature FuncCond and Temperature Field entries are common for every Conditional Temperature condition and can only be modified in the Tdyn Initial and Conditional Data.

When Conditional Temperature condition is assigned, Temperature Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units of the temperature boundaries may be defined in Data>Units Data | General .

Conditions available in module ADVECT

Fix Concentration

This condition is assigned to geometrical/mesh entities and layers and is used to fix the value of the concentration of species (substances) at the given value.

Fields :

Species Name : Name of the species (see material Fluid/Solid description in sectionMaterials) which concentration is to be fixed.

Value : Value of the concentration of the species.

Remarks:

The value of the concentration of every species should be prescribed at every inlet boundary.

Units of the concentration boundaries may be defined in Data > Modules Data | ADVECT | Reference Units .

Concentration Field

This condition is assigned to geometrical/mesh entities and is used to fix the concentration of species at the value given by the Concentration Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ).

Fields :

Species Name : Name of the species (see material Fluid/Solid description in sectionMaterials) which concentration is to be fixed.

Fields :

Fix Initial : The concentration of the species will be fixed to the initial value (evaluated in t=0) of the function inserted in the Concentration Field entry of the Tdyn Initial and Conditional Data window. Concentration Field entry is evaluated at the initial step (t=0) and concentration is fixed to the resulting value for the rest of the execution.

Fix Field : The concentration will be fixed to the value (for every time step) of the function inserted in the Concentration Field entry of the Tdyn Initial and Conditional Data window. Concentration Field entry is evaluated every step and concentration is fixed to the resulting value.

Remarks:

The value of the concentration of every species should be prescribed at every inlet boundary.

This condition allows definitions of transient boundary conditions for concentration. The analytical functions defining transient boundary conditions will be specified in the Concentration Field entry of the Tdyn Initial and Conditional Data window.

If the boundary conditions for the concentration are steady, this condition can be substituted by the Fix Concentration condition. The only difference between these two options in this case is, that when using the ConcentrationField, the value of the fixed concentration can be changed automatically in every entity by updating the Concentration Field entry of the Tdyn Initial and Conditional Data window.

When Concentration Field condition is assignedConcentration Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units of the concentration boundaries may be defined in Data > Modules Data | ADVECT | Reference Units .

Conditional Concentration

This condition is assigned to geometrical/mesh entities and layers and is used to specify the concentration of species at the value given by the Concentration Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ) only if the Species FuncCond data field is greater than 0.

If the evaluation of the Species FuncCond field results in a value less than 0, the boundary conditions will not be applied. If the value is 0, the boundary condition will be applied only if it was applied in the previous time step.

Remarks :

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

Species FuncCond and Concentration Field entries are common for every Conditional Concentration condition and can only be modified in the Tdyn Initial and Conditional Data.

When Conditional Concentration condition is assigned,Concentration Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units of the concentration boundaries may be defined in Data > Modules Data | ADVECT | Reference Units .

Conditions available in module URSOLVER

Fix Variable

This condition is assigned to geometrical/mesh entities and layers and is used to fix the value of the variable at the given value.

Fields :

Phis Name : Name of the variable (see material Fluid/Solid description in sectionMaterials) which value is to be fixed.

Value : Value of the variable.

Remarks:

The value of the variable should be prescribed at every inlet boundary.

Units of the variable boundaries may be defined in Data>Modules Data> ADVECT>Reference Units .

Variable Field

This condition is assigned to geometrical/mesh entities and is used to fix the value of a variable at the value given by the Variable Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ).

Fields :

Phis Name : Name of the variable (see material Fluid/Solid description in section Materials) which value is to be fixed.

Fix Initial : The variable will be fixed to the initial value (evaluated in t=0) of the function inserted in the Variable Field entry of the Tdyn Initial and Conditional Data window. Variable Field entry is evaluated at the initial step (t=0) and variable is fixed to the resulting value for the rest of the execution.

Fix Field : The variable will be fixed to the value (for every time step) of the function inserted in the Variable Field entry of the Tdyn Initial and Conditional Data window. Variable Field entry is evaluated every step and Variable is fixed to the resulting value.

Remarks:

The value of the variable should be prescribed at every inlet boundary.

This condition allows definitions of transient boundary conditions for variables. The analytical functions defining transient boundary conditions will be specified in the Variable Field entry of the Tdyn Initial and Conditional Data window.

If the boundary conditions for the variable are steady, this condition can be substituted by the Fix Variable condition. The only difference between these two options in this case is, that when using the Variable Field condition, the value of the fixed variable can be easily updated in every entity by changing the Variable Field entry of the Tdyn Initial and Conditional Data window.

When Variable Field condition is assigned VariableField entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units of the variable boundaries may be defined in Data>Modules Data> URSOLVER | Reference Units .

Conditional Variable

This condition is assigned to geometrical/mesh entities and layers and is used to specify the value of a variable at the value given by the Variable Field entry of the Tdyn Initial and Conditional Data window (Data > Initial Data ) only if the evaluation of the function defined in Variable FuncCond field is greater than 0.

If the evaluation of the Variable FuncCond field results in a value less than 0, the boundary conditions will not be applied. If the value is 0, the boundary condition will be applied only if it was applied in the previous time step.

Remarks :

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section). Variable FuncCond and Variable Field entries are common for every Conditional Variable condition and can only be modified in the Tdyn Initial and Conditional Data.

When Conditional Variable condition is assignedVariable Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units of the Variable boundary conditions may be defined in Data>Modules Data> URSOLVER>Reference Units .

Conditions available in module NAVAL

Fix Beta

This condition is assigned to geometrical/mesh entities and layers. It is used to fix the value of the wave elevation at its initial value. The initial value is the difference between the OZ coordinate of the point and the reference height of the free surface (see Data > Problem Data > OTHER > Give pressure origin ).

Fields :

Fix : The wave elevation will be fixed to its initial value only if the field is marked.

Remarks :

This option is effective in the stern of some geometries to keep the stability of the free surface. In most of the cases it can be automatically imposed by using the Body Boundary options (see Stern C Angle option and Stern flow modelling in transpiration problem section).

Conditions available in module ALEMESH

Fix Mesh Deformation

This condition is assigned to geometrical/mesh entities and layers. It is used to fix the value of the mesh deformation to cero or to the value given in the Fluid/Solid Deformation Increment field (see Data > Modules Data | ALEMESH).

Fields :

Type : Type of mesh deformation. If Fix Field is selected, imposed mesh deformation will be defined by Fluid/Solid Deformation Increment field (see Data > Modules Data

| ALEMESH ). If Fix Null is selected, mesh deformation is imposed to be cero. Finally, if No Fix is selected, any other imposition on the mesh deformation field is ignored.

Remarks :

Mesh deformation type may be defined in the Tdyn Modules Data window (see Data > Modules Data | ALEMESH | Fluid/Solid Mesh Deformation ).

Conditions available in module RAMSOLID

A description of every available option of this module can be found in the RamSeries user and reference manual.

Conditions available in module ODDLS

Fix ODDLS

This condition is assigned to geometrical/mesh entities and layers and is used to fix the value of the level set function.

Fields :

Value : Value of the level set function. Positive values identifies the primary phase.

Remarks:

The value of the level set function should be prescribed at every inlet boundary.

ODDLS Field

This condition is assigned to geometrical/mesh entities and is used to fix the value of the level set function at the value given by the OddLevelSet Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ).

Fields :

Fix Initial : The level set function will be fixed to the initial value (evaluated in t=0) of the function inserted in the OddLevelSet Field entry of the Tdyn Initial and Conditional Data window. OddLevelSet Field entry is evaluated at the initial step (t=0) and level set function is fixed to the resulting value for the rest of the execution.

Fix Field : The level set function will be fixed to the value (evaluated every time step) of the function inserted in the OddLevelSet Field entry of the Tdyn Initial and Conditional Data window. OddLevelSet Field entry is evaluated every time step and level set function is fixed to the resulting value.

Remarks:

The value of the level set function should be prescribed at every inlet boundary.

This condition allows definitions of transient boundary conditions for level set function. The analytical functions defining transient boundary conditions will be specified in the OddLevelSet Field entry of the Tdyn Initial and Conditional Data window.

If the boundary conditions for the variable are steady, this condition can be substituted by the Fix ODDLS condition. The only difference between these two options in this case is, that when using the ODDLS Field the value of the fixed variable can be easily updated in every entity by changing the OddLevelSet Field of the Tdyn Initial and Conditional Data window.

When ODDLS Field condition is assigned,OddLevelSet Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units for level set function (signed distance to the free surface) are the internal length units. Internal length units can be defined in Data > Units data | IN/OUT .

Conditional ODDLS

This condition is assigned to geometrical/mesh entities and layers and is used to specify the value of the level set function at the value given by the OddLevelSet Field entry of the Tdyn Initial and Conditional Data window (Data>Initial Data ) only if the OddLevelSet FuncCond data field is greater than 0.

If the evaluation of the OddLevelSet FuncCond field results in a value less than 0, the boundary conditions will not be applied. If the value is 0, the boundary condition will be applied only if it was applied in the previous time step.

Remarks :

Entries of the Tdyn Initial and Conditional Data window may be defined by functions (see Function Syntax section).

OddLevelSet FuncCond and OddLevelSet Field entries are common for every Conditional ODDLS condition and can only be modified in the Tdyn Initial and Conditional Data.

When Conditional ODDLS condition is assignedOddLevelSet Field entry is used both for defining initial values (t = 0) when starting calculation and for evaluating the assigned condition the rest of time steps.

Units for level set function (signed distance to the free surface) are the internal length units. Internal length units can be defined in Data > Units data | IN/OUT .