Mailman 3 - SfePy - python.org

meshpy
by Robert Cimrman 19 Sep '08

19 Sep '08

Hi, I have just come around an interesting piece of software: http://mathema.tician.de/software/meshpy Has anybody some experience with it? r.

3 7

dft.c
by osman 07 Sep '08

07 Sep '08

Robert, Ondrej, how about f2c to turn dft.f into dft.c you just need f2c.h. I just edited the .f file, moved the integer declaration to above the "data" statement and ran f2c. gcc -o dft.so --shared -fPIC dft.c created the .so file. shroedinger.py still seems to work. br. -osman

3 5

sfepy 0.5 tests on 64 bit ubuntu
by osman 06 Sep '08

06 Sep '08

Hi Robert, Ondrej, Finally I was able to re-build numpy/scipy and tried the new version of sfepy. Even during building of scipy, whenever a fortran or f2py based shared lib to be built, I need to manually insert "-shared" to the command (that is after it fails to build an executable! . Same with sfepy physics module. But tests did run and two failed : ... tests/test_lcbc_2d.py --- test_linear_rigid_body_bc: failed! tests/test_lcbc_3d.py --- test_linear_rigid_body_bc: failed! ... expected? Regards, -osman

3 15

ANN: SfePy-00.50.00
by Robert Cimrman 02 Sep '08

02 Sep '08

I am pleased announce the release of SfePy 00.50.00. SfePy is a finite element analysis software in Python, based primarily on Numpy and SciPy. Mailing lists, issue tracking, mercurial repository: http://sfepy.org Home page: http://sfepy.kme.zcu.cz People who contributed to this release: Ondrej Certik, Ryan Krauss, Vladimir Lukes. Major improvements: - finite strain elasticity: neo-Hookean, Mooney-Rivlin materials in the total Lagrangian (TL) formulation - solving problems in complex numbers - generalized equations to allow linear combination of terms - run-time type of state term arguments - refactoring to follow Python coding style guidelines - new terms For more information on this release, see http://sfepy.googlecode.com/svn/web/releases/005000_RELEASE_NOTES.txt Best regards, Robert Cimrman

1 0

large deformations
by Robert Cimrman 01 Sep '08

01 Sep '08

Hi all, and Ryan in particular, I have started implementing large deformations into the code. Nothing is finished yet, but I have already some proof-of-concept. I will commit relatively soon (i.e. after my holidays) a patch adding the hyperelastic neo-Hookean material. Ultimately, I would like to have in SfePy all the functionality I had in its predecessor (a matlab code called mafest1), but it is a long term goal, as it was more a one-purpose tool than a general FE system. All that the old code can do is nicely summarized in my thesis, that you can find at http://ui505p06-mbs.ntc.zcu.cz/sfe/RobertCimrman at the bottom (thesis.pdf). Ryan, try to look in particular at Section 2.1.2 (TL formulation), Chapter 3 (FE discretization in TL context) and Chapter 6 (FE discretization in a linear problem context), as it may provide you some insight. Appendix A might be also interesting, as the usual constitutive (stress-strain) relations are summarized there, e.g. the neo-Hookean one. r.

2 3

make sfepy usable a'la mathematica using sympy
by Ondrej Certik 01 Sep '08

01 Sep '08

Hi, I'd like to be able to do these things with sfepy+sympy together: http://reference.wolfram.com/mathematica/tutorial/NDSolvePDE.html I.e. really just specify the equation in sympy and sfepy should be clever enough to solve it correctly, or say why it cannot solve it. Ondrej

2 5

next release
by Robert Cimrman 27 Aug '08

27 Aug '08

Hi all, it's time to make another release (this week or start of the next one), so if you have time and will, try the latest hg version, please, and report any problems. Mainly the new hyperelastic terms surely need some testing (input/hyperelastic.py), as well as solutions in complex domain (input/complex.py). r.

1 0

Compilation/configuration problems
by Michael 24 Aug '08

24 Aug '08

Hello everybody, while compiling sfepy I found that makefile was not able to find a correct include directory for the numphy library. I had to change it by hand and it worked. I set: PYTHON_INCL := -I/usr/include/python$(PYVER) -I/usr/lib64/python2.4/ site-packages/numpy/core/include/ My Linux : uname -s -r -p -i -m Linux 2.6.18-92.1.6.el5 x86_64 x86_64 x86_64 The numphy library I compiled from the distribution numpy-1.1.1.tar.gz. I just followed their instruction: sudo python setup.py install. Michael.

2 1

holidays etc.
by Robert Cimrman 13 Aug '08

13 Aug '08

Hi all, I will be hiking in Alps from 14. to 24. August, so keep posting your questions/bugreports/patches, I will process the unresolved ones as fast as possible after. This week is unfortunately an IT infrastructure maintenance week at our university, so I may have problems getting on-line even before Thursday. It is already very slow. best wishes, r.

4 3

Installing on a Mac + manual
by Dominique 12 Aug '08

12 Aug '08

Hi all, I just downloaded the latest devel version of sfepy for installation on an Intel Mac. I wanted to let you know that in order for sfepy to compile properly, I had to make the following changes: - In the top directory Makefile: add the following to OPTFLAGS -fno-strict-aliasing -fno-common -dynamic - In sfepy/fem/extmods/Makefile.inc and sfepy/terms/extmods/ Makefile.inc, replace occurences of '-shared' with $(SHARED), where I defined SHARED = -dynamiclib -undefined dynamic_lookup at the top of the Makefile.inc (there surely is a nicer way!) I thought this might be useful to others. Next, upon running the tests, I obtained: [dpo@pod:sfepy-fe15c3e45e20]$ ./runTests.py --filter-more <<< directory: tests, test files: 23 +++ test_vector_matrix: ok +++ test_struct_add: ok +++ test_struct_i_add: ok +++ test_get_solution: ok +++ test_linear_terms: ok +++ test_input: ok +++ test_input: ok +++ test_input: ok nodes: 100% | #####################################################################| Time: 00:00:00 elements: 100% | ##################################################################| Time: 00:00:00 +++ test_input: ok +++ test_input: ok +++ test_input: ok +++ test_input: ok +++ test_input: ok +++ test_recursive_dict_hdf5: ok +++ test_sparse_matrix_hdf5: ok --- test_linear_rigid_body_bc: failed! --- test_linear_rigid_body_bc: failed! +++ test_solvers: ok nodes: 100% | #####################################################################| Time: 00:00:00 elements: 100% | ##################################################################| Time: 00:00:00 +++ test_read_meshes: ok +++ test_compare_same_meshes: ok +++ test_read_dimension: ok --- test_msm_laplace: failed! +++ test_msm_symbolic_diffusion: ok +++ test_msm_symbolic_laplace: ok +++ test_parse_equations: ok +++ test_parse_regions: ok +++ test_pbc: ok +++ test_pbc: ok +++ test_problem_creation: ok +++ test_consistency_d_dw: ok 23 test file(s) executed in 27.13 s, 3 failure(s) of 30 test(s) How can I check what went wrong with the three failures? I see no log files in the 'output_tests' directory. Moreover, I can't seem to do anything with the vtk files generated by the tests, neither with that generated with 'simply.py input/ poisson.py'. What am I missing? I have the latest Enthought Python Distribution and Enthought Tool Suite. Mayavi2 cannot seem to display the vtk scenes and neither can Paraview. Any idea what's wrong? Note that in order for the tests to run, I had to bypass the Scipy distributed as part of ETS since it is outdated (!). I had a build of 0.7.0 lying around, with UMFPACK, and that seemed to work with sfepy. Finally, yes I know, I really should read the manual. But I can't generate it! While pexpect is a breeze to install, lxml is a real pain on the Mac. Could anyone post the sfepy manual on the Wiki or on the newsgroup page? Many thanks, Dominique

3 6