dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #18622
[Bug 594954] Re: uBLAS GMRES solver fails on first run
And it happens only occasionally, not every time. And it doesn't seem to
correlate with instant-clean.
--
uBLAS GMRES solver fails on first run
https://bugs.launchpad.net/bugs/594954
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.
Status in DOLFIN: Confirmed
Bug description:
(reported by Doug Arnold)
After cleaning the instant cache, the solver
from dolfin import *
parameters["linear_algebra_backend"] = "uBLAS"
mesh = UnitSquare(3,3)
V = FunctionSpace(mesh, 'CG', 1)
v = TestFunction(V)
u = TrialFunction(V)
a = u*v*dx
A = assemble(a)
L = v*dx
b = assemble(L)
x = Vector(b.size())
solve(A, x, b, "gmres")
print x.array()
crashes with the message:
Check failed in file /usr/include/boost/numeric/ublas/operation.hpp at line 260:
norm_1 (v - cv) <= 2 * std::numeric_limits<real_type>::epsilon () * verrorbound
Traceback (most recent call last):
File "solve3.py", line 12, in <module>
solve(A, x, b, 'gmres')
File "/home/faculty/arnold/workshop/FEniCS/lib/python2.6/site-packages/dolfin/cpp.py", line 4169, in solve
return _cpp.solve(*args)
StandardError: internal logic
Searching on the web for the error message came up with this:
http://archives.free.net.ph/message/20081022.224821.1eddeaa9.da.html
where Gunter Winkler suggests "#define BOOST_UBLAS_TYPE_CHECK 0",
but I don't know how to do this from dolfin.
References