porting to smesh 8.3
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: porting to smesh 8.3
Thanks, so compiling smesh with libmed won't solve the issues I had with netgen and mefisto... But anyway I will try to convince pyocct to include libmed for the next release.
Re: porting to smesh 8.3
thanks for this hint. After inclusion of these commits, netgen and mefisto seem to work again.bernd wrote:related commits:
I created a PR to get some feedback about the diff [1]. The remaining problem is the backward compatibility... But maybe someone else can have a look at this. Also I think it wouldn't be the worst idea to only support the externalized smesh...
[1] https://github.com/FreeCAD/FreeCAD/pull/1407
Re: porting to smesh 8.3
Finally it seems like the basic tests are working...
Re: porting to smesh 8.3
that is awesome!
Re: porting to smesh 8.3
AFAIK to import and export med Mesh files. This was added from vejmarie. I do not know of someone else who ever talked about med file format.
bernd
Re: porting to smesh 8.3
yes, no crash anymore. This was related to a patch for netgen which was added for pyocct, but is not really necessary. I hope we can now share the sources/ dependencies with pyocct.
For netgen we still use a patch from the salome project:
https://github.com/conda-forge/netgen-f ... lome.patch
For netgen we still use a patch from the salome project:
https://github.com/conda-forge/netgen-f ... lome.patch
Re: porting to smesh 8.3
I post this here again:
the update to newer smesh8.3 breaks the unv import and gmsh-meshing tool (as it uses .unv import internally)
maybe this one will help?: https://github.com/FreeCAD/FreeCAD/comm ... 0d7cdd82f5
references:
https://forum.freecadweb.org/viewtopic. ... 80#p231430
the update to newer smesh8.3 breaks the unv import and gmsh-meshing tool (as it uses .unv import internally)
maybe this one will help?: https://github.com/FreeCAD/FreeCAD/comm ... 0d7cdd82f5
references:
https://forum.freecadweb.org/viewtopic. ... 80#p231430
Re: porting to smesh 8.3
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?
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?