8000 Best Practices for mixed canonical/polyhedron zones? · Issue #725 · CGNS/CGNS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Best Practices for mixed canonical/polyhedron zones? #725

8000
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.

Sign up for GitHub

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

Jump to bottom
Open
dbgarlisch opened this issue Jul 10, 2023 · 1 comment
Open

Best Practices for mixed canonical/polyhedron zones? #725

dbgarlisch opened this issue Jul 10, 2023 · 1 comment

Comments

@dbgarlisch
Copy link

As best I can tell, CGNS/SIDS does NOT prohibit mixed element/face zones. The ParaView CGNS reader disagrees.

I don't know of any reason why a reader shouldn't be able to handle mixed element/face zones. It might be a little more work/bookkeeping; but doable.

I have generated mixed element/face zones meshes that load into CGNSview and pass CGNScheck (v3.31) without objection.

I am looking for official guidance on what a valid CGNS export should be for a mesh volume zone that contains both canonical and polyhedron elements...

Do I split out the polyhedron and canonical cells into different zones with the same VC?

Do I write all canonical cells as polyhedron?

Other?

Or is this a practical issue? Since many/most/all readers will most likely balk on a mixed element/face zone, I should play it safe and export a uniform file?

Whatever the official answer, the SIDS and related docs should be amended to make this clear.

See also: #720
@MicK7
Copy link
Contributor
MicK7 commented Oct 16, 2024

You can have classical elements in separate sections (TRI, QUAD, TETRA, HEXA, PYRA...) + ngon/face sections under the same zone.
This should be valid for most readers (as well as for ParaView CGNS reader)

To handle the case of a MIXED section + ngon/nface, it is a lot more tedious for readers. Thus the CGNS/SIDS does not prohibit this mixing but no one has implemented it. To get an efficient implementation you would need to start with MLL CGNS 4.x series.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dbgarlisch @MicK7
0