I want to smooth my surface to receive a surface that is one face (to reduce vertices and edges) but I need that some part of the surface would be smooth but stay different faces from all the rest of the surface.
that is my surface after 0.5 smooth factor. in this factor, it becomes one face
the red circles are the places where I want to be different faces from the whole surface
I try to use a lower smooth factor but it becomes too many faces, and also try to use the smoothing effect…
it is very important to me to smooth the model - because I need to produce a simulation in the model and if it is composed of a lot of vertices, edges, and faces are impossible/ on the other hand I need some faces to be the input and output of the simulation.
have you any idea?
thank you for helping!!
Smoothing does not reduce number of cells (triangle faces). If you want to have less cells then you can use “Decimation” module.
However, if you want to do finite-element analysis then you need to convert the surface mesh to a volumetric mesh. The number of cells in the volumetric mesh mainly depends on the meshing algorithm and parameters and the number of triangles in the input surface mesh should not matter much.
You can use SegmentMesher extension to convert a segmentation to volumetric mesh.
thank you for your response!
in comsol (simulation software) when I use the smooth factor it has an influence on the number of faces, edges ex’. (perhaps the software convert it to volume mesh and in this conversion Occurs)
however, i understand that after that i will need also to reconvert to stl format?
and another question: when trying using TetGen i receive an error
" self-intersection was detected. Program stopped.
Hint: use -d option to detect all self-intersections.
Error: Command ‘tetgen.exe’ returned non-zero exit status 3."
do you know what is “-d option”?
The option appears to do exactly what the hint suggests in that:
-d Detects self-intersections of facets of the PLC.
although that appears to be the only detail offered on the matter in the documentation.
It might be more effective to address the problem at the source (quality of the segmentation) and you might consider e.g. editing the segmentation manually, or using morphological filters, to minimise the risk to run into such issues.