This causes a problem when the material ids don't start at zero.
Helpful additional information
Did VisIt crash: no
Did you get wrong results:
mdserver fails while digesting materials metadata (doens't crash, but prevents us from opening the file)
finding coordinate system
coordinate system:
axes:
x:
y:
type: "cartesian"
(ndims=2)
adding field vars for mesh
adding materials for mesh
adding material set mesh_MESH mesh_MESH_MATERIAL
material map
box: 1
(caught invalid access in conduit)
Describe the bug
There are places were we index by an integer id, instead of a name.
Here is one of them: https://github.com/visit-dav/visit/blob/91ff5211fbae8256bb8590688ca37106b24fef5c/src/databases/Blueprint/avtBlueprintFileFormat.C#L949
This causes a problem when the material ids don't start at zero.
Helpful additional information
mdserver fails while digesting materials metadata (doens't crash, but prevents us from opening the file)
Expected behavior
Map logic should handle this case.
Desktop