mus_bc_header_module Module

name of this boundary

elements list of this boundary in different refinement level size: minLevel -> maxLevel

Collect corner BC i.e elements which are interesected by multiple boundaries only for moments based BC

list corner boundary elements

number of local (this process) boundary elements per level including ghostFromCoarser. GhostFromFiner are interpolated but ghostFromCoarser needs correct boundary value in fine level sub-iteration.

number of local (this process) boundary elements per level wihtout Ghost elements

number of total (total processes) boundary elements per level

number of local boundary elements

number of total boundary elements

whether this boundary requires qVal

has qVal initialized with default qVal = 0.5

if this is a wall or symmetry BC (implicit treated during streaming)

Average normal direction of this boundary along layout%prevailDir Normal in elemLvl is normal direction per element and this is normal per boundary

which is the index in the stencil corresponding to the normal vector?

Boundary ID

kind of this boundary

name of this boundary

number of neighbors fluid element needed for extrapolation to get data at boundary element

Curved boundaries are treated with qValues and extrapolation of nonEq from 2nd neighbor

Level wise neighbor information of boundary elements Each field may have a different handlement on the same boundary Thus requires a different neighborhood allocated in mus_alloc_fieldBC

Level wise element information of boundary elements like stencil position in array of stencils, moments type for momentBC and LODI array for NRBC allocated in mus_alloc_fieldBC

function pointer to boundary routine to call

function pointer to compute bndForce on wall

musubi bc state variables

Dictionary of boundary variables with varDict%val()%key is the name of boundary variable and varDict%val()%value is the name of spacetime function variable

order of boundary which determines number of neighbor need for this boundary

standard q-value for higher order boundaries without any definition in seeder

Non-reflective boundary type

slip wall factor

black box membrane boundary

whether this boundary needs neighbors on compute stencil

Is true if this boundary requires boundary variables on boundary surface linkwise. Required to compute real coordinates points on boundary surface

Is true only if boundary requires neighbuf Pre-collision values from next time step

Is true only if boundary requires neighbuf Pre-collision values from current time step

Is true only if boundary requires neighbuf Post-collision values

Collect corner BC i.e elements which are interesected by multiple boundaries only for moments based BC

Level-wise links that are to be updated size: minLevel:maxLevel allocated in mus_alloc_fieldBC

Level wise wall bouzidi data size: minLevel:maxLevel

Level wise inletUbbQVal data size: minLevel:maxLevel

Level wise inletBfl data size: minLevel:maxLevel

Level wise nonEquilibrium extrapolation data for link-wise implementation size: minLevel:maxLevel

Level wise outletExpol data size: minLevel:maxLevel

Turbulent wall model type contains function pointers to compute friction and stream-wise velocity. Also stores friction velocity and turbulent viscosity on boundary elements

Number of unknown state links to update

known moments position in moments vector

inverse matrix of unknown pdf matrix

Positions in levelDesc total list Its purpose is to get the treeID of BC elements size: globBC%nElems to use: levelDesc(iLevel)%total( globBC%elemLvl(iLevel)%elem%val(iElem) )

Position of this boundary in the bc_elemBuffer bc_elemBuffer is growing array initial size: globBC%nElems It is initiated in mus_init_bc_elems of mus_bc_header_module Only non-wall BC needs elemBuffer

Normal vector for each boundary element pointing into the domain. normal is a growing array with size: normal%val(3, nElems)

which is the index in the stencil corresponding to the normal vector?

bit mask for each node holding directions which have to be updated. The bitmask points into the incoming direction into the flow domain, which actually we want to update * For PUSH, we write to the incoming position, as the kernel reads it from there without propagation. * For PULL, we need to write to the inverse direction, as the kernel performs a bounce back before reading it. However, this bounced back direction actually comes from the non-existent boundary element and would point into the incoming direction, so the value has to be treated and set as if it points really into the incoming direction. bitmask is a growing array, the values are in bitmask%val(:,:) 1st index size is QQN since center is not treated for bcElems

The q-Values for the exact wall positions Its size: QQN, nElemsBC It is allocated in routine: allocateBCList assigned in routine: assignBCList

