On Mon, 17 Sep 2012, Derek Gaston wrote:
> While that is probably true... we should probably enhance the SparseMatrix > interface to handle mat*mat cases... maybe Andrew would be willing to > supply a patch?! ;-) I'd be thrilled to see that. PetscMatrix does give easy access to the PETSc Mat, but it's better to write nominally solver-indpendent code, even if it's just libmesh_not_implemented() in the other solvers, simply because the next thing you know some OCD person comes around and says "hey, why isn't that new example working in Trilinos and Lapack; let me fix that" and the next thing you know you're actually solver-independent again. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
