dolfin team mailing list archive

["Garth N. Wells" <g.n.wells@xxxxxxxxxx>]

> > One thing to consider is more sophisticated dof mapping. It is worth 
> > considering a special class to take care of this. This would be useful 
> > for meshes with mixed cell/element types, parallel assembly and 
> > computing sparsity patterns.
>
> Yes, we could create a separate class in src/fem/ that takes care of
> this. Name suggestions: NodeMap, NodeMapping, Nodes, Dofs, DofHandler,
> ...

What about DofHandler or DofManager? I see the class handling the dof 
mapping, as well as generating sparsity patterns. I'll add something, 
and start with a function for computing the number of non-zeroes per 
matrix row (we're overestimating this at the moment substantially which 
is giving me some memory problems).

Garth

> FFC generates *one* local-to-global mapping but we are free to reorder
> what FFC generates. The new class should take input from FFC, reorder
> it and then make the new ordering accessible during assembly.
>
> > Is there a preference to eventually add partitioning functions in 
> > src/kernel/mesh, or src/kernel/partition?
>
> I suggest src/kernel/mesh since this is at the same level as
> refinement and coarsening.
>
> /Anders
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev