visit: Some variables in vtkMultiBlockDataSet are not available

Describe the bug

I am attempting to visualize multiblock vtk files produced by GEOSX in VisIt. These regions include different sets of variables, some of which have the same name across all region. When opened, the variable list in VisIt reflects the first region listed in the .vtm file.

For variables with shared names across regions, I can use the group selection to visualize the model as expected: image

If I attempt to do the same for a variable that only exists in one region, I get the following error message: An invalid variable (elementAperture) was specified. If only the appropriate regions are active in group selection, then the visualization works correctly.

Helpful additional information

To Reproduce

To obtain the error message:

  1. Modify one of the .vtm files, so that SurfaceElementRegion is listed first
  2. Attempt to create a psuedocolor plot of elementAperture

Expected behavior

Each region in a multiblock vtk file should be considered for the variable list, and the code should not produce an error if a variable is missing in a region (or at least provide a more helpful error message).

Attachments

I have attached a small test database and session file here:

geosx_multiregion_example.zip

Desktop

  • TOSS (Pascal)
  • VisIt Version: 3.1.4

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 38 (20 by maintainers)

Most upvoted comments

@biagas - Sure, there is no issue there

I need to add more logic to support you opening just a single .vtm file, because that currently isn’t handled (for your flavor of .vtm). Will start on that.

Time pick works with the updates to the reader. I did need to change the QueryOverTime options for the x-axis to Time as shown below. Timestep would work too. This is due to my not populating ‘Cycle’ for the reader.

queryOverTimeOptions

I’ve attached the dlls that you can install. Unzip them to your VISIT user-home directory. You can double check its location by running visit.exe -env, and the first entry for VISITPLUGINDIR is where VisIt will look for private plugins. Put the dll’s in a databases subdirectory.

Let me know what you think.

I will test out the time-pick, then upload the dll’s in a tarball.

@cssherman I have made progress incorporating a GEOS-flavor to our VTK database plugin. I tried to make it seamless (eg just open your .pvd file and the reader will do the right thing). It is currently keyed off the presence of block names CellElementRegion or SurfaceElementRegion or ParticleRegion or WellElementRegion in the first .vtm file. If any of these are present it considers the data to be GEOS flavor, otherwise reads the .pvd and .vtm files as currently handled.

Each .vtm file is brought into VisIt as a single mesh, with multiple groups (could be renamed regions if you prefer). Each group contains however many blocks were specified as the individual .vtu files.

Here is the Pseudocolor menu for the THM test case: THM_test_case_pseudocolor_menu

And here is a Mesh plot of the particle region example, with a Pseudocolor of particleDamage at the partition, also showing the Subset selection window with group and block designations. The groups option could be used to turn on/off regions of intereset.

ParticleCrossingPartition_ShowinSubsetSelectionWindow

The group names are currently very verbose, I was just trying to capture as much information from your hierarchy as possible while still fitting withing VisIt’s infrastructure.

Please let me know your thoughts on the current interface.

If you would like to take it for a spin, I can give you the plugin files to build as a ‘private plugin’, with instructions on how to build. If you are on Windows, I can simply provide the dlls.

Work is currently off our develop branch, but should work with 3.4.x VisIt.

I’m not up-to-date on this conversation, but the current version of VisIt is 3.4.1.

@JustinPrivitera - good point. I’ve updated to this version, and see the same observations detailed above.