-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Allow promotion of geometry dimension for built-in mesh creators. #3471
base: main
Are you sure you want to change the base?
Conversation
I will now do the work on the C++ interface to get this parameter up to |
@@ -72,7 +72,7 @@ refine(const mesh::Mesh<T>& mesh, | |||
|
|||
mesh::Mesh<T> mesh1 = mesh::create_mesh( | |||
mesh.comm(), mesh.comm(), cell_adj.array(), mesh.geometry().cmap(), | |||
mesh.comm(), new_vertex_coords, xshape, partitioner); | |||
mesh.comm(), new_vertex_coords, xshape, mesh.geometry().dim(), partitioner); |
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.
Shouldn’t xshape[1] and mesh.geometry().dim() be the same?
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.
Yes - but in terms of the code being correct in meaning, the former is the shape of the geometry data and the latter is the geometric dimension.
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.
Do we check if they match? We should probably add some sanity checks.
…olfinx into jhale/add-gdim-to-mesh-creators
There is currently no easy way to create e.g. a unit interval living in 2d or
3d geometric space.
After discussion of this implementation I will implement the others the same way.