Moderator: bernd
ccx uses Abaqus inp file format. It is written here: https://github.com/berndhahnebach/FreeC ... ter.py#L82 The writer ist done in C++ see https://github.com/berndhahnebach/FreeC ... .cpp#L1185
Code: Select all
expath = '/home/hugo/Desktop/'
mesh = App.ActiveDocument.Box_Mesh.FemMesh
mesh.write(expath + 'mesh.inp')
mesh.write(expath + 'mesh.vtk')
mesh.write(expath + 'mesh.stl')
mesh.write(expath + 'mesh.unv')
Code: Select all
expath = '/home/hugo/Desktop/'
from feminout.importZ88Mesh import export as z88export
z88export([App.ActiveDocument.Box_Mesh], expath + 'mesh.txt')
similar to z88. They have a converter too. My first idea was use the converter, but than I realised to write an exporter just for nodes and tet10 elements is not difficult and just some lines of code. With this one can export lots of analysis already. All other element types where added step by step later on.HarryvL wrote: ↑Thu Nov 01, 2018 9:57 pmAFAIK the mesh information is typed in the input file in a connectivity format (global node numbers by element) unique to OOFEM. The developers make available a converter script (unv2oofem) that turns UNV files into OOFEM format, but going via UNV would be a roundabout way to get to the required result. Not sure this answers your question.
That's exactly the thought process I went through for OOFEMbernd wrote: ↑Fri Nov 02, 2018 6:23 amsimilar to z88. They have a converter too. My first idea was use the converter, but than I realised to write an exporter just for nodes and tet10 elements is not difficult and just some lines of code. With this one can export lots of analysis already. All other element types where added step by step later on.
cheers bernd