← Back to team overview

dolfin team mailing list archive

Re: [Fenics] Ubuntu release schedule

 

On Mon, Jun 21, 2010 at 02:37:26PM +0200, Johannes Ring wrote:
> On Mon, Jun 21, 2010 at 1:53 PM, Anders Logg <logg@xxxxxxxxx> wrote:
> > On Wed, Jun 16, 2010 at 11:49:32AM +0200, Johannes Ring wrote:
> >> On Wed, Jun 16, 2010 at 11:27 AM, Anders Logg <logg@xxxxxxxxx> wrote:
> >> > When should the deadline be for making the new releases?
> >> >
> >> > Is it too later if we finish by June 23rd?
> >>
> >> Well, it might be too late for automatic imports from Debian to
> >> Ubuntu, but I can request manual imports later. It worked out fine the
> >> last time. So June 23rd sounds good for me.
> >
> > ok, let's aim for 23rd (Wednesday this week).
> >
> > Anything that we need to fix before the release?
> >
> > The buildbot fails with this message when running the extrapolation demo:
> >
> >  run-time error: auxlib::solve_od(): need LAPACK
>
> I have the same problem on my laptop.
>
> > Is there something that needs to be installed on the buildbot?
>
> I'm not sure whats wrong but the problem seems to be that I have built
> Armadillo with debugging turned on (-DCMAKE_BUILD_TYPE:STRING=Debug)
> on the buildbot (and on my laptop). When I run gdb on
> demo/adaptivity/extrapolation/cpp I get this:
>
> [...]
> #7  0xb76340b9 in dolfin::Extrapolation::compute_coefficients
> (coefficients=@0xbfe89fc0, v=@0xbfe8a258, V=@0xbfe8a3b8,
> W=@0xbfe8a338,
>     cell0=@0xbfe89f98, c0=@0xbfe89f58, dofs=@0xbfe89fd0, offset=@0xbfe89fcc)
>     at /home/johannr/src/armadillo-0.6.10/Build/local/include/armadillo_bits/debug.hpp:218
> #8  0xb7634e5b in dolfin::Extrapolation::extrapolate (w=@0xbfe8a178,
> v=@0xbfe8a258) at dolfin/adaptivity/Extrapolation.cpp:72
> #9  0xb740bd54 in dolfin::Function::extrapolate (this=0xbfe8a178,
> v=@0xbfe8a258) at dolfin/function/Function.cpp:330
> #10 0x0805c768 in main () at main.cpp:44
>
> Should I just rebuild Armadillo with debugging off on the buildbots?
>
> Johannes

Could you add some debugging to Extrapolation.cpp to see where things
go wrong? Find the line that says

  arma::Col<double> x = arma::solve(A, b);

and print something before and after. It would be interesting to see
if

  1. This is where it breaks
  2. It breaks already the first time or just for particular input data

--
Anders

Attachment: signature.asc
Description: Digital signature


Follow ups