improve implementation of boundary ids
- we could use the fact that
domain["boundary"][i]
is directly passed through todune-alugrid's
grid factory as integer vector. So it would be easy at least for alu to add an additional entry to the vector for the boundary id, sodomain["boundary"][i] = [p1,p2,p3,id]
for a triangle boundary segment in a 3d grid. - we could export some functionality on the
boundaryIdProvider
instance, i.e.,dune.fem.boundaryDomain(gv,[[lower],[upper]],id)
to describe a boundary domain similar to dgf'sboundaryDomain
. To information could be stored in theboundaryIdProvided
which is a singleton over the grid or on the pythongridView
instance. Adune.fem.boundaryDefault(gv,id)
could then also be provided and this allows the same control over the boundary ids as we have in dgf.
See also #118
Edited by Andreas Dedner