Mark C. Miller

> Out-of-bounds coloring is already available in Pseudocolor plot: Yeah, that is what I was thinking about I think when I added *out of bounds* there. But, I was also...

> The way it is implemented for PC plot directly correlates to how it is handled in VTK. @biagas are you saying we should do it this way because VTK...

You can watch what happens when I do this in the attached video. https://github.com/visit-dav/visit/assets/5720676/b994a6a9-5f6d-4469-86de-b78ce2f6c3d3

If I disable mfem, I get the same problem with conduit. The engine includes and links with conduit so any dependencies for conduit get linked into the engine.

@iulian787 and @vijaysm if I disable conduit, mfem and fsm in my build, I can get the engine to run and use MOAB in parallel correctly... ![Screen Shot 2024-05-26 at...

> When you say MOAB parallel engine is working correctly, I assume this means there are no HDF5 property table errors that we were seeing before? Yes, correct. > I...

Was chatting with @brugger1 about this. One idea he has...build `engine_par` against `hdf5_mpi` instead of `hdf5`. That would fix the collision with `MOAB` parallel database plugin. But, it would mean...

> @markcmiller86 conduit and mfem were added as dependencies when avt/Blueprint and avt/MFEM were added. > With those additions, we also get whatever dependencies conduit and mfem have. Yes, that...

> Both Conduit and MFEM are used outside of the database plugins. Sure...but I guess my question is...what do conduit and MFEM need to do in the way of I/O...

Ok, I tried a simple test with my build of VisIt 3.4.1. on macOS where I have disabled MFEM and conduit. But, I do have things like Silo (which is...