Save pvtu Data Does Not Respect Request to Save 0 Ghost Levels
Save pvtu Data Does Not Respect Request to Save 0 Ghost Levels, when there are ghost cells
To replicate,
Run client - server with 4 ranks
Make an unstructured grid and save pvtu:
- Load wavelet all defaults (gives 8000 cells)
- Run D3 filter (all defaults hit accept, "boundary mode" = "assign cells uniquely") (gives 8000 cells) (this might be a separate bug, d3 doesn't generate ghost cells when run on structured grid data, but it does when run on pvtu data.)
- Save Data as a pvtu, filename=deleteme, set GhostLevel=0 in dialog after entering file name
Load a pvtu - make it have ghost cells and save:
- Load "deleteme.pvtu" saved in previous step (gives 8000 cells)
- Run D3 filter same options as before (gives 9680 cells), there are now ghost cells
- Save Data as a pvtu, filename=deleteme2, set GhostLevel=0 in dialog after entering file name (same as before different filename)
Load a pvtu:
- Load "deleteme2.pvtu" gives 9680 cells which includes ghost cell data
Attached is a python trace of the above steps, It shows the GhostLevel=0 on the above saves.ExampleOfGhostCellSave.py In hind sight, you could probably get the same results by running D3 on the results of the first D3 without going through the save process.... Nope.
ParaView 5.2.0, mac client, snow supercomputer default build