porting to smesh 8.3

Here's the place for discussion related to coding in FreeCAD, C++ or Python. Design, interfaces and structures.
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: porting to smesh 8.3

Post by bernd »

looo wrote: Thu May 03, 2018 3:38 pm the strange thing is that the unv file stores the mesh not in the order [1,2,3,4...10].
With the included smesh of FreeCAD:
1 7 3 6 2 5 8 10 9 4
(this order works)

with the external smesh 8.3:
1 3 2 4 7 6 5 8 10 9
which seems to be a wrong order

I wonder how the order is recrated in the working example. Is this done on SMESH side or on FreeCAD side?
unv is handled with Smesh only AFAIK

FreeCAD uses med for node ordering. UNV may be has different node order https://www.freecadweb.org/wiki/FEM_Element_Types But this is all handled by smesh.
User avatar
looo
Veteran
Posts: 3941
Joined: Mon Nov 11, 2013 5:29 pm

Re: porting to smesh 8.3

Post by looo »

from other topic:
bernd wrote:BTW: if loading unv is broken you are not able to load FreeCAD FEM meshes at all. FreeCAD FEM meshes are saved inside FCStd files as unv meshes. Just unzip an FCStd file with a FreeCAD FEM mesh to see the unv.
I guess only tetra10 elements are broken (second order volume elements)
bernd wrote:But this is all handled by smesh.
so this is a bug on smesh-side. :(
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: porting to smesh 8.3

Post by bernd »

looo wrote: Thu May 03, 2018 7:20 pm from other topic:
bernd wrote:BTW: if loading unv is broken you are not able to load FreeCAD FEM meshes at all. FreeCAD FEM meshes are saved inside FCStd files as unv meshes. Just unzip an FCStd file with a FreeCAD FEM mesh to see the unv.
I guess only tetra10 elements are broken (second order volume elements)
bernd wrote:But this is all handled by smesh.
so this is a bug on smesh-side. :(
Or it was a bug in Smesh and was fixed :shock:
User avatar
looo
Veteran
Posts: 3941
Joined: Mon Nov 11, 2013 5:29 pm

Re: porting to smesh 8.3

Post by looo »

hmm, if so you maybe remember problems looking like this:
nasty_mesh.png
nasty_mesh.png (46.2 KiB) Viewed 840 times
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: porting to smesh 8.3

Post by bernd »

yeah, I remember when vejmarie updated smesh we had such problems too !!! we should check his commits, and may be the commits inside the internal smesh code ...
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: porting to smesh 8.3

Post by bernd »

only 45 commits, lots of them not related to smesh but step instead ... https://github.com/FreeCAD/FreeCAD/comm ... r=vejmarie

example: https://github.com/FreeCAD/FreeCAD/comm ... eddb3932e6 I do not know if it is still needed ...


all started here: https://github.com/FreeCAD/FreeCAD/commit/666a3e5a
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: porting to smesh 8.3

Post by bernd »

May be this topic helps too. https://forum.freecadweb.org/viewtopic.php?t=16312 HaHaHa dejavu :shock:
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: porting to smesh 8.3

Post by bernd »

Have you tried this Python code ... https://www.freecadweb.org/wiki/FEM_Mes ... ement_Type run the code, save the file, load the file, I wonder which of the elements is broken.
User avatar
looo
Veteran
Posts: 3941
Joined: Mon Nov 11, 2013 5:29 pm

Re: porting to smesh 8.3

Post by looo »

very good catch!!! I have some hope again.
Attachments
elements.png
elements.png (13.79 KiB) Viewed 820 times
Post Reply