I don't like the look of this. It's mixing a linear algebra issue
(PETSc bug?) with the assembler. Moreover, it will be horrendously
slow if the diagonal has not been allocated during the initialisation
of the matrix.
There is a suggestion in the thread to make the sparsity pattern
contain the diagonal entry, which seems a reasonable option, but there
is not answer on whether this solves the problem. Would it solve the
problem?
I don't like the look of this. It's mixing a linear algebra issue
(PETSc bug?) with the assembler. Moreover, it will be horrendously
slow if the diagonal has not been allocated during the initialisation
of the matrix.
There is a suggestion in the thread to make the sparsity pattern
contain the diagonal entry, which seems a reasonable option, but there
is not answer on whether this solves the problem. Would it solve the
problem?
Garth
On 9 May 2012 06:05, Cian Wilson <email address hidden> wrote: /bugs.launchpad .net/dolfin/ +bug/927539/ +attachment/ 3137879/ +files/ diag.diff /bugs.launchpad .net/bugs/ 927539 /bugs.launchpad .net/dolfin/ +bug/927539/ +subscriptions
> ** Patch added: "diag.diff"
> https:/
>
> --
> You received this bug notification because you are a member of DOLFIN
> Core Team, which is subscribed to DOLFIN.
> https:/
>
> Title:
> Missing diagonals after subdomain assembly
>
> To manage notifications about this bug go to:
> https:/