Hi all,
In the development version of SfePy, I have just finished a large
refactoring aimed at adhering to python style guidelines, see
'http://code.google.com/p/sfepy/wiki/CodingStyle'. The change has been
pushed for by Ondrej (thanks for being insistent) and motivated by the
fact that most of our favorite Python projects already use this style.
You can use './script/edit_identifiers.py <files>' to convert your code
to the new style. Some manual tweaks might be needed, though, as the
script is a quick one-shot hack.
This style will be used in the next release, that is why I inform you in
advance about what is going on in the development code.
Best wishes,
r.
I have a question about where you guys put the files you are working
on with SfePy. For SciPy and NumPy, I am used to having an svn
directory that is only for the scipy/numpy code. Once I do "sudo
python setup.py install", I leave that directory and don't do any
actual work in it. SfePy doesn't seem to work that way. The thing
about that that is tricky for me is that I like to use Unison to
sychronize my laptop and desktop. They have different processors, so
I don't want to syncronize any build directories (or anything else
that would get typically modified by mercurial), but I do want to sync
my own stuff (meshes and input files and such).
Do you put all your personal work in folders that are underneath the
main SfePy directory? Or with enough paths added to PYTHONPATH, can I
put my SfePy related stuff in any directory?
Thanks,
Ryan
Hi,
I need to restart the server and at this occasion, I'll also move the
repositories from /tmp. :) Anyway, this time you'll have to recreate
them, next time all should be ok.
Ondrej
What repository do I need to add to /etc/apt/sources.list to get
paraview easily installed? I don't see it in Synaptic with my current
list of sources (I am running Ubuntu 7.10).
Thanks,
Ryan
So, I am taking my first steps in using SfePy. I have two questions,
one about mesh generation and one about the results I am getting.
First, about mesh generation. I am trying to understand the workflow.
What is actually necessary? What is the easiest way to create a mesh
for a really simple part, like a cube or cylinder? I have tinkered
with TetGen and have generated a mesh that way. I was reading through
convert.py and trying to understand what it wants as an input. In the
end, I didn't use convert.py and simply set
fileName_mesh = 'input/first_mesh.1.node'
in my input file. Is this correct? Is it best? Does it actually
read all the other files about by TetGen (.face and .ele), or is it
only using the .node file?
First_mesh.poly is my input to TetGen and the others are the output.
I think it worked.
For my second question, I used the attached mesh files along with the
input script from_Robert.py (something he sent me a while back) and
simply.py and got the following output:
In [1]: run simple.py input/from_Robert.py
sfe: warning: other missing: ['functions', 'modules',
'epbc_[0-9]+|epbcs', 'lcbc_[0-9]+|lcbcs', 'nbc_[0-9]+|nbcs',
'options']
sfe: warning: left over: ['tractionLoad']
sfe: reading mesh...
nodes: 100% |############################################| Time: 00:00:00
elements: 100% |#########################################| Time: 00:00:00
sfe: ...done in 0.04 s
sfe: setting up domain edges...
sfe: ...done in 0.00 s
sfe: setting up domain faces...
sfe: ...done in 0.01 s
sfe: creating regions...
sfe: leaf Top region_2
sfe: leaf Omega region_1000
sfe: leaf Bottom region_1
sfe: ...done in 0.04 s
sfe: equation "balance_of_forces":
sfe: dw_lin_elastic_iso.i1.Omega( solid.lame, v, u )
= dw_surface_ltr.isurf.Top( traction.val, v )
sfe: describing geometries...
sfe: ...done in 0.01 s
sfe: setting up dof connectivities...
sfe: ...done in 0.00 s
sfe: using solvers:
nls: newton
ls: ls
sfe: matrix shape: (156, 156)
sfe: assembling matrix graph...
sfe: ...done in 0.00 s
sfe: matrix structural nonzeros: 4248 (1.75e-01% fill)
sfe: updating materials...
sfe: solid
sfe: traction
TimeStepper
nDigit:
1
t0:
0.0
t1:
1.0
step:
0
time:
0.0
dt:
1.0
times:
[ 0.]
nt:
0.0
nStep:
1
input/from_Robert.py, 69: tractionLoad(), 76
sfe: ...done in 0.00 s
sfe: nls: iter: 0, residual: 0.000000e+00 (rel: 0.000000e+00)
and the attached vtk file. The vtk file seems to say that the force
at each node is 0. That doesn't seem right.
Am I doing something wrong? Are these results actually valid? How
should I proceed?
I was thinking that in terms of material modeling, I would start with
a static compressive load applied to the foam specimen, then a load
that ramps up and watch the displacement and stress in each case.
Start with small stresses and strains and then talk about how to
handle large strains. Does that make sense?
Thanks for your help.
Ryan
Just to inform you that equation syntax was generalized for an arbitrary
linear combination of terms, e.g.:
2 * dw_laplace.i1.Omega( coef.val, s, t ) = - 0.5 *
dw_volume_lvf.i1.Omega( rhs.val, s )
It is no more necessary to pass a multiplicative constant via a material
argument.
r.
Hi,
thanks to Ondrej and Ryan, there will be two more (Ryan) or less
(Ondrej) SfePy-related talks at the SciPy 2008 conference at Caltech,
http://conference.scipy.org/.
Submit, please, issues related to your topics at
http://code.google.com/p/sfepy/issues/list, so that all can see what
needs to be done prior to the conference.
r.
I am pleased announce the release of SfePy 00.46.02.
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
Major improvements:
- alternative short syntax for specifying essential boundary conditions,
variables and regions
- manufactured solutions tests:
- SymPy support
- site configuration now via script/config.py + site_cfg.py
- new solvers
- new terms
For more information on this release, see
http://sfepy.googlecode.com/svn/web/releases/004602_RELEASE_NOTES.txt
If you happen to come to Leipzig for EuroSciPy 2008, see you there!
Best regards,
Robert Cimrman & SfePy developers
