[meta] Revamp boundary condition input and handling
Note: This is a meta-task. It bundles several tasks together and is only closed once all these tasks are finished.
Aims
This meta-tasks aims at a complete revamp of the input and internal handling of boundary conditions, in a similar way as #63 (closed) rebuilt the paramterization. The new scheme should offer more flexibility, while using explicit mappings to the grid elements (boundary segments).
Again, this feature will be split up into several tasks:
- Rebuilding the file input and mapping, which builds upon the classes created in #86 (closed)
- Using new data structures for representing boundary conditions
- Create internal mappings similar to the ones in
FlowParameters
for efficient access - Reworking the adaptation of time steps to boundary condition changes in
CalculationController
- Wrapping everything together
Tasks
-
#124 (closed): Remove BC options
evaporation
andlimitedInflux
, they never really worked - #123 (closed): Implement new way of specifying boundary segmentations
- #126 (closed): Implement new input of boundary condition data
- #125 (closed): Create new data structure for storing and accessing boundary conditions
-
!121 (merged): Merge everything into revamped
FlowBoundary
People involved
@lriedel, @sospinar (for review?)
Related issues
- #63 (closed) Rebuild of parameterization input
-
#29 (closed) Use
yaml-cpp
for BC input file
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information