dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #04122
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
On Mon, Jan 15, 2007 at 05:58:46PM +0100, Garth N. Wells wrote:
>
>
> Anders Logg wrote:
> > On Thu, Dec 07, 2006 at 01:12:41AM +0100, Garth N. Wells wrote:
> >
> >>>> I'll add shortly the possibility to run the Cuthill-McKee over the map
> >>>> and reorder it. This will be an option.
> >>> What is Cuthill-McKee?
> >> It's the most common reordering algorithm. It will probably improve the
> >> sparse matrix performance.
> >
> > How about using the Boost Graph Library for this?
> >
> > http://www.boost.org/libs/graph/doc/table_of_contents.html
> > http://www.boost.org/libs/graph/doc/cuthill_mckee_ordering.html
> >
> > We already have a boost dependence so another one is no problem.
> >
>
> Sure, if it's in Boost I'd much rather use it than implement it myself.
I've started looking at it and might commit something tonight.
> I will start with a class Assembler soon. This is related in some ways
> to DofMap, matrix layout, reuse, etc. We could then create a class
> "pAssembler" for experimental parallel assembly which should eventually
> merge back into Assembler.
>
> Garth
I'm also about to start working on an Assembler class that works with
the UFC generated code. Should we work together on the new Assembler
class? Alternatively, I could open a separate UFCAssembler class (to
be merged)?
/Anders
Follow ups
References
-
[HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: DOLFIN, 2006-12-05
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Anders Logg, 2006-12-06
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Garth N. Wells, 2006-12-06
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Anders Logg, 2006-12-06
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Garth N. Wells, 2006-12-06
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Anders Logg, 2006-12-06
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Garth N. Wells, 2006-12-07
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Anders Logg, 2007-01-14
-
Re: [HG dolfin] Use DofMap in FEM to get dof mapping and to compute number of nonzeroes per matrix row. This gives big memory savings for some problems. For /src/demo/pde/elasticity memory use was approx. 600mb, now 200mb.
From: Garth N. Wells, 2007-01-15