Skip to content

Fix ghost zone handling when AMR data already have ghost zone.

When the loaded AMR data already have ghost zone, then the vtkAMRUtilities::BlankGridsAtLevel method was discarding the existing ghost zones.

The fix merges the two ghost zone definitions in order to keep the existing ones.

This should fix the first part of this issue: paraview/paraview#19060

Merge request reports