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. .
Dear SfePy users,
Is it possible to evaluate a solution not only in the FEM mesh node, but in
any arbitrary point in the domain with the given (x, y, z) coordinates?
For example, consider Dirichlet problem for Poisson equation. We apply
essential boundary conditions on the surface nodes and after the problem
has been solved we have the solution vector, i.e. vector of values in the
FEM mesh nodes. But I want to know the solution in point v(x, y, z) that is
not FEM mesh node. What is the best way to obtain solution in this point v?
I am pleased to announce release 2014.1 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.
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
- sfepy.fem was split to separate FEM-specific and general modules
- lower memory usage by creating active DOF connectivities directly from field
- new handling of field and variable shapes
- clean up: many obsolete modules were removed, all module names follow naming
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):
Vladimír Lukeš, Matyáš Novák, Jaroslav Vondřejc
several important changes for users of "SfePy as a library to build apps" will
be in the next release of SfePy (to be soon) and are already in the master
repository. Those are:
1. sfepy.fem has been reorganized and split into code that is discretization
method independent (now in sfepy.discrete and sfepy.discrete.common) and FEM
specific (now in sfepy.discrete.fem).
2. all source files in the repository now use the same naming conventions (no
more thisStyle.py modules, only this_style.py).
3. isfepy was removed, see the docs for an advice how to setup ipython for the
4. a number of unused/underused modules were removed.
If you have any feedback, do not hesitate to post.
FYI: I am going to remove the isfepy ipython-based shell from sfepy, as it has
not much value over plain ipython. An information will be added to the docs
saying what to put into an ipython startup file to get the same functionality.
I recently cloned the source from github and all the tests passed. I am
trying to run posproc.py on cylinder.vtk and it results in the following
python2 postproc.py cylinder.vtk
Traceback (most recent call last):
File "postproc.py", line 42, in <module>
from sfepy.postprocess import Viewer, get_data_ranges,
File "/mysrc/sfepy/sfepy/postprocess/__init__.py", line 1, in <module>
from viewer import Viewer, ViewerGUI
File "/mysrc/sfepy/sfepy/postprocess/viewer.py", line 19, in <module>
from traitsui.api \
File "/usr/lib/python2.7/site-packages/traitsui/api.py", line 35, in
from .editors.api import (ArrayEditor, BooleanEditor, ButtonEditor,
line 22, in <module>
from .api import (toolkit, ArrayEditor, BooleanEditor, ButtonEditor,
File "/usr/lib/python2.7/site-packages/traitsui/editors/api.py", line 10,
from .code_editor import CodeEditor
line 36, in <module>
class ToolkitEditorFactory ( EditorFactory ):
line 48, in ToolkitEditorFactory
mark_color = Color( 0xECE9D8 )
File "/usr/lib/python2.7/site-packages/traits/traits.py", line 487, in
return self.maker_function( *args, **metadata )
File "/usr/lib/python2.7/site-packages/traits/traits.py", line 1191, in
return ColorTrait( *args, **metadata )
File "/usr/lib/python2.7/site-packages/traitsui/toolkit_traits.py", line
7, in ColorTrait
return toolkit().color_trait( *args, **traits )
File "/usr/lib/python2.7/site-packages/traitsui/toolkit.py", line 117, in
_toolkit = _import_toolkit( toolkit_name )
File "/usr/lib/python2.7/site-packages/traitsui/toolkit.py", line 51, in
return __import__( name, globals=globals(), level=1 ).toolkit
File "/usr/lib/python2.7/site-packages/traitsui/wx/__init__.py", line 26,
File "/usr/lib/python2.7/site-packages/traitsui/wx/toolkit.py", line 55,
from pyface.wx.drag_and_drop \
File "/usr/lib/python2.7/site-packages/pyface/wx/drag_and_drop.py", line
21, in <module>
File "/usr/lib/python2.7/site-packages/wxversion.py", line 144, in select
raise AlreadyImportedError("wxversion.select() must be called before
wxPython is imported")
wxversion.AlreadyImportedError: wxversion.select() must be called before
wxPython is imported