https://github.com/berndhahnebach/FreeC ... tress2D.in
line 18
OOFem
Moderator: bernd
Forum rules
and Helpful information for the FEM forum
and Helpful information for the FEM forum
Re: OOFem
FTFYbernd wrote: ↑Sat Sep 26, 2020 12:00 pm https://github.com/berndhahnebach/FreeC ... tress2D.in
line 18
https://github.com/berndhahnebach/FreeC ... s2D.in#L18
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
Re: OOFem
Sure but I have been on a mobile.
Re: OOFem
I did not compile and test the oofem branch for a long time. Just pushed some fixes. Unit tests and examples set up again.bernd wrote: ↑Fri Sep 25, 2020 7:00 pm 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
unit tests:
- https://github.com/berndhahnebach/FreeC ... nds.sh#L20
- https://github.com/berndhahnebach/FreeC ... #L105-L107
- https://github.com/berndhahnebach/FreeC ... r_oofem.py
examples:
- start FreeCAD
- change to FEM
- Menu utilities --> FEM examples
- in new task panel --> solvers --> oofem --> double click to set up
run oofem:
I have not oofem installed ATM, means I could not test if the examples still give the correct results.
Re: OOFem
https://github.com/berndhahnebach/FreeC ... a26052a120bernd wrote: ↑Fri Sep 25, 2020 7:08 pmwould 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
Thanks. All good.