WorkFlows - 2019 - spring
Posted: 04 Mar 2019, 13:26
hi,
I had several year's break for useing ElmerFEM.
Elmer it self is at good condition but applications
before are at moment suffering "depency locks",
unsupported compatibelity,....
Salomè works fine, you can mesh whit netgen
and export as .unv You can name boundaries at
salome by setting group at mesh before export.
Salomè has add-one plugin that dose not support
current version, actually problem is at calling conevtions
of functions and I have "corrected" version for testing
- if there is time.
FreeCAD, has limitations at meshing. Only GMESH
works whit Elmerfem trough FEM WorkBench. You find at ElmerFEM workflows
python script helping batch prosessing.
You can export mesh as .unv but I did not find a way to
declare boundaries, give name for boundaries so I can
referense those at case.sif for elmer.
Whit 6.2 Netgen I get crash, floating point exeception,
it come's while writeing outstream.n < P.Z() so native
export won't work. Basically current netgen accept's
all format's in but could not find feasible way to get
those out. Could this be related used parameter
types int32/int64/int128 ??? At older versions
you could define those, at now I could not find
system in minutes,...
This is pitty due Netgen dose good work and
timely manner whit large net's,... I got 6.2 Netgen
work whit FreeCAD,... just turn off OCC and python.
To get Netgen accept your own compilation of OCE
you should have empty build directory and pass
OCE directories correctly,... all other flags as well,
there must be mistake at Netgen cmake files,...
Salomè is immune to depencyes but Elmer / FreeCAD
/Negen are NOT!
========================================
OCC / OCE causes conflict between FreeCAD / Netgen
Python3 work's both FreeCAD 0.18 (2 or 3) and Netgen 6.2 (must be 3)
Incorrect OCC libraryes causes error messages hard to trace
time to time.
I like to get commnets if you know better, I lost several day's
to learn all these,...
It's not enough just to cmake cmake-gui ldd and compare,....
...
Also there is lot of libraryes that are depend eighter OCC or python.
So wheter I need a all applications build from sources at one directory
shared at my cluster or do I use native ubuntu 18.04 packaging ???
I'am about create mpi4you package,... it's also time consuming,...
I had several year's break for useing ElmerFEM.
Elmer it self is at good condition but applications
before are at moment suffering "depency locks",
unsupported compatibelity,....
Salomè works fine, you can mesh whit netgen
and export as .unv You can name boundaries at
salome by setting group at mesh before export.
Salomè has add-one plugin that dose not support
current version, actually problem is at calling conevtions
of functions and I have "corrected" version for testing
- if there is time.
FreeCAD, has limitations at meshing. Only GMESH
works whit Elmerfem trough FEM WorkBench. You find at ElmerFEM workflows
python script helping batch prosessing.
You can export mesh as .unv but I did not find a way to
declare boundaries, give name for boundaries so I can
referense those at case.sif for elmer.
Whit 6.2 Netgen I get crash, floating point exeception,
it come's while writeing outstream.n < P.Z() so native
export won't work. Basically current netgen accept's
all format's in but could not find feasible way to get
those out. Could this be related used parameter
types int32/int64/int128 ??? At older versions
you could define those, at now I could not find
system in minutes,...
This is pitty due Netgen dose good work and
timely manner whit large net's,... I got 6.2 Netgen
work whit FreeCAD,... just turn off OCC and python.
To get Netgen accept your own compilation of OCE
you should have empty build directory and pass
OCE directories correctly,... all other flags as well,
there must be mistake at Netgen cmake files,...
Salomè is immune to depencyes but Elmer / FreeCAD
/Negen are NOT!
========================================
OCC / OCE causes conflict between FreeCAD / Netgen
Python3 work's both FreeCAD 0.18 (2 or 3) and Netgen 6.2 (must be 3)
Incorrect OCC libraryes causes error messages hard to trace
time to time.
I like to get commnets if you know better, I lost several day's
to learn all these,...
It's not enough just to cmake cmake-gui ldd and compare,....
...
Also there is lot of libraryes that are depend eighter OCC or python.
So wheter I need a all applications build from sources at one directory
shared at my cluster or do I use native ubuntu 18.04 packaging ???
I'am about create mpi4you package,... it's also time consuming,...