When doing slices and clipping of 3D meshes (specially unstructured meshes), when one turns on the surface with edges representation. paraview shows a lot of parasite edges that are not there in reality, an example of this behavior (cylinder mesh generated by snappyHexMesh from OpenFOAM library):
the issue (specially for new commers) is that one thinks there are this edges in the mesh and thinks ‘something went wrong’, where this are artifacts from cliping/slicing, if one sets to crinkle view this issue is not shown:
Ideally it would be nice to not have this parasite projected edges that they prompt to confusion, even in non crinkle version but I think this would be a lot of work (and not evident on ‘how to’ implement it) nevertheless simply having crinkle by default would be better…
also same mesh (with same clip) but from a normal view with 2D representation:
I think this is domain specific, and hard to find a default that will match all use cases, that’s also why ParaView can store custom default properties.
That said, if you consider that those edges should not be there at all, we may investigate why they show up
I think this is domain specific, and hard to find a default that will match all use cases, that’s also why ParaView can store custom default properties.
I fully agree with you! and on or off it will be more suited for one or the other, nevertheless the crinkle would not ‘look’ like there is an issue on the mesh for any application where on the other way around yes… and
That said, if you consider that those edges should not be there at all, we may investigate why they show up
oh for sure they should not show up, I am guessing it is from some form of projection of the other nodes of the cells where the plane is cutting them, it creates this ‘phantom’ edges that are not supposed to be there and a lot of people thinks there is an issue (reason of asking the default behavior, as people that knows about overwrite the default value). if the lines are removed and we can keep the ‘not crinkle view’ this would be even better but not sure how complex this would be.
FYI, this comes quite ofter:
@nicolas.vuaille do not hesitate if a mesh to test this would help, i can provide one. also if necessary i can make an issue (but i guess there is a lost somewhere issue already created for this, i remember asking personally about this a bunch of years ago while doing my phd)
regards
