Dear all,
I have encountered a weird issue that occurs in ParaView 6.0.
I am working on a multiresolution unstructured grid files where there are overlapping faces on transitions from one resolution to another.
(I have attached python code to create your own test configuration for that using flow.py (3.5 KB))
On both ParaView 5.13.3 and 6.0, adding a standard streamtracer (keeping all default values) results in these artifacts at region boundaries:
StreamLines are terminated for crossing “the exterior boundary of the input dataset”, which seems to happen inconsistenly.
While trying to investigate this behavior, I stumbled across an even weirder issue:
In ParaView 5.13.3, this problem is fixed by chosing the Cell Locator for interpolation.
However, in ParaView 6.0, changing this parameter does not have any effect whatsoever.
Here are the same configarations with only that setting changed:
Not sure if this is a bug within the StreamTracer implementation of VTK or within ParaView.
I’d be happy to find a reliable way to get my streamlines through those non existing “exterior boundaires” and am happy for any help.
Could you elaborate a bit more what you mean by invalid?
We are working with simulation scientists that are currently writing their simulation results to file in a similar manner than in the python script I provided by converting from hdf5 to vtu.
I have attached a small working example vtu file here created from the python script, which shows the same behavior: layered_grid_with_flow.vtu (259.2 KB)
Still, using a the cell locator changes the resulting lines only in 5.13 - not in 6.0.
For convenience, here’s also the paraview statefile (obviosly using my local path to the file): pipeline.pvsm (352.2 KB)
multiresolution unstructured grid files where there are overlapping faces
This is invalid in the sense that VTK/ParaView cannot build correct neighboring information in that case, which can cause some issues with certains filters like the stream tracer.
In any case I reproduce the issue, it looks like the integrator is not correctly initialized somehow. You can work around that using the cell locator then changing the integration type until it works.
