SfePy December 2008

sfepy@python.org

3 participants
4 discussions

Coupled Thermal-Electrical problem
by bosman 06 Jan '09

06 Jan '09

Hi! I got a question how to go about setting up a coupled Thermal- Electrical problem, where the heating comes from the Joule heating of a electrically conductive part. The properties are temperature dependent. Is there some similar example? PS! Robert, We met at EuroScipy and I only now got around to join the list.

3 14

git repository
by Robert Cimrman 18 Dec '08

18 Dec '08

Hi, we have just switched out source code management system from mercurial to git [1]. See [2] for information on git features and how it compares to mercurial (or, how it is superior in most aspects :). [1] http://code.google.com/p/sfepy/wiki/Downloads [2] http://wiki.sympy.org/wiki/Git_hg_rosetta_stone cheers, r.

1 0

ANN: SfePy 2008.4
by Robert Cimrman 04 Dec '08

04 Dec '08

I am pleased to announce the release of SfePy 2008.4. SfePy (simple finite elements in Python) is a finite element analysis software based primarily on Numpy and SciPy. Mailing lists, issue tracking, mercurial repository: http://sfepy.org Home page: http://sfepy.kme.zcu.cz Major improvements: - framework for running parametric studies - greatly improved support for time-dependent problems - time derivatives of variables as term arguments - initial conditions via ics, ic_<number> keywords - live plotting using multiprocessing module - type of term arguments determined fully at run-time - new terms, namely piezo-coupling Applications: - enhanced acoustic band gaps code - dispersion analysis (polarization angle calculation) - applied load tensor computation - phase velocity computation for periodic perforated media with empty holes - improved schroedinger.py - plotting DFT iterations For more information on this release, see http://sfepy.googlecode.com/svn/web/releases/2008.4_RELEASE_NOTES.txt Best regards, Robert Cimrman

1 0

release numbering
by Robert Cimrman 02 Dec '08

02 Dec '08

Hi all, we are going to replace the current rather ad-hoc numbering of sfepy releases to something more reasonable. To take part in the discussion, post a comment at [1], please. A new release (with some nice new functionality) is imminent - just the numbering should be resolved. Best regards, r. [1] http://code.google.com/p/sfepy/issues/detail?id=64

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

SfePy December 2008