graeser at mi.fu-berlin.de
Tue Oct 13 14:37:19 CEST 2015
in my attempt to verify if out global basis interface is rich
enough I implemented an ISTL-backend whose sole functionality
is currently to provide
operator()(const MultiIndex& row, const MultiIndex& col)
Sound's easy, but is in fact a little tricky to get right
for multitype-matrices and especially if the multi-indices
have non-uniform length (but it works for these cases).
Next thing to add would be resize/allocate functionality.
But I'm undecided if the backend should be in dune-functions
+ Stokes-example gets more elegant
+ Stokes-example gets almost agnostic on index scheme
+ Can serve as an example of how to implement a backend
- Far beyond the scope of dune-functions.
- Stokes-example gets less basic because we'd not like
to explain the magic in the backend to Joe Average
Please give you're opinion. A 'no' would be no problem
and just mean that I put this in dune-fufem where we'll
need this once we switch to dune-functions bases.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: OpenPGP digital signature
More information about the dune-functions