Skip to content
Main SfePy repository
Python C Other
Latest commit f71404a May 12, 2016 @rc rc 2016.2: bump version number
Failed to load latest commit information.
doc 2016.2: update news May 12, 2016
examples update tolerance for solution without umfpack May 10, 2016
meshes add missing mesh - new meshes/elements/3_2_4_2.mesh May 3, 2016
script update examples, for changed variable names May 2, 2016
sfepy 2016.2: bump version number May 12, 2016
tests new examples/linear_elasticity/ + test May 2, 2016
.gitignore update .gitignore Oct 23, 2014
AUTHORS update AUTHORS Dec 1, 2015
INSTALL docs: update installation requirements - add scikit-umfpack Jul 10, 2015
LICENSE update years in LICENSE Apr 17, 2014 fix path in Sep 23, 2015
Makefile python ... via Makefile May 31, 2011
README update docs for no isfepy Feb 18, 2014
btrace_python started SfePy, based on sfe-release-00.35.01.tgz Dec 19, 2007 update build helper to clean *.pyd files (dynamic libs on… Jul 7, 2015 rename ProblemDefinition -> Problem Feb 20, 2014 clean up Nov 27, 2013 band_gaps_he: update required options Apr 2, 2012 new --colormap option Sep 3, 2015 rename ProblemDefinition -> Problem Feb 20, 2014 new flush() method in OutputFilter class - needed for multiprocessing Apr 12, 2016 update remove mesh generation options, simplify Apr 16, 2014 do not import setuptools for sdist command - fixes release … May 10, 2016
sfepy-run sfepy-run: update for no scripts-common/ symlinks, use explicit scrip… May 4, 2016 rename sfepy/optimize/ -> sfepy/optimize/ Feb 20, 2014 new --save-restart, --load-restart options Nov 18, 2015 support DEBUG_MESH flag in sfepy/fem/extmods/ May 20, 2013 update - new test to check presence of lines in the o… Apr 12, 2016


SfePy (Simple finite elements in Python)

A finite element analysis software based primarily on NumPy and SciPy.

See the INSTALL file for installation instructions or refer to SfePy
documentation site [1].

How to start

SfePy uses so called "problem definition files" (also referred to as
"input files" or "problem description files"") that describe the partial
differential equations (PDEs), boundary conditions, function spaces and
other ingredients of the finite element (FE) formulation of a
PDE-related problem, see [1]. The PDEs are given in weak formulation as
usual in the FE context, see [2], where each equation is composed of one
or more terms. To see which terms are available consult
'doc/sfepy_manual.pdf', or see them online [3].

In order to solve a problem, a problem description file has to be
created. There is also an interactive solution support for advanced
users [4].

When starting to solve a new problem, it is best to have a look at
example problem definition files in the 'examples/' directory - copy the
one that is similar to the problem at hand, and modify it. Two of the
examples are commented: 'examples/diffusion/' and

While a problem definition file describes a mathematical problem, it does not
contain a discretized solution domain (a FE mesh). The FE mesh must be provided
in another file in one of the supported formats, notably the legacy VTK format
[5]. SfePy does not provide meshing tools, but it can use a number of standard
formats. The results are almost exclusively stored in legacy VTK files, or
custom HDF5 files. Many standard open-source tools can be used to display the
VTK files, namely paraview [6], or mayavi [7]. The latter is supported directly
within SfePy, via the script.

Once an input file and a corresponding mesh file are prepared, the
solution of the problem can be attempted by the '' script, see
Examples section in the INSTALL file.



 - ... main SfePy development site (releases, mailing lists,
                        wiki, issue tracking, downloads, examples
 - ... documentation
 - ... master git repository
 - ... projects solved within SfePy

License: New BSD License, see the LICENSE file.

Robert Cimrman and Contributors
Something went wrong with that request. Please try again.