Barry Smith writes:
> I think it is better to make this safe. If user calls
> MatXXXSetPreallocation() then set nonew flag, if they do not call
> it then do not set nonew flag. Having it depend on the exact
> arguments passed in is just too dangerous.
That's fine, but Pierre shoul
Jed,
I think it is better to make this safe. If user calls
MatXXXSetPreallocation() then set nonew flag, if they do not call it then do
not set nonew flag. Having it depend on the exact arguments passed in is just
too dangerous.
See my other mail to petsc-dev
when MatMPISetPrea
On Jan 15, 2014, at 11:20 AM, Matthew Knepley wrote:
> This is a bug in the setup phase for Mat. I did not put in the logic, so I
> might be missing the point. Here is
> my outline:
>
> 1) When MatSetPreallocation_*() is called, we set the
> NEW_NONZERO_ALLOCATION_ERR option, but ONLY
>
This is a bug in the setup phase for Mat. I did not put in the logic, so I
might be missing the point. Here is
my outline:
1) When MatSetPreallocation_*() is called, we set the
NEW_NONZERO_ALLOCATION_ERR option, but ONLY
if the user passed a nonzero nz or nnz.
2) During assembly, we ch
