Bounds from CGNS zone are based on all coordinates array, not on actual cells
Hello,
First, my apologies for that strange title, I am not sure how I can put what I am seeing into words. So here is the complete story, in less compact format:
We use the CGNS format as output of our CFD solver. The files contain two zones: Volume and Surfaces These two zones contain arrays defining all vertices present in the zone. This means that the Volume zone contains all vertices, and the Surfaces zone contains all boundary vertices.
Both zones can contain multiple sub-zone: various grids for the Volume zone, and the boundary cells for the surfaces.
To extract a specific boundary, I use the extract block filter, and choose the blocks I want.
The issue I am seeing now with version 5.11 is that if I extract only one zone, the bounds still correspond to all vertices, and not to the vertices shown on the screen.
This was not happening in 5.9
To reproduce:
- Read the file, using the CGNS reader
- extract the first block
- look at the bounds: they are not what one expect it to be
So I have a feeling that the CGNS reader was changed and now only relies on the complete array of vertices to define the bounds instead of relying on the cells that are actually declared in the specific block.
I hope that makes the issue clearer. (and I attached an example file file too)