BoundaryHandling Documentation
Draft:
Section 1: Boundary Handling
- Basic Idea
- "copydoc" from FlagField: why FlagUID?
- FlagField, simple case: flag corresponds to boundary / domain
- generalize: boundary/domain can be masks
-> explain need for BoundaryUID vs. FlagUID
- sidenote: Optimization with near boundary flag
or ListBased Approach ( description howto switch )
- what is a consistent state?
- boundary concept: how to implement a own boundary ( copydoc / nice format )
- Practical Usage:
- why templates?
- setup using tuples
- set/force/remove
- boundary handling factories
- explain difference between Flag/Domain/Boundary: difference is only 'optimization level'
Section 2: Boundary Handling Collection
- reason "multiphysics simulations"
- explain using example: picture ( fluid, temperature )
- explain why setBoundary(FlagUID) does not exist
- do some crazy scenario setups....
Section 3: Initializer i.e. what they can/cannot do. - @bauer