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?
r.
----- Reply message -----
From: "Andre Smit" <freev...(a)gmail.com>
To: <sfepy...(a)googlegroups.com>
Subject: Torque
Date: Sat, Dec 18, 2010 05:10
What is the best way to apply a torque load to a model?
--
Andre
--
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.
Hi,
I have just updated the time stepping solvers in sfepy for interactive use, as
demonstrated in the new example [1]. For basic use, ignore the probing code -
the time stepper can be used as simply as:
tss = SimpleTimeSteppingSolver({'t0' : 0.0, 't1' : 100.0, 'n_step' : 11},
problem=problem)
tss.init_time()
for step, time, state in tss():
pass
r.
[1] http://sfepy.org/doc-devel/examples/diffusion/time_poisson_interactive.html
Dear Robert
I could overcome my previous problems of not having root privileges, so it
all worked up till the command:
./postproc.py cylinder.vtk
This echoed the below message:
Exception
In
/home/gmh/.local/lib/python2.7/site-packages/mayavi-4.4.4.dev0-py2.7-linux-x86_64.egg/mayavi/sources/vtk_xml_file_reader.py:86
AttributeError: 'AlgorithmOutput' object has no attribute 'point_data' (in
get_all_attributes)
Traceback (most recent call last):
File
"/home/gmh/.local/lib/python2.7/site-packages/traits-4.6.0.dev354-py2.7-linux-x86_64.egg/traits/trait_notifiers.py",
line 340, in __call__
self.handler( *args )
File "/home/gmh/sfepy/sfepy/postprocess/dataset_manager.py", line 177, in
_dataset_changed
self._assign_attribute.input = value
File
"/home/gmh/.local/lib/python2.7/site-packages/traits-4.6.0.dev354-py2.7-linux-x86_64.egg/traits/trait_handlers.py",
line 104, in _read_only
name, class_of( object ) )
TraitError: The 'input' trait of an AssignAttribute instance is 'read only'.
sfepy: point scalars t at [-0.05 -0.02 0. ]
sfepy: range: -2.00e+00 2.00e+00 l2 norm range: 1.06e-02 2.00e+00
No handlers could be found for logger "mayavi.core.common"
I'm using Python 2.7.8 if that's relevant to the current issue.
Thanks again
Cheers
I am trying to generate a mesh from geometry but it does not seem to be
working. Does anybody have experience with this option? I am attaching a
sample code.
I am pleased to announce release 2016.1 of SfePy.
Description
-----------
SfePy (simple finite elements in Python) is a software for solving systems of
coupled partial differential equations by the finite element method or by the
isogeometric analysis (preliminary support). 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
--------------------------
- major simplification of finite element field code
- automatic checking of shapes of term arguments
- improved mesh parametrization code and documentation
- support for fieldsplit preconditioners of PETSc
For full release notes see http://docs.sfepy.org/doc/release_notes.html#id1
(rather long and technical).
Best regards,
Robert Cimrman on behalf of the SfePy development team
---
Contributors to this release in alphabetical order:
Robert Cimrman
Vladimir Lukes
Hi sfepy users!
I have a bit of trouble with evaluating surface fluxes when using the
poisson equation.
I have a spherical shell geometry, where the inner shell surface and the
outer shell surface are kept at two different potentials.
There is spherical symmetry, so the flux should be equally distributed on
the surface faces of each shell.
Also, the total flux for the two surfaces should be the same, except for an
opposite sign.
After solving the PDE the main variable field, t, looks fine, there is a
1/r dependence as expected.
But when I evaluate the surface fluxes on either the inner or the outer
shell there are both positive
and negative fluxes per face. For each sphere there are two positive flux
regions and two negative
flux regions.
I checked my surface normals and they look as expected, i.e. parallel to a
vector from the origo to the face
on the outer surface, and antiparallel on the inner surface.
I use the call
Surfaces_flux=pb.evaluate('d_surface_flux.i.Surfaces(coef.val,t)',
mode='el_eval',verbose=False)
to evaluate the flux.
I hope that there is someone who can point out the obvious and easy-to-fix
mistake i made...
Best regards
- Bjarke Dalslet
FYI: I have realized that sfepy can do the explicit time-stepping (forward
Euler method) as in [1] just by replacing
# Backward Euler method for temperature evolution.
equations = {
'Temperature' :
"""dw_volume_dot.i.Omega( s, dT/dt )
+ dw_laplace.i.Omega( coef.val, s, T ) = 0"""
}
by
# Forward Euler method for temperature evolution.
equations = {
'Temperature' :
"""dw_volume_dot.i.Omega( s, dT/dt )
+ dw_laplace.i.Omega( coef.val, s, T[-1] ) = 0"""
}
That is why the (broken) 'ts.explicit' solver was removed - 'ts.simple' or
'ts.adaptive' can be used instead.
r.
[1] http://sfepy.org/doc-devel/examples/diffusion/time_poisson_explicit.html
FYI: Better late then never, I have created a new issue [1] to discuss a
possible new logo. Kudos to Serge-Étienne Parent for the two proposals from
December 2015!
r.
[1] https://github.com/sfepy/sfepy/issues/303