number of local boundary elements per level

boundary neighbor in different refinement level

boundary id in each direction for each corner node size layout%stencil%QQ, nElems

size: links(iLevel)%nVals

set in routine: mus_set_bouzidi

size: links(iLevel)%nVals

set in routine: mus_set_bouzidi

size: links(iLevel)%nVals

set in routine: mus_set_bouzidi

size: links(iLevel)%nVals

set in routine: mus_set_bouzidi

size: links(iLevel)%nVals

specific heat ratio appears in eq 3: cs = sqrt( kappa * R * T )

from eq 17: k = sigma * ( 1 - Ma^2 ) * cs / L

used in eq 17

used in eq 17

length between inlet and outlet, represented by L in the paper

Lattice Mach number characterised by lattice flow velocity

type of membrance (AEM or CEM)

transference number defining transfer property of ionic species on the membrance KM

osmotic solvent transport coefficient

Velocity at boundary

mass flow rate at boundary node for mfr (mass flow rate) boundary condition

Pressure at boundary

mole fraction for species boundary

molar flux for species (c_i*u_i)

mole density for species (c_i)

molar diffusion flux for species

probability density function for boundary

potential for Poisson boundary

surface charge density for Poisson Neumann boundary

array

size

Neighbor position in level-wise state array size: nNeighs, nElems allocated in routine: setFieldBCNeigh, mus_construction_module

Pre-collision state values of neighbors on normal direction on next time step size: nNeighs, nElems*stencil%QQ It is allocated in routine update_BClists

Pre-collision state values of neighbors on normal direction on previous time step size: nNeighs, nElems*stencil%QQ It is allocated in routine update_BClists

Post-collision state values of neighbors on normal direction size: nNeighs, nElems*stencil%QQ It is allocated in routine update_BClists It is filled in fill_neighBuffer

Post-collision state values of neighbors on all directions at current time step. Its also a Pre-collision state values of an element next to boundary at next time step size: nElems * computeStencil%QQ It is allocated in routine update_BClists (mus_construction_module), filled in routine: fill_computeNeighBuf (mus_bc_general_module). it use AOS layout always!

Position of stencil of each element in array of stencils in layout. Unique stencil label for boundary stencils are created with boundary label and stencil%cxDir therefore each stencil is limited to one boundary type Dimension: globBC%nElems(iLevel) allocated in mus_build_BCStencils (mus_construction_module)

LODI array for the NRBC Dimension: 4, 3, globBC%nElems(iLevel) allocated in init_nrbc routine

defined moments position in moments matrix and inverse of unknown pdf matrix Dimension: bc%nElems(iLevel)

Position in LevelDesc%neigh%NghElems size: globBC%nElems(iLevel) allocated in mus_build_BCStencils routine, mus_construction_module

field boundary type

boundary data from mesh

lua flu state

bc parent handle

Global variable system required to append annoymous boundary variables

stencil information

Number of direction excluding center since center is never treated for bc elems

number of valid BC elements

their position in bc_elems_type

BC elements information

BC elements information

Level Pointer ( position of a element in level desc )

Level Descriptor

number of BC elements

BC elements list that contains their position in levelPointer

number of valid (non-solid) elements

positions of valid elements in globBC elements list

number of BC elements

number of BC elements

cIn, cOut, cNgh should have size of nLinks

setting type for bc

using mesh information

for directions

number of scalars

for number of elements in boundary and position in buffer

level descriptor

for position of outgoing elements

for linkwise treatment

minimum and maximum level

minimum and maximum level

setting type for bc

using mesh information

for directions

number of scalars

for number of elements in boundary and position in buffer

level descriptor

for position of elements

for linkwise treatment

minimum and maximum level

minimum and maximum level

setting type for bc

Curved or straight boundary

using mesh information

for directions

number of scalars

scheme global boundary type

boundary neighbor

contains global state vector

level descriptor

for position of elements

for linkwise treatment

minimum and maximum level

minimum and maximum level

setting type for bc

for directions

number of scalars for number of elements in boundary and position in buffer

for position of elements Number of links on each level

minimum and maximum level

minimum and maximum level