You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the only way to get the .inp file with CalculiX analysis definition for external use is to enter the Solver job control, write the input deck, edit it, select the whole content (Ctrl+A) and copy it (Ctrl+C), then paste to a newly created text file whose extension should be changed to .inp (or save as .py macro and change extension to .inp). Quite tedious considering that there could be an option to use File --> Export (with Analysis container or CalculiX solver object or edited input file selected) for that.
For now, only the mesh can be exported to the .inp format.
Full version info
OS: Windows 10 build 19045
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.37358 (Git)
Build type: Release
Branch: main
Hash: 0e24e121eb3e5708c380596e0a9fd583befac977
Python 3.11.9, Qt 5.15.13, Coin 4.0.2, Vtk 9.2.6, OCC 7.7.2
Locale: Polish/Poland (pl_PL)
Subproject(s) affected?
FEM
Anything else?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem description
Currently, the only way to get the .inp file with CalculiX analysis definition for external use is to enter the Solver job control, write the input deck, edit it, select the whole content (Ctrl+A) and copy it (Ctrl+C), then paste to a newly created text file whose extension should be changed to .inp (or save as .py macro and change extension to .inp). Quite tedious considering that there could be an option to use File --> Export (with Analysis container or CalculiX solver object or edited input file selected) for that.
For now, only the mesh can be exported to the .inp format.
Full version info
Subproject(s) affected?
FEM
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: