On 07/04/2013 10:45 PM, Derek Gaston wrote:
> David - do you call close() on a matrix before putting entries into it
> everywhere?
Looking at the code, I call zero() before commencing matrix assembly,
but not close().
> Are you relying on setting something like
> KEEP_NONZERO_PATTERN on a Pet
On 07/04/2013 10:18 PM, Kirk, Benjamin (JSC-EG311) wrote:
> I'll be able to debug it after the holiday, but just to be sure - there is a
> method in the DofMap that returns block size - if you hardcode that to return
> 1 everything should be as it was - does that work?
Yep, hardcoding the block
David - do you call close() on a matrix before putting entries into it
everywhere? Are you relying on setting something like
KEEP_NONZERO_PATTERN on a Petsc matrix to keep it from dropping your
preallocation in the case where you close a matrix before setting all
of its entries?
The reason I ask
I'll be able to debug it after the holiday, but just to be sure - there is a
method in the DofMap that returns block size - if you hardcode that to return 1
everything should be as it was - does that work?
-Ben
On Jul 4, 2013, at 7:59 AM, "David Knezevic" wrote:
> If you have any ideas on w
Hi Ben,
A bit more info re the apparent sparsity pattern issue in RBConstruction.
The error occurs in RBConstruction::assemble_misc_matrices(),
specifically in the call to
assemble_inner_product_matrix(inner_product_matrix.get());
inner_product_matrix is an "extra matrix" that is a member of
