On Tue, Jun 7, 2016 at 6:19 PM, Jayaraman, Vegnesh
wrote:
> Hi
>
> Can the matrix->zero_rows() function not be used during assembly? I get an
> "Object Not Initialized " error during runtime if I use the above function
> in assembly.
>
zero_rows() can't be called interspersed with the MatSetValu
to set the right option.
Thanks for helping me
Vegnesh
From: David Knezevic [david.kneze...@akselos.com]
Sent: Monday, June 06, 2016 9:30 PM
To: Jayaraman, Vegnesh
Cc: libmesh-users@lists.sourceforge.net
Subject: Re: [Libmesh-users] Using Sparse matrix functions
The error message "New nonzero at (1,9) caused a malloc!" is from PETSc.
PETSc is trying to do you a favor by telling you that you're allocating new
non-zeros in your matrix, which is slow and should be avoided.
PETSc requires the number of nonzeros per row to be specified before the
matrix is ass
Hello,
I am trying to modify the entries of the system matrix in the main function.
As a first test, I did the following,
elem = *el;
dof_map.dof_indices(elem,dof_columns);
system.matrix->zero_rows(dof_columns,500.234);
The above code changes the variables in system matrix.
However, if I did
