CHAMBER

(required) define the chamber index for the geometry entities

In MESHFREE, a simulation chamber generally means a phase that takes part in the simulation. In the alias section, the CHAMBER index selects for which KindOfProblem the boundary has an influence and provides thus a link between the solver choice in KOP and the boundary conditions BC in the alias definition. Example 1: In a one-phase example KOP is defined for CHAMBER 1

KOP(1) = LIQUID LAGRANGE IMPLICIT v-- TURBULENCE:k-epsilon ... begin_alias{} "car" = " BC$...$ ACTIVE$...$ IDENT%...% MAT$...$ TOUCH%...% MOVE$...$ CHAMBER1 " end_alias

and in the alias section the flag CHAMBER1 links to KOP(1) for the boundary element "car". If the same boundary needs to be visible to several chambers, they need to be defined once for each chamber, possibly with different settings. Example 2: in this two-phase example, KOP selects solvers for both simulation chambers 1 and 2.

KOP(1) = LIQUID IMPLICIT LAGRANGE vp- T:NONE # chamber 1: air phase KOP(2) = LIQUID IMPLICIT LAGRANGE vp- T:NONE # chamber 2: water phase ... begin_alias{} "wall" = " BC$BC_wall_air$ ACTIVE$init_always$ IDENT%BND_slip% MAT$AIR$ TOUCH%TOUCH_always% MOVE$NO_MOVE$ CHAMBER1 " "wall" = " BC$BC_wall_water$ ACTIVE$noinit_always$ IDENT%BND_wall% MAT$WATER$ TOUCH%TOUCH_liquid% MOVE$NO_MOVE$ CHAMBER2 " end_alias

The boundary elements with the alias "wall" are used in both chambers as there is one line for CHAMBER1 and one line for CHAMBER2. In most cases it makes sense that both chambers share the same MOVE statement as the movement of the boundary elements will be identical. Everything else might be set different. Of course, it depends on the use case if the geometry should be visible for both chambers. A further example with different geometries for both phases can be found here. The chamber information can be visualized on the pointcloud with the index %ind_cham% :

SAVE_ITEM = (%SAVE_scalar%, [Y%ind_cham%], "Chamber")