-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Wrap mesh tags from Python #2522
Conversation
Thanks @garth-wells, I'll test this with |
|
||
new_meshtag = _cpp.refinement.transfer_cell_meshtag(meshtag, fine_mesh, parent_cell) | ||
|
||
new_meshtag = _cpp.refinement.transfer_cell_meshtag(meshtag._cpp_object, fine_mesh, parent_cell) |
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 guess this indicates that we should wrap up refinement.transfer_cell_meshtag
and refinement.transfer_facet_meshtag
in the Python Layer.
This would probably be true for plaza_refine_data
, as it returns a cpp.Mesh
, which should be wrapped as a Python 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.
This will need further work to sort out.
Co-authored-by: Joe Dean <[email protected]> Co-authored-by: Jørgen Schartum Dokken <[email protected]>
Wrap MeshTags from Python. Fixes #2519.
Also, a major simplification of building lists of entities to integrate over in
fem::Form
. This will allow changes on the Python side that will be more forgiving of (mesh tag) marker type.