Adding a netgen flag to specify the index value associated with each label#26
Adding a netgen flag to specify the index value associated with each label#26UZerbinati wants to merge 4 commits intomainfrom
Conversation
Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
pefarrell
left a comment
There was a problem hiding this comment.
I don't know. This seems misguided. I would prefer the interface where the user code would look like
DirichletBC(V, 0, "outer")
and for the user to forget about the integer labels altogether. @rckirby , what do you think?
|
This PR is motivated by a use case where I'm hooking up to an external operator that can only do its thing on a boundary if all the boundary segments of interest share the same integer label. So your cleaner interface is cleaner but... Does anything stop us from using this PR to relabel all "inner" as "inner" rather than 1, that is, the first "inner" corresponds to sets of boundary segments in the netgen geometry and the second refers to labels that we attach to those edges in the mesh? |
Exactly the issue is that Netgen will number differently entities with the same labels, what we do here is to force all entities with the same label to have a given id in the DMPlex when conversion happens.
Can we attach a label that is a string to the entities of a DMPlex, I only have seen Firedrake using integers. |
Adding a netgen flag to specify the index value associated with each label.
Here is a minimal working code.