Blueprint reader can mess up fields for point meshes. #20273
Labels
bug
Something isn't working
impact medium
Productivity partially degraded (not easily mitigated bug) or improved (enhancement)
likelihood medium
Neither low nor high likelihood
Describe the bug
I noticed in
ExplicitCoordsToVTKPoints
that there is code to check the topology to make avtkPoints
object that contains only the used points for point meshes. Vertex-associated fields will have the number of values that the coordset has. This operation reduces the number of points in the VTK dataset, making it no longer match any vertex-associated fields. Later when a vertex-associated field is retrieved, VisIt just copies it into a VTK data array and serves it up. The field has the wrong number of values for the mesh.Either:
a) Remove this behavior when constructing the points (add them all like other unstructured topos)
b) Or, use the connectivity to pull out the relevant field values when making a field
Option a is probably easiest/best.
To Reproduce
This YAML file makes 8 points but only selects 4 of them via connectivity. When making a PC plot of "wrong", it shows all 10's instead of the negative values that should be shown, according to the connectivity.
Take this YAML file and convert it to blueprint.
conduit_relay_io_convert pointmesh.yaml pointmesh --write-protocol blueprint
Expected behavior
Plot the data, get 4 points, and show the negative values for a PC plot of "wrong".
Desktop
/usr/gapps/visit on RZ.
The text was updated successfully, but these errors were encountered: