In examples/large_deformation/hyperelastic.py a rotation by displacements is applied. By using a similar function the vectors defining the force couples could be defined for dw_surface_ltr (IMHO). Does it make sense?
----- Reply message -----
From: "Andre Smit" <freev...(a)gmail.com>
Date: Sat, Dec 18, 2010 05:10
What is the best way to apply a torque load to a model?
You received this message because you are subscribed to the Google Groups "sfepy-devel" group.
To post to this group, send email to sfepy...(a)googlegroups.com.
To unsubscribe from this group, send email to sfepy-devel...(a)googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
I am currrently looking for FEM packages to help me solve a system of
beams and columns, basically a collection of 1D bernoulli/timoshenko
I started reading SfePy docs and i am getting the idea that doing the
above is not really possible here, am i right?
Are only 2D area elements permitted in SfePy?
Or is there any direct support for solving 1D line elements too..
FYI: As SciPy 0.12.0 is out and one of the release highlights is "Support for
Python 2 and Python 3 from the same code base (no more 2to3)", we can think
seriously about updating SfePy in this respect as well, cf. .
I'm trying to use Sfepy in a Doctest example. It would be nice to turn
off Sfepy output to reduce the noise in the Docs. The code I'm using
I've managed to turn off most of the output using
goptions['verbose'] = False
gen_block_mesh((Lx, Ly), shape, center, verbose=False)
Unfortunately, the following still remains
sfepy: matrix shape: (199, 199)
sfepy: assembling matrix graph...
sfepy: ...done in 0.00 s
sfepy: matrix structural nonzeros: 5631 (1.42e-01% fill)
I can't figure out how to turn off the above four lines. Any ideas?
I've just been browsing through the Sfepy website and investigating its
use. I wandered onto the fish heart section and tried to download the pdf
thesis at the bottom of the page but it keeps timing out (so does the
link). Is there an alternative link for its download or alternative way to
I noticed that the name "Domain" has changed to "FEDomain".
While this is probably a change for the better, I would recommend
being very cautious about such changes. For example, it breaks code
that I'm hoping to package and release at some stage. This seems to be
an API change and Sfepy probably needs a policy for this. Maybe some
discussion on the mailing list for example. In traditional release
models with X.Y.Z release numbers, this would probably require
changing the X value. I realize that Sfepy has rolling releases which
is fine, but similar caution should probably be employed.
Perhaps it is a bit overkill but I am interested in using finite elements
methods to solve systems of non-linear ODEs with complicated boundary
conditions. Can SfePy be used to accomplish this?
I am pleased to announce release 2014.2 of SfePy.
SfePy (simple finite elements in Python) is a software for solving
systems of coupled partial differential equations by the finite element
method. The code is based on NumPy and SciPy packages. It is distributed
under the new BSD license.
This release brings a preliminary support for isogeometric analysis - a
recently developed computational approach that allows using the NURBS-based
domain description from CAD design tools also for approximation purposes
similar to the finite element method.
Home page: http://sfepy.org
Mailing list: http://groups.google.com/group/sfepy-devel
Git (source) repository, issue tracker, wiki: http://github.com/sfepy
Highlights of this release
- preliminary support for isogeometric analysis
- improved post-processing and visualization script for time-dependent problems
with adaptive time steps
- three new terms
For full release notes see http://docs.sfepy.org/doc/release_notes.html#id1
(rather long and technical).
Robert Cimrman and Contributors (*)
(*) Contributors to this release (alphabetical order):
I try to simulate laminar flow in microfluidics (for now I just use a
simple cube), in order to do this I tried to modify the definition file for
the Navier_stokes example and creat my own mesh with GMSH.
I saved the mesh file as m3d.mesh, removed the triangles and the edges and
used the command /script/convert_mesh.py meshes/3d/m3d.mesh
meshes/3d/micro3d.mesh -r2 in order to produce a "useable" mesh.
Nevertheless when running simple.py with my definition file I receive the
following error message:
Sfepy: creating regions...
parsing failed : nodes in x>1.99999)
...pyparsing.ParseException: Expected ''all'' ( at char 0),( line:1, col: 1)
I am not really a computer scientist but I guess that the problems comes
from the mesh or the way I define my outlet region.
If someone as any idea how I could fix my script I would be really happy