On Sun, Apr 22, 2012 at 8:41 AM, Alexander Grayver <agrayver at gfz-potsdam.de>wrote:
> ** > 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 at 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 > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120422/3fdd2bca/attachment.html>