MATSHELL a bit broken...

Lisandro Dalcin dalcinl at
Thu Oct 25 16:20:48 CDT 2007

It seems MATSHELL implementation is a bit broken. If I'm not wrong, if
a user set the operations MOP_ASSEMBLY_END, then the use of the
automatic MatScale/MatShift would lead to unexpected result...

Should this operation be managed the same way as
mult/multtranspose/get diagonal currently is, that is, by backupping
the user provided function pointer?

BTW, sorry if I disturb you asking for making changes that seems
trivial, but I really do not like to change any line of code after
knowing your opinion.

Lisandro Dalcín
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594

More information about the petsc-dev mailing list