New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEM: Added read nastran95 inp file ability in FemMesh.cpp #4009
Conversation
@ceanwang why did you close it ? |
Seems nothing is happening. I give up. |
@berndhahnebach ping |
have some patience. I am really busy ... christmas time is familly time ... Furthermore there are some dead lines in my daily job before christmas ... |
@berndhahnebach any idea at what point you'll have time to address this PR ? |
I have merged it now. It's a bit weird that the same file extension (.inp) is used for Abaqus and Nastran-95 files. The difficulty of this PR was that it doesn't handle both formats at the same time but basically disabled the Abaqus support. So, I solved it this way: if an inp file is given then FreeCAD first tries the Abaqus importer and if afterwards the mesh is empty (i.e. it has no nodes) the Nastran-95 imported is used. Btw, here is a link to a file that can be used for testing: https://forum.freecadweb.org/viewtopic.php?f=18&t=39234&start=10#p412743 |
Thanks.
The question was raised in the forum, but no input. I was thinking a FEM WB setting to choose which importer to use for inp extension: https://forum.freecadweb.org/viewtopic.php?f=18&t=51569&start=10#p443787
Abaqus must copied Nastran. It’s good FC can support a Free and open source one.
|
BTW: this was the reason I did not merge it myself earlier. |
Forum talk at here https://forum.freecadweb.org/viewtopic.php?f=18&t=51569