Hi Mike,
You need to either generate the mesh using the simple mesh generators that are in the sfepy package (just block or cylinder meshes), or (most often) you need to provide a mesh file, created in advance in an external tool. Many open-source or commercial softwares can be used for meshing. The following formats are supported thanks to meshio package:
$ python3 script/convert_mesh.py -l a b sfepy: Supported readable mesh formats: sfepy: -------------------------------- sfepy: abaqus (.inp) sfepy: ansys (.cdb) sfepy: comsol (.txt) sfepy: exodus (['.ex2', '.e', '.exo']) sfepy: gambit (.neu) sfepy: gmsh (.msh) sfepy: gmsh-dg (.msh) sfepy: gmsh2-ascii (.msh) sfepy: gmsh2-binary (.msh) sfepy: gmsh4-ascii (.msh) sfepy: gmsh4-binary (.msh) sfepy: hdf5 (.h5) sfepy: hdf5-xdmf (.h5x) sfepy: hmascii (.hmascii) sfepy: med (.med) sfepy: medit (['.mesh', '.meshb']) sfepy: mesh3d (.mesh3d) sfepy: nastran (['.nas', '.fem', '.bdf']) sfepy: tetgen (['.node', '.ele']) sfepy: vtk (.vtk) sfepy: vtk-ascii (.vtk) sfepy: vtk-binary (.vtk) sfepy: vtu (.vtu) sfepy: xdmf (['.xmf', '.xdmf']) sfepy: xyz (.xyz) sfepy: sfepy: Supported writable mesh formats: sfepy: -------------------------------- sfepy: abaqus (.inp) sfepy: exodus (['.ex2', '.e', '.exo']) sfepy: gmsh (.msh) sfepy: gmsh-dg (.msh) sfepy: gmsh2-ascii (.msh) sfepy: gmsh2-binary (.msh) sfepy: gmsh4-ascii (.msh) sfepy: gmsh4-binary (.msh) sfepy: hdf5 (.h5) sfepy: hdf5-xdmf (.h5x) sfepy: med (.med) sfepy: medit (['.mesh', '.meshb']) sfepy: nastran (['.nas', '.fem', '.bdf']) sfepy: tetgen (['.node', '.ele']) sfepy: vtk (.vtk) sfepy: vtk-ascii (.vtk) sfepy: vtk-binary (.vtk) sfepy: vtu (.vtu) sfepy: xdmf (['.xmf', '.xdmf']) sfepy: xyz (.xyz)
Does it help?
r.
On 10. 12. 20 20:53, Michael Rizzo wrote:
Yea that one managed to work, and I made sure to change to the correct directory. I fact, it seems I had already done this, but I was unable to notice the importance of another error, which seems to relate to a mesh that is no longer available in the standard sfepy build: [image: image.png]
I am new to FEA, but I do have some experience using ANSYS, where we usually start with the geometry and then figure out the mesh. In this case it seems I am not familiar enough to understand how to setup the mesh at present.
Regards, Mike
On Wed, 9 Dec 2020 at 16:02, Robert Cimrman cimrman3@ntc.zcu.cz wrote:
OK, so is fish_heart.py in your working directory? And how did you install sfepy (which version)?
Anyway, maybe start with the example [1], which is up-to-date and simpler.
r.
[1] http://sfepy.org/doc-devel/examples/large_deformation-active_fibres.html
On 09. 12. 20 21:45, Michael Rizzo wrote:
Yea I am trying to use a module custom built by this other group for now. I am trying the way indicated in the manual:
[image: image.png]
I can also take a look at some more recent description files.
On Wed, 9 Dec 2020 at 15:32, Robert Cimrman cimrman3@ntc.zcu.cz wrote:
Can you post how you run the example module?
If it is the file from [1], note that it is already 10 years old, so it likely needs updating for current sfepy.
Regards, r.
[1] http://sfepy.org/fish_heart/
On 09. 12. 20 18:42, Michael Rizzo wrote:
Okay. I am working in colaboratory for now. I am able to pip install sfepy, but when I try to use a custom module I am running into path issues.
[image: image.png]
I have been able to append the module to path using sys.append, and I have also added the module to the examples folder. It seems like I may need to rebuild and run the make again, however.
I appreciated the assistance.
Regards, Mike
On Wed, 9 Dec 2020 at 11:44, Robert Cimrman cimrman3@ntc.zcu.cz wrote:
Hi Mike,
On 12/9/20 5:24 PM, Michael Rizzo wrote: > Hello SFE folk, > > I am new to development. Is this the appropriate contact for question > asking? If not, a redirect would be appreciated.
Yes, ask here!
Cheers, r.
> Regards, > Mike
SfePy mailing list -- sfepy@python.org To unsubscribe send an email to sfepy-leave@python.org https://mail.python.org/mailman3/lists/sfepy.python.org/ Member address: mdrizzzoh@gmail.com