Skip to content
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

Can't correctly volume rendering UGRID data from GeoFlow #2889

Closed
clyne opened this issue Oct 29, 2021 · 3 comments · Fixed by #2894
Closed

Can't correctly volume rendering UGRID data from GeoFlow #2889

clyne opened this issue Oct 29, 2021 · 3 comments · Fixed by #2894
Assignees
Milestone

Comments

@clyne
Copy link
Collaborator

clyne commented Oct 29, 2021

The OSPray volume renderer does not render the UGRID data from GeoFlow correctly. The data set fills the entire domain, however an OSPRay volume rendering only draws something on one side of the domain as seen in the attached image.

To reproduce:

  1. Import the all of the UGRID files in /glade/p/cisl/vast/vapor/data/Source/UGRID/NOAA-geoflow/small (note, need to use the UGRID, not CF importer)
  2. Enable the volume renderer

geoflow

@clyne clyne added the Bug label Oct 29, 2021
@sgpearse sgpearse added the High label Nov 3, 2021
@StasJ
Copy link
Collaborator

StasJ commented Nov 3, 2021

@clyne have you confirmed that the grid is being imported correctly? I looked at the wireframe and, while I cannot be sure as I am unfamiliar with this data format, it does not look quite right to me. Also, I cannot see any discernible patterns in any of the variables over the noise.

@clyne
Copy link
Collaborator Author

clyne commented Nov 3, 2021

The wireframe looks reasonably correct to me, though it is hard to tell with 3D and perspective projection. I've attached an image using orthographic projection. The data also looks correct (verified by the NOAA people). See the attached slice of 'dtotal' variable.

dtotal_wireframe
dtotal_slice

@StasJ
Copy link
Collaborator

StasJ commented Nov 4, 2021

Ok, sounds good. It does look quite different from the other unstructured datasets I've worked with so far. I can see the variables clearly in your picture. I was looking at the wireframe and the data is too high frequency to see clearly in the wireframe alone, my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants