-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add a 3D paraview extractor option corresponding to layer thicknesses? #264
Comments
There are a few options. We could put this script as-is in MPAS-QuickViz: Or, we could test it on a few meshes, make sure it is general, test in python-3, and put it in MPAS-Tools. |
@mark-petersen, I'm thinking, pending discussion with @xylar (I emailed him), that we would want to have this capability moved into the paraview extractor. You are right-- minimally, we can merge to QuickViz, but I think we want something more robust in the long term-- hence this tread to open up the discussion. |
@pwolfram, I agree that this should be possible. I can't quite remember if we're already telling the extractor enough in order for the water-tight bathymetry to work for it to also know how to construct a vertical coordinate. My guess is not yet. The extractor should work for 3D fields from all MPAS components that will use it, so I guess we need a way of specifying which field contains layer thickness? The vtk extractor works with a completely different library (pyevtk) than the example code above so I don't think it would be possible to do more than use it as a rough pseudocode for the changes that would be needed in the extractor. Anyway, I'll be around starting in early August and that's likely the soonest I'd be able to help with this. |
@pwolfram , do you have any example visualizations of this? Trying to wrap my head around what this implementation would look like. Would it be helpful for passive/isopycnal LIGHT trajectories? |
@xylar, that is correct -- we will need another flag to specify something like @GregAbram has the examples for this code-- @bradyrx it is to get 3D Eulerian fields and it could be a very useful background field (e.g., volumetric rendered cloud) that particle trajectories and streamtubes could advect through. |
I'm trying to generate 3D files for volume rendering. Is the code above what I should be using? Has something else been added somewhere? |
We have had no time to implement 3D vtk files yet. It's been on my to-do list but I don't think I will be able to work on it anytime soon. |
In order to represent volumetric data in ParaView we need to restructure the data in such a way that volume rendering will work (e.g., topologically 3D vs 2D).
The reason to do this is so that a full 3D volume can be output in https://github.com/MPAS-Dev/MPAS-Tools/blob/master/visualization/paraview_vtk_field_extractor/paraview_vtk_field_extractor.py
@GregAbram's code is at https://gist.github.com/d963664449fe02f511099dc272c47d1a (copied below for convenience)
cc @GregAbram, @xylar, @mark-petersen
The text was updated successfully, but these errors were encountered: