Mesh, grids, and tiles
Mesh
Level-0 mesh
The following inputs are defined using the prefix amr:
Description |
Type |
Default |
|
|---|---|---|---|
max_level |
Maximum level of refinement. The default value, 0, means that there is one cell size covering the entire domain (i.e., single-level). |
Int |
0 |
n_cell |
Number of cells at level 0 in each coordinate direction. |
Ints |
0 0 0 |
The level 0 mesh spacing is computed for each direction by dividing the domain length by the number of cells. The mesh spacing is required to be the same in all directions:
The inputs for defining the mesh for a single-level simulation are demonstrated in the following example and illustrated in Fig. 1. In this example, the domain is a \(4 \times 1 \times 1\) cuboid, and there are \(32 \times 8 \times 8\) cells in the X, Y, and Z directions, respectively. The result is a uniform mesh spacing of \(0.125\) m in all three directions.
# Define periodicity and domain extents
# -------------------------------------------------------------
geometry.coord_sys = 0 # Cartesian coordinates
geometry.is_periodic = 0 0 0 # periodicity for each direction
geometry.prob_lo = 0. 0. 0 # lo corner of physical domain.
geometry.prob_hi = 4. 1. 1. # hi corner of physical domain
# Define the maximum level of refinement and number of cells
# -------------------------------------------------------------
arm.max_level = 0
arm.n_cell = 32 8 8
Fig. 1 Example of a single-level mesh.
Warning
MFIX-Exa simulations with a non-uniform mesh will not run.
Mesh refinement
The following inputs are defined using the prefix amr. These inputs control the automatic
mesh refinement algorithm and are only applicable when amr.max_level > 0.
Description |
Type |
Default |
|
|---|---|---|---|
grid_eff |
Threshold value to ensure grids do not contain too large a fraction of untagged cells. |
Real |
0.7 |
n_error_buf |
Controls the number of tagged cells before grids are defined. Used to ensure coarse/fine boundaries are not too close to tagged cells. |
Int |
1 |
Caution
Mesh refinement limitations:
MFIX-Exa simulations with particles currently do not support mesh refinement.
See the AMReX documentation for details on the adaptive mesh refinement algorithms.
The following inputs are defined using the prefix mfix.tag. They control how cells are tagged
for the mesh refinement algorithm and are only applicable when amr.max_level > 0.
Cells intersected by the embedded boundary are always tagged for refinement, regardless of these settings.
Description |
Type |
Default |
|
|---|---|---|---|
rho |
Tag cells for refinement when the fluid density is greater than the specified value.
|
Reals |
None |
rho.less_than |
Tag cells for refinement when the fluid density is less than the specified value. |
Bool |
false |
grad_rho |
Tag cells for refinement when the difference in fluid density between two adjacent cells is greater than the specified value.
|
Reals |
None |
grad_rho.less_than |
Tag cells for refinement when the difference in fluid density between two adjacent cells is less than the specified value. |
Bool |
false |
vel |
Tag cells for refinement when the difference in any fluid velocity component between two adjacent cells is greater than the specified value.
Tag cells for refinement when the fluid velocity magnitude is greater than the specified value. |
Reals |
None |
vel.less_than |
Tag cells for refinement when fluid velocity magnitude is less than the specified value. |
Bool |
false |
grad_vel |
Tag cells for refinement when the difference in any fluid velocity component between two adjacent cells is greater than the specified value.
|
Reals |
None |
grad_vel.less_than |
Tag cells for refinement when the difference in any fluid velocity component between two adjacent cells is less than the specified value. |
Bool |
false |
regions |
A list of predefined regions used to identify sections of the domain for mesh refinement. |
Strings |
None |
Grids
The following inputs are defined using the prefix amr:
Description |
Type |
Default |
|
|---|---|---|---|
max_grid_size_x |
Maximum number of cells at level 0 in each grid in X |
Int |
32 |
max_grid_size_y |
Maximum number of cells at level 0 in each grid in Y |
Int |
32 |
max_grid_size_z |
Maximum number of cells at level 0 in each grid in Z |
Int |
32 |
blocking_factor_x |
Each grid in X must be divisible by |
Int |
8 |
blocking_factor_y |
Each grid in Y must be divisible by |
Int |
8 |
blocking_factor_z |
Each grid in Z must be divisible by |
Int |
8 |
The domain is decomposed into grids by dividing the number of cells by the max grid size
for each direction (e.g., n_cells[0]/max_grid_size_x). The blocking factor ensures that
the grids will be sufficiently coarsenable for good multigrid performance; therefore, the
max_grid_size must be divisible by the corresponding blocking_factor.
Note
The AMReX documentation contains a significant amount of information on grid creation and load balancing. Users are strongly encouraged to read the relevant sections.
Tiles
The following inputs are defined using the prefix fabarray:
Description |
Type |
Default |
|
|---|---|---|---|
mfiter_tile_size |
Maximum number of cells in each direction for (logical) tiles. |
Ints |
1024000 8 8 |
The following inputs are defined using the prefix particles:
Description |
Type |
Default |
|
|---|---|---|---|
tile_size |
Maximum number of cells in each direction for (logical) tiles
in the ParticleBoxArray if |
Ints |
1024000 8 8 |
When running on shared memory machines using an OpenMP enabled executable, grids are subdivided into tiles and iterated over to improve data locality by cache blocking.
Note
MFIX-Exa disables tiling when using GPU accelerators.