-
Notifications
You must be signed in to change notification settings - Fork 18
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
Convert tool to convert wmtk mesh types #832
Conversation
…g_to_multimesh_component
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #832 +/- ##
==========================================
+ Coverage 76.62% 76.77% +0.14%
==========================================
Files 463 466 +3
Lines 23035 23374 +339
Branches 2580 2620 +40
==========================================
+ Hits 17651 17945 +294
- Misses 5373 5418 +45
Partials 11 11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -0,0 +1,7 @@ | |||
{ | |||
"tests": [ |
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.
we need tests for this
…n input component
…ng_to_multimesh_component
…ng_to_multimesh_component
We currently support 2-3 mesh formats within the toolkit (vtu / hdf5 / msh) and it would be useful to be able to directly create/manipulate meshes using them. This is particularly annoying because hdf5 supports multimesh configurations while others do not - For building examples that use multimesh we can create simple input/output pairs by sticking to hdf5 / use this tool to help build hdf5 files from inputs