Sorry, I don't quite get. Is this something I can avoid by doing preallocation properly or petsc issue that will be fixed?

This looks like a PETSc bug to me, but it would be nice to get input that triggers it.

Thanks,

Matt

On 20.04.2012 14:23, Jed Brown wrote:

On Fri, Apr 20, 2012 at 05:18, Matthew Knepley <knepley@gmail.com> wrote:

Did someone intend to fix this, and then stop? MatAXPY_BasicWithPreallocation() is the same as MatAXPY_Basic().

Look how it's called. I don't know what's going on here.

ierr = MatAXPYGetPreallocation_SeqAIJ(yy->A,xx->A,nnz_d);CHKERRQ(ierr);

ierr = MatAXPYGetPreallocation_SeqAIJ(yy->B,xx->B,nnz_o);CHKERRQ(ierr);

ierr = MatMPIAIJSetPreallocation(B,0,nnz_d,0,nnz_o);CHKERRQ(ierr);

ierr = MatAXPY_BasicWithPreallocation(B,Y,a,X,str);CHKERRQ(ierr);

-- Regards, Alexander