OOFem
Moderator: bernd
Forum rules
and Helpful information for the FEM forum
and Helpful information for the FEM forum
Re: OOFem
This remindes me, I should add the oofem examples to the new examples gui we implemented during GSOC.
Re: OOFem
Hey bernd, good idea! Lets track these FEM side-projects a little more closely so we can keep track of all of them and what their progress is. FreeCAD is giving opensource FEM an amazing platform and publicity.
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
-
- Posts: 3
- Joined: Thu Mar 21, 2019 9:54 am
Re: OOFem
Hi, thanks for the quick answers.
I was able to compile FreeCAD and create a simple 3d mesh.
I got just one error when trying to run OOFEM, the error was related to time.clock() (in writer.py) since I am using python 3.8.2; that was an easy fix.
Otherwise, the analysis runs fine; however, the results are all zero. When I check the OOFEM input file, the nodal load is missing. I prescribed the force using ContstraintForce and I can see the arrows in the modeler. Note that the Dirichlet BCs are present.
Do you have any idea where the problem can be?
I am definitely going to dive deeper into the tool. My goal is to work on the OOFEM part and improve it. Do you have any suggestions on what should be done first, i.e., what is present already for other solvers, but not for OOFEM?
I was able to compile FreeCAD and create a simple 3d mesh.
I got just one error when trying to run OOFEM, the error was related to time.clock() (in writer.py) since I am using python 3.8.2; that was an easy fix.
Otherwise, the analysis runs fine; however, the results are all zero. When I check the OOFEM input file, the nodal load is missing. I prescribed the force using ContstraintForce and I can see the arrows in the modeler. Note that the Dirichlet BCs are present.
Do you have any idea where the problem can be?
I am definitely going to dive deeper into the tool. My goal is to work on the OOFEM part and improve it. Do you have any suggestions on what should be done first, i.e., what is present already for other solvers, but not for OOFEM?
Re: OOFem
very good news.
There are some examples. These should give results.
- https://github.com/berndhahnebach/FreeC ... s2d.py#L30 and
- and the standard ccx cantilever
- a unit test can be run. see https://github.com/berndhahnebach/FreeC ... #L166-L169 the commands to set up the example can be found in the module test_solver_oofem.py the FreeCAD files will be save in tmp folder
There are some examples. These should give results.
- https://github.com/berndhahnebach/FreeC ... s2d.py#L30 and
- and the standard ccx cantilever
- a unit test can be run. see https://github.com/berndhahnebach/FreeC ... #L166-L169 the commands to set up the example can be found in the module test_solver_oofem.py the FreeCAD files will be save in tmp folder
Re: OOFem
- displacements constraints: https://github.com/berndhahnebach/FreeC ... er.py#L536
- fixed constraints: https://github.com/berndhahnebach/FreeC ... er.py#L641
- force constraints: on nodes: https://github.com/berndhahnebach/FreeC ... er.py#L695
no other constraints are supported ATM
- fixed constraints: https://github.com/berndhahnebach/FreeC ... er.py#L641
- force constraints: on nodes: https://github.com/berndhahnebach/FreeC ... er.py#L695
no other constraints are supported ATM
Re: OOFem
would you make a PR to https://github.com/berndhahnebach/FreeC ... s/femoofemnitramkaroh wrote: ↑Fri Sep 25, 2020 12:35 pm ... I got just one error when trying to run OOFEM, the error was related to time.clock() (in writer.py) since I am using python 3.8.2; that was an easy fix. ...
Re: OOFem
see the examples in femexamples what works for other solver ccx and elmer.nitramkaroh wrote: ↑Fri Sep 25, 2020 12:35 pm I am definitely going to dive deeper into the tool. My goal is to work on the OOFEM part and improve it. Do you have any suggestions on what should be done first, i.e., what is present already for other solvers, but not for OOFEM?
Mhh what should be done next ... ATM only tet4, tet10 and quad4 meshes are supported. Extending this would be great. https://github.com/berndhahnebach/FreeC ... sh.py#L178
Ahh the main reason to start oofem was the support of real beam elements. The idea was to have a solver to solve mixed beam and shell analysis as they are used in structural engineering analysis of concrete buildings.
Re: OOFem
How to Export to VTK format? Thanks.nitramkaroh wrote: ↑Thu Mar 21, 2019 10:06 am Hi guys, I am one of OOFEM developers and the integration of OOFEM into FreeCAD is really great. If you need any help with OOFEM input file structure or anything else I would be happy to help.
Re: OOFem
What would you like to export to vtk format?
Re: OOFem
http://www.oofem.org/en/features
says:
Postprocessing:
Export to VTK format is supported, allowing to use VTK based visualization tools (such as MayaVi or ParaView) for postprocessing on different platforms
I am just trying to figure it out how.