-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce edge integrals #330
base: main
Are you sure you want to change the base?
Conversation
@@ -32,6 +32,8 @@ | |||
# === Integration over topological dimension - 1: | |||
("exterior_facet", "ds"), # Over one-sided exterior facets of a mesh | |||
("interior_facet", "dS"), # Over two-sided facets between pairs of adjacent cells of a mesh | |||
# === Integration over topological dimension - 2: | |||
("edge", "dl"), # Over edges of a mesh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edges are only tdim - 2 in a 3d mesh. Should these be called "ridges" instead (See eg https://en.wikipedia.org/wiki/Face_(geometry)#k-face)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Presumably dl
integrates over points in 2d (just like ds
and dS
in 1D).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ridge
I was thinking about this when looking through UFL. I guess we should decide if we want to support "Edge" (i.e. only 3D-1D), or ridge (2D-0D, 3D-1D)? @cdaversin do you have any opinions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Supporting integration over points in 2D would be nice, even though I think we should focus on 3D-1D for now. We can still use "ridge", but this implies that we will support 2D-0D at some point :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is conflating "things that are expressible in UFL" with "things that are supported in Dolfinx". Lots of things can be expressed in UFL that individual solvers don't support. The point is that the UFL notation should match the maths as closely as possible so that we don't have to go back and make a backward incompatible change when someone expands their capabilities in the future.
I think that the UFL feature should be codimension 2, even if that's not what is supported in Dolfinx right now.
Continuation of @cdaversin work on 3D-1D coupling.