I am not sure that’s the case. I think this may be just a matter of changing the locator used. However switching to cell locator raises can't evaluate datasetset errors.
Mathieu is correct in the identification of the problem. Utkarsh is correct in what would work In the advanced mode of the streamtracer filter, there is an Interpolator Type parameter which when set to a Cell Locator should work. The cell locator does not care about cell neighbors when evaluating positions.
By the way, as Mathieu said, from VTK’s perspective, this is not really a manifold mesh and you will likely run into other issues. One example is that some of the internal faces will be treated as external faces. You can see this by setting the opacity to < 1.
I though of a workaround. create an equivalent fine rectilinear mesh, and then resample the octree solution onto the rectilinear mesh. It works sort of, even though its a bit patchy in places.
Are there any other ways to workaround it using the filters. I though that converting to tetrahedralizing it would do the job? Thanks guys!
OK I now know why this works for me and not for you. It is not because of the version. It is because I have the setting “Auto Convert Properties” turned on and you don’t. Assuming you have this setting, you can turn it on or you can simply run the Cell Data to Point Data filter. There is a small bug and the cell locator does not work with cell centered data. I will look into fixing that soon.
Well nice idea, but having checked that box in v5.2.0 it still imports the file with no contours whatsoever.
(so i dont know why that doesnt work either)
But more importantly - I dont want to have to filter (average) the data in that way.
In version 3 & 4, the file imports and I can see the actual cell centred data just as expected,
so I dont understand why v5 doesnt do this basic task. I just want to view my cell centred data.
The figure here show difference between original and filtered (cell -> point) data, which is not pretty
You don’t have to display the interpolated field. You just need it to integrate the streamlines. You can still use the cell data from the original data for surface display slicing and such. Interpolating from cells to points changes the streamlines slightly also but not enough to worry about accuracy.
There are several seperate issues getting mixed up here I think, and thats probably my fault:
I’d like to be able to use the latest version(s) of paraview but I cant - due to my graphics driver being outdated it seems
the streamlines functionality is currently is not there for cell-centred octree data, apparently due to some fault with the “interpolator with cell locator”.
I do need to be able to view cell-centred data in v5.0 (like I can do in v3 and v4) but currently not able to do this in v5, without using Cell data to point data filter, which defeats the object of viewing cell data.
At the moment I will have to stick with Paraview v3 or v4 because they are least problematic.