9 Select a subset of the mesh entities
11 This is a sole helper class: It does not generate any C++ code itself
12 and is not an action set. It merely hands out guards, i.e. C++
13 snippets which other Python classes, such as action sets, can embed
14 into their generated code to decide whether they should act on a
15 particular vertex, face or cell.
17 Each routine returns a string which has to be a C++ boolean expression.
18 The expression is evaluated in a context where the corresponding marker
19 is available as marker, i.e. it can query the
20 peano4::datamanagement::VertexMarker, peano4::datamanagement::FaceMarker
21 or peano4::datamanagement::CellMarker, respectively.
31 C++ boolean expression over a peano4::datamanagement::VertexMarker
40 C++ boolean expression over a peano4::datamanagement::FaceMarker
49 C++ boolean expression over a peano4::datamanagement::CellMarker
57 C++ boolean expression over a peano4::datamanagement::VertexMarker
58 called marker which decides whether a vertex's data is stored at
59 the end of a mesh sweep
61 Peano's stacks require that data stored in one mesh sweep are
62 loaded in the next one. The load is guarded by createVertexGuard().
63 If this guard depends on the refinement state, the store therefore
64 has to anticipate the state of the next sweep. By default, we use
65 createVertexGuard(), which is correct for selectors that do not
66 depend on the refinement state.
69 return self.createVertexGuard()
74 Counterpart of createVertexStoreGuard() for faces
82 Counterpart of createVertexStoreGuard() for cells