You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are using hex-meshes mainly to represent voxel meshes.
In this case you should be able to use some improvements:
it might be better to use the sub-entity center search instead of the normal projection, as you have a structured (voxel) mesh
instead of writing an unstructured grid file for a structured grid it would be more appropriate to go for the structured grid and the filter cells using dune-subgrid, like we do it for node shift meshes (where we also start with the voxel mesh).
The text was updated successfully, but these errors were encountered:
What implications would this have in the future?
I would prefer (from a limited understanding) the unstructured grid options even if it requires more memory/computation-time. When dealing with mri->mesh libraries we cannot limit our work to those libraries that generate a structured grid.
Or perhaps I'n not really understanding the point?
voxel meshes with node-shift
and potentially in the future
unstructured hex meshes
The unstructured hex mesh is currently used, but it imposes more costs. I don't suggest to remove this code path. The proposal is to add an improved code path for voxel meshes.
You are using hex-meshes mainly to represent voxel meshes.
In this case you should be able to use some improvements:
The text was updated successfully, but these errors were encountered: