-
Notifications
You must be signed in to change notification settings - Fork 62
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
Unsupported cell types: pyramid, wedge #1249
Comments
related to: we do have arbitrary polyhedral support, here is an test that plots one of our example meshes: https://github.com/Alpine-DAV/ascent/blob/develop/src/tests/ascent/t_ascent_render_3d_poly.cpp This allows you to have heterogeneous element types within a topology as well as polyhedra. Long term: goal is to support unstructured pyramids and widgets, as well heterogeneous elements w/o the full polyhedra spec. |
Is there a proposed Conduit syntax for what mixed topologies (but with fixed element types rather than polyhedra) would look like? |
Yes, Blueprint provides the a concept of a shape_map + a shapes array, and a set of indexed arrays for this case: The conduit braid example dataset has a
For the case w/o polyhedra, you won't need the sub-elements -- it would look more like:
|
Perfect! I'll get support wired up in our code for this. We only need it for pyramids (since being high-order we have to subdivide and pyramids divide into pyramids and tets giving rise to a mixed grid). What are the blockers in terms of getting Ascent ready for pyramids and prisms? |
We will first add pyramids and wedges as single element types, then support mixed meshes. |
#1302 Adds support for all pyramid and all wedge typologies. |
Meshes which use
pyramid
akaPYRA_5
as well aswedge
akaPENTA_6
elements, as specified in the conduit mesh docs, are not supported as seen here:ascent/src/libs/ascent/runtimes/ascent_vtkh_data_adapter.cpp
Line 479 in 6d1ca3f
Are there plans to support this, or the arbitrary polyhedron type?
The text was updated successfully, but these errors were encountered: