search

visit-dav / visit

VisIt - Visualization and Data Analysis for Mesh-based Scientific Data
https://visit.llnl.gov
BSD 3-Clause "New" or "Revised" License
406 stars 110 forks source link

CGNS higher order elements #5518

Open aowen87 opened 3 years ago

aowen87 commented 3 years ago

The CGNS reader in VisIt currently reduces higher order elements to linear ones and issues a warning. Since we can support higher order elements now, we should update this.

brugger1 commented 3 years ago

Here is an e-mail about high order elements on the CGNS mailing list.

Hi,

Right now there are no known major incompatibilities concerning High Order. In the future, as High Order CPEXs goes mainline for CGNS 5.0 version, some incompatibilities may arise. The incompatibilities should mainly be about interpolation solution location storage but other CGNS users could provide a more detailed explanation.

By the way, there is a nice blog post on Pointwise website about High order: http://www.pointwise.com/theconnector/2016-Q3/High-Order-Mesh-Generation-at-Pointwise.html

For reference, the HO mesh generated in NASA drag prediction workshop seems to be in CGNS: https://how5.cenaero.be/content/mc1-high-lift-common-research-model

And finally, if you have any proposal to improve CGNS regarding this topic you are welcomed.

Best Regards

Mickael

aowen87 commented 3 years ago

I tried loading the NASA data into VisIt, but VisIt can't recognize the file. I tried to "force" using the CGNS reader without any luck.

markcmiller86 commented 3 years ago

I tried this file on my just now build of 3.2 and was not able to do a mesh plot of Zone_1. Get this error message...

The compute engine running on host scratlantis issued the following warning: VisIt found quadratic or cubic cells in the mesh and reduced them to linear cells. Contact visit-users@ornl.gov if you would like VisIt to natively process higher order elements.
aowen87 commented 3 years ago

I just tried to load that data into VisIt as well, and it looks like there might be something else wrong with visualizing that mesh. I don't think that the reduction to linear cells should cause this crash...