[Help] Need contributors for 'Onboarding FEM Devs' wiki page

[johnwang]

This branch is rebased on a regular basis on master and thus updatodate. I even merge new development inside the history of femoofem to keep this branch uptodate.

Why not release it into the master?

[bernd]

This branch is rebased on a regular basis on master and thus updatodate. I even merge new development inside the history of femoofem to keep this branch uptodate.

Why not release it into the master?

There is noone who uses it. It has started with lots of interest and ended as my playground. But mainly you are right. Why keeping it on my github and do rebase and rebase it. Since it even has unit test it would keep working even on code changes ...

[Kunda1]

But mainly you are right. Why keeping it on my github and do rebase and rebase it. Since it even has unit test it would keep working even on code changes ...

You can label it experimental or even make it hidden by default via the FEM preferences?

[johnwang]

another helpful information.

A new solver mainly needs the following small steps ...

- mesh exporter
- results importer
- solver object (needs changes in solver settings, unit tests, ObjectsFem modules as well)
- task and writer module (here is where the main solver input writing happens)
- Gui tool to create a solver
- Gui preference tab to set the solver binary path
- a solver input writing unit test. Best to take the ccx cantilever. This is available for all mesh element types
- having one or two beers

Add_FEM_Solver_Tutorial

[johnwang]

There is noone who uses it. It has started with lots of interest and ended as my playground. But mainly you are right. Why keeping it on my github and do rebase and rebase it. Since it even has unit test it would keep working even on code changes ...

Hard for people to compile your branch to test it. If it is ready to use in master, maybe more will try.

Since FC can't support hundreds of solver, maybe introduce a mod/fem/femsolver/3rdParty folder. The GUI part is all done by FreeCAD, each solver just needs to make their own solver.py,writer.py,tasks.py and anything else needed. Only Python is needed. They can make their own package to connect with FreeCAD. If a user want to test oofem, he can copy oofem package into that folder. So to Frame3DD. To FreeCAD, they are all 3rdParty solver. Same one button.

[bernd]

Actually it is exactly how it works ATM. Compiling is only needed for the preferences page, the too bar as well as the menu enty. These are for historical reason made in C++ in FEM.

Means if you copy all FEM directory from femoofem branch you can set up a oofem example with the gui and thus you even have the solver without a python command.

[bernd]

... To FreeCAD, they are all 3rdParty solver. Same one button.

I like this idea. We do not make a button menu for each solver, we have a 3rd party solver button and this can be linked with a preference to a method in pythons FEM comands module where all the solver are. This way it would not matter if a 3rd party solver is in main sources or a module like the japanese one Front something ...

All I need would be some days with 48 hours ...

[Kunda1]

All I need would be some days with 48 hours ...

[johnwang]

I like this idea. We do not make a button menu for each solver, we have a 3rd party solver button and this can be linked with a preference to a method in pythons FEM comands module where all the solver are.

Use the preferences page to switch 3rd party solver. Under solver folder, there could be oofem and frame3dd folder. No need to be only one 3rdparty folder.
Or the oofem and frame3dd folder all put under 3rdparty folder.

[johnwang]

Means if you copy all FEM directory from femoofem branch you can set up a oofem example with the gui and thus you even have the solver without a python command.

I'll try only copy https://github.com/berndhahnebach/FreeC ... lver/oofem

Edit:
also need this file: https://raw.githubusercontent.com/bernd ... femMesh.py