What about the mesh?
Moderator: bernd
Forum rules
and Helpful information for the FEM forum
and Helpful information for the FEM forum
-
- Veteran
- Posts: 3158
- Joined: Sat May 20, 2017 12:06 pm
- Location: Germany
What about the mesh?
At this moment we have 5 different meshers for FEM/CFD:
FEM: gmsh, netgen
CFD: gmsh, snappyhexmesh, cfmesh (used for openfoam)
The FEM/CFD results depend on the mesh-quality.
Is that right?
In my opinion snappyhexmesh is the best mesher.
For CFD.
And FEM?
netgen.
FEM: gmsh, netgen
CFD: gmsh, snappyhexmesh, cfmesh (used for openfoam)
The FEM/CFD results depend on the mesh-quality.
Is that right?
In my opinion snappyhexmesh is the best mesher.
For CFD.
And FEM?
netgen.
Re: What about the mesh?
Normally Netgen gives better meshes than GMSH, but we do support fairly more options for GMSH.
Would be cool if we could snappyHexMesh somehow integrte in FEM to use it for FEM!
bernd
Would be cool if we could snappyHexMesh somehow integrte in FEM to use it for FEM!
bernd
Re: What about the mesh?
What is the reason we have better support for GMSH?
More easy to integrate?
In my experiance (that's not that much) GMSH fails faster on more complex models(stp files). It don't generate volumes.
Netgen accapt more but take ages with the finer default values and i have no clue what changed.
More easy to integrate?
In my experiance (that's not that much) GMSH fails faster on more complex models(stp files). It don't generate volumes.
Netgen accapt more but take ages with the finer default values and i have no clue what changed.
Re: What about the mesh?
all gmsh is done in Python whereas all Netgen needs to be done in C++. My knowledge of Python is just much better than my knowledge of Netgen (at the time of writing gmsh object the knowledge difference was even bigger than it is nowadays).
Bernd
Bernd
Re: What about the mesh?
Check thanks for you're replay
Re: What about the mesh?
These days I would probably directly go for improving Netgen. It is on my ToDo, but the list is so long and improving Netgen is not far on top of the list ATM ...
Re: What about the mesh?
boa this is very difficult since it changes. On top is for sure fixing bugs if they encounter. Since all is done in spare time, and I do not use FreeCAD FEM i daily business usage (only from time to time I really use FreeCAD FEM at work) this changes depending on time and on the what others do. As an example since you have started the oofem implementation I have started to think about changes in the solver frame work I have in mind for a long time. Another one are the file headers. They are different in most FEM Python modules but I never started to do anything in this regard. Luzpaz started this by a PR on my repo and thus this jumped from far away to be on top of my TODO. Actually it is what I'm on ATM See https://github.com/berndhahnebach/FreeCAD_bhb/pull/48
... I try to define a list of my ideas later on ... I really like to say ideas what I would like to implement ...
bernd
... I try to define a list of my ideas later on ... I really like to say ideas what I would like to implement ...
bernd
Re: What about the mesh?
Python 3 should also close to the top...
but that one have its own topic
but that one have its own topic