I think it is of practical value and a great learning experience for me on how to write Python and integrate it with FreeCAD using the FC API.
1) Maybe we should try square x-section rather than round. The shape doesn't matter too much. It's just a way to introduce an internal load.
+1 and +1HarryvL wrote: ↑Tue May 22, 2018 7:23 pm1) Maybe we should try square x-section rather than round. The shape doesn't matter too much. It's just a way to introduce an internal load.
2) We could try mixed meshes once it can handle embedding 1D or 2D elements in 3D. It would be ideal to model the cable as a string of 1D elements. Or even a 2 D strip would be a great simplification.
To be honest, I would like to integrate it in FreeCAD somehow. But it it run as a macro an integration will be posible with not such big effort.HarryvL wrote: ↑Tue May 22, 2018 7:12 pmI am now trying to clean importToolsFem.py up and write a Macro instead, starting from the one done by Mario52 some time ago for Inertial Properties. Once I've got that cracked I will publish it for review and testing. Main remaining learning points / challenges for me:
see github of old gmsh macro https://www.freecadweb.org/wiki/Macro_GMSH we used it before I made the gmsh object in FreeCAD. The macro should still work. Or use any other macro. There are dozens ...HarryvL wrote: ↑Tue May 22, 2018 7:12 pm1) How to create a user dialogue for input of some additional material parameters (e.g. fy for steel and Phi and fck for concrete. Also some display choices (like the number of Reinforcement Ratio values to display - discrete number rather than continues display).
have a look here https://forum.freecadweb.org/viewtopic.php?f=18&t=28788 for some Python code in the regard of result object. BTW, you can add any FEM object to the document and thus to the TreeView by importing module ObjectsFem and use it's make... methods See https://github.com/FreeCAD/FreeCAD/blob ... ectsFem.py You can even use your prefered name.
Mhh not at runtime, at least not in easy manner. We need to recode the result task panel and use a combo box. The combo box uses just all available result types. With this it is easy to add any kind of result type even at runtime.
You're right. No need to write a macro if this gets embedded into FC. So I gave up on this and decided to introduce 4 new parameters in _ViewProviderFemrsultMechanical.py so that I can select them in the User Defined Equation dialog box for now. After updating this, FemrsultMechanical.py and importToolsFem.py I can indeed produce the results via the ResultObject dialog.
I am glad I didn't give up. The change to FemVTKTools.cpp was really easy and the whole thing compiled and linked in under 5 minutes.