deal.II version GIT relicensing-1982-gbb401394a0 2024-10-13 08:40:01+00:00
|
#include <deal.II/base/geometry_info.h>
Public Types | |
enum | Possibilities : std::uint8_t { no_refinement = 0 , cut_x = 1 , cut_y = 2 , cut_xy = cut_x | cut_y , isotropic_refinement = cut_xy } |
A class that provides possible choices for isotropic and anisotropic refinement flags in the current space dimension.
This specialization is used for dim=2
, where it offers refinement in x- and y-direction separately, as well as isotropic refinement in both directions at the same time.
Definition at line 616 of file geometry_info.h.
enum RefinementPossibilities< 2 >::Possibilities : std::uint8_t |
Possible values for refinement cases in the current dimension.
Note the construction of the values: the lowest bit describes a cut of the x-axis, the second to lowest bit corresponds to a cut of the y-axis and the third to lowest bit corresponds to a cut of the z-axis. Thus, the following relations hold (among others):
Only those cuts that are reasonable in a given space dimension are offered, of course.
In addition, the tag isotropic_refinement
denotes isotropic refinement in the space dimension selected by the template argument of this class.
If you choose anisotropic refinement, for example by passing as argument to CellIterator::set_refine_flag() one of the flags RefinementCase::cut_x, RefinementCase::cut_y, RefinementCase::cut_z, or a combination of these, then keep in mind that refining in x-, y-, or z-direction happens with regard to the local coordinate system of the cell. In other words, these flags determine which edges and faces of the cell will be cut into new edges and faces. On the other hand, this process is independent of how the cell is oriented within the global coordinate system, and you should not assume any particular orientation of the cell's local coordinate system within the global coordinate system of the space it lives in.
Definition at line 652 of file geometry_info.h.