IDENT

In the alias section, the IDENT identifier defines how boundary elements are treated during point cloud organization and in distance computation. It is used in AliasForGeometryItems statements. Example: Default:

• IDENT%IDENT_wall% for all boundary elements EXCEPT BND_plane (if no identifier provided)
• IDENT%IDENT_free% for boundary elements of type BND_plane (if no identifier provided)

Note:

• The IDENT identifier DOES NOT describe the type of physical boundary condition. Physical boundary conditions are flagged by BC (see also %ind_BC%) and defined by BC_v, BC_p etc (see BoundaryConditions).
• A definition depending on time or boundary element quantities is possible with IDENT statements.
• The type of boundary associated to a MESHFREE point is found in %ind_kob% and can be visualized by
  SAVE_ITEM = (%SAVE_scalar%, [Y%ind_kob%], "IDENT")
• For backwards compatibility, %IDENT_...% keywords hold the same value as their %BND_...% counterparts, and using IDENT%BND_wall%, IDENT%BND_inflow%, etc. will still work.
• %IDENT_none% is the value of %ind_kob% of inner points in LIQUID and freely flying, non boundary points in DROPLETPHASE.
• A list of all possible IDENT identifiers is found below.

Identifiers for boundary elements participating in the simulation

For regular geometries use

• IDENT%IDENT_free%
• IDENT%IDENT_inflow%
• IDENT%IDENT_outflow%
• IDENT%IDENT_slip%
• IDENT%IDENT_wall%
• IDENT%IDENT_wall_NoLayerThickness%

Note: IDENT%IDENT_free% is used in initial filling to define the initial free surface for LIQUID. Whereas, %IDENT_ThinFilm% is used within DROPLETPHASE when in the initial filling phase a wall layer for LiquidLayer should be created.

Identifiers for postprocessing

For invisible geometries in INTEGRATION statements use

• IDENT%IDENT_void%
• IDENT%IDENT_BlindAndEmpty%

IDENT%IDENT_BlindAndEmpty% is perfect for flux integrations, e.g. %INTEGRATION_FLUX%, and monitor point creation with %MONITORPOINTS_CREATION_PenetrationOfBlindAndEmptyBoundary%.

Interaction with TOUCH

This part of the documentation is currently under construction.