Re: .mesh file documentation

June 23, 2008


      So, I thought it was a problem with my not using Mercurial correctly.
So, I deleted my clone and re-cloned and am still getting the same
error: No module named splinalg.isolve.  Here is the full output:
In [4]: run runTests.py --debug tests/test_linear_solvers.py
<<< tests/test_linear_solvers.py
sfe: warning: other missing: ['functions', 'modules',
'epbc_[0-9]+|epbcs', 'lcbc_[0-9]+|lcbcs', 'nbc_[0-9]+|nbcs']
sfe: warning: left over: ['outputName', 'TestCommon']
sfe: reading mesh...
sfe: ...done in 1.05 s
sfe: setting up domain edges...
sfe: ...done in 0.70 s
sfe: setting up domain faces...
sfe: ...done in 0.52 s
sfe: creating regions...
sfe:     leaf Gamma_Right region__0
sfe:     leaf Omega region__1
sfe:     leaf Gamma_Left region__2
sfe: ...done in 0.79 s
sfe: equation "Temperature":
sfe: dw_laplace.i1.Omega( coef.val, s, t ) = 0
sfe: describing geometries...
sfe: ...done in 0.05 s
sfe: setting up dof connectivities...
sfe: ...done in 0.00 s
sfe: using solvers:
nls: newton
ls: ls101
sfe: matrix shape: (9511, 9511)
sfe: assembling matrix graph...
sfe: ...done in 0.09 s
sfe: matrix structural nonzeros: 132239 (1.46e-03% fill)
sfe: updating materials...
sfe:     coef
sfe: ...done in 0.00 s
...
...
...
test instance prepared (1 test(s))
... dls100 ls.umfpack
... matrix size: (9511, 9511)
...         nnz: 132239
just before UMFPACK_CONTROL
just after UMFPACK_CONTROL
UMFPACK_CONTROL=20
sfe: nls: iter: 0, residual: 3.587850e+00 (rel: 1.000000e+00)
sfe:   rezidual:    0.02 [s]
sfe:      solve:    2.14 [s]
sfe:     matrix:    0.06 [s]
sfe: nls: iter: 1, residual: 4.177710e-15 (rel: 1.164405e-15)
...   rezidual:    0.02 [s]
...      solve:    2.14 [s]
...     matrix:    0.06 [s]
... condition: 0, err0: 3.588e+00, err: 4.178e-15
... ls101 ls.pyamg ruge_stuben_solver
... matrix size: (9511, 9511)
...         nnz: 132239
sfe: cannot import pyamg!
... solver failed:
... No module named pyamg
... ls102 ls.pyamg smoothed_aggregation_solver
... matrix size: (9511, 9511)
...         nnz: 132239
sfe: cannot import pyamg!
... solver failed:
... No module named pyamg
... ls110 ls.scipy_iterative cg
... matrix size: (9511, 9511)
...         nnz: 132239
... solver failed:
... No module named splinalg.isolve
... ls111 ls.scipy_iterative bicgstab
... matrix size: (9511, 9511)
...         nnz: 132239
... solver failed:
... No module named splinalg.isolve
... ls112 ls.scipy_iterative qmr
... matrix size: (9511, 9511)
...         nnz: 132239
... solver failed:
... No module named splinalg.isolve
... solution times:
... 2.14 : dls100 ls.umfpack
... 10000000000.00 : ls101 ls.pyamg ruge_stuben_solver
... 10000000000.00 : ls102 ls.pyamg smoothed_aggregation_solver
... 10000000000.00 : ls110 ls.scipy_iterative cg
... 10000000000.00 : ls111 ls.scipy_iterative bicgstab
... 10000000000.00 : ls112 ls.scipy_iterative qmr
--- test_solvers: failed!
!!! 1 test failed
1 test file executed in 3.17 s, 1 failure(s) of 1 test(s)
I am running scipy svn from a month or so ago.  I can easily update or
install the previous revision, but I thought it was worth fighting
through this to get rid of a bug:
In [5]: scipy.__version__
Out[5]: '0.7.0.dev3851'
Thanks for the on going help,
Ryan
On Mon, Jun 23, 2008 at 3:53 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
...
Ondrej Certik wrote:
...
Thanks, seems like a bug in sfepy, that it requires svn version of
scipy, while it should only require the released version (everything
else being only optional). We fixed most of bugs like these, but
sometimes something creeps in.
Yes, it is good to have people using different scipy versions to test
the code. I use the SVN version, so sometimes something slips in.
r.
...

Re: .mesh file documentation

Ryan Krauss