FreeCADI plan on contacting one of the main authors of OpenSees soon to inquire about the possibility of a license change.
Moderator: bernd
I plan on contacting one of the main authors of OpenSees soon to inquire about the possibility of a license change.
I think it has licensing issue for commercial purpose. look this, you can understand it more than me surely.
added Felt to the list of interesting solvers FEM_Solverhardeeprai wrote: ↑Mon Nov 12, 2018 4:54 pmIs any current solver used through FEM workbench has 1D beam element to do plane and frame analysis (which is most commonly used for structural analysis of Steel and Reinforced Concrete frames). I am thinking to use FElt for this purpose.
https://github.com/Sudhanshu-Dubey14/felt
which is an effort to make it to run on latest compilers and hardware.
Original FElt is at: http://felt.sourceforge.net/
Hello @bernd. If we want to implement OpenSees, I think we must convert geometry, boundary conditions, loads, materials , etc to proper OpenSees .tcl file or in newer version to *.py. Is it correct?bernd wrote: ↑Tue Nov 13, 2018 6:09 amadded Felt to the list of interesting solvers FEM_Solverhardeeprai wrote: ↑Mon Nov 12, 2018 4:54 pmIs any current solver used through FEM workbench has 1D beam element to do plane and frame analysis (which is most commonly used for structural analysis of Steel and Reinforced Concrete frames). I am thinking to use FElt for this purpose.
https://github.com/Sudhanshu-Dubey14/felt
which is an effort to make it to run on latest compilers and hardware.
Original FElt is at: http://felt.sourceforge.net/
exact. It is the way Elmer, Z88 and CalculiX solver work.ebrahim raeyat wrote: ↑Tue Nov 13, 2018 7:59 amHello @bernd. If we want to implement OpenSees, I think we must convert geometry, boundary conditions, loads, materials , etc to proper OpenSees .tcl file or in newer version to *.py. Is it correct?
excelant! if you find some overview of xc, please share it here. one question:bernd wrote: ↑Tue Nov 13, 2018 8:47 amexact. It is the way Elmer, Z88 and CalculiX solver work.ebrahim raeyat wrote: ↑Tue Nov 13, 2018 7:59 amHello @bernd. If we want to implement OpenSees, I think we must convert geometry, boundary conditions, loads, materials , etc to proper OpenSees .tcl file or in newer version to *.py. Is it correct?
ATM it seams XC fits much more in my needs than OpenSees. Thus I will go for XC. BTW, XC has an python interface already. ATM I'm still trying to get into XC before I gone start to write some code how to get data from FreeCAD to XC.
bernd
xc is based on opensees code basis with lots of enhancements. New features of opensees are ported to xc, but features of xc are not pushed upstream into opensees. See https://github.com/xcfem/xc/issues/46ebrahim raeyat wrote: ↑Tue Nov 13, 2018 9:12 am... one question:
how xc uses opensees and when, do you know?
thanks, that was very interesting.bernd wrote: ↑Tue Nov 13, 2018 10:47 amxc is based on opensees code basis with lots of enhancements. New features of opensees are ported to xc, but features of xc are not pushed upstream into opensees. See https://github.com/xcfem/xc/issues/46ebrahim raeyat wrote: ↑Tue Nov 13, 2018 9:12 am... one question:
how xc uses opensees and when, do you know?
If you are registered student, then you might think of makinhttps://summerofcode.withgoogle.com/archive/2017/projects/6536382147198976/g it GSoC project, as well:hardeeprai wrote: ↑Sun Nov 11, 2018 2:08 pm
It will be better, if you make project outline.
Project's objectives, what you have, where you wish to go, and what will be approach.
Do you need our input on your project? That will not be of great help, if we don't see that project overview.
Thanks a lot! It's very interestinghardeeprai wrote: ↑Fri Nov 16, 2018 1:11 pm
If you are registered student, then you might think of makinhttps://summerofcode.withgoogle.com/archive/2017/projects/6536382147198976/g it GSoC project, as well:
