I’m using Paraview to visualize and analyze data from ExodusII-Files. Those ExodusII files consist of a number of blocks. Using “object properties” (see section 4.12.1 in https://sandialabs.github.io/seacas-docs/exodusII-new.pdf) I tried to define groups of objects (e.g. all blocks to be examined in detail, or all blocks representing a special part of my model, etc.).
Now, it seems that Paraview is ignoring those “object properties” in my ExodusII file. To be more precise: I do not find them anywhere in Paraview (but they are present in my ExodusII-file according to netcdf-ncdump.exe).
Now I’d like to ask some questions:
Does Paraview allow to represent groups of blocks (where one block may be assigned to several groups)?
Is Paraview really ignoring the ExodusII object properties? Or did I miss something?
Depending on the answer to the questions above: Ho to use ExodusII object properties to have block groups?
I’m afraid no. You can store that information in the form of FieldData with some duplication of information, but it will be your own formalism and ParaView will interpret it just as data.
Is Paraview really ignoring the ExodusII object properties? Or did I miss something?
Looks like it does, but you will need to share some data if you want us to check
First of all, thank you very much for your reply and the information. This clears things up.
As kind of a feature request: The option to have groups of blocks in Paraview would be great.
Please find attached an exodus model consisting of an array on blocks. The blocks get activated/deactivated over time and are assigned to two groups: “OddVolumes” and “EvenVolumes” (via eb_prop2 and eb_prop3).
