Re: [petsc-dev] New implementation of PtAP based on all-at-once algorithm

2019-04-15 Thread Mark Adams via petsc-dev
> >> I wonder if the their symbolic setup is getting called every time. You do >> 50 solves it looks like and that should be enough to amortize a one time >> setup cost. >> > > Hypre does not have concept called symbolic. They do everything from > scratch, and won't reuse any data. > Really,

Re: [petsc-dev] New implementation of PtAP based on all-at-once algorithm

2019-04-15 Thread Mark Adams via petsc-dev
> > So you could reorder your equations and see a block diagonal matrix with >> 576 blocks. right? >> > > I not sure I understand the question correctly. For each mesh vertex, we > have a 576x576 diagonal matrix. The unknowns are ordered in this way: > v0, v2.., v575 for vertex 1, and another

Re: [petsc-dev] New implementation of PtAP based on all-at-once algorithm

2019-04-15 Thread Mark Adams via petsc-dev
On Mon, Apr 15, 2019 at 2:56 PM Fande Kong wrote: > > > On Mon, Apr 15, 2019 at 6:49 AM Matthew Knepley wrote: > >> On Mon, Apr 15, 2019 at 12:41 AM Fande Kong via petsc-dev < >> petsc-dev@mcs.anl.gov> wrote: >> >>> On Fri, Apr 12, 2019 at 7:27 AM Mark Adams wrote: >>> On Thu,

Re: [petsc-dev] New implementation of PtAP based on all-at-once algorithm

2019-04-15 Thread Mark Adams via petsc-dev
> > > I guess you are interested in the performance of the new algorithms on > small problems. I will try to test a petsc example such as > mat/examples/tests/ex96.c. > It's not a big deal. And the fact that they are similar on one node tells us the kernels are similar. > > >> >> And are you

Re: [petsc-dev] MatNest and FieldSplit

2019-04-15 Thread Pierre Jolivet via petsc-dev
> On 15 Apr 2019, at 2:17 PM, Matthew Knepley > wrote: > > On Mon, Apr 15, 2019 at 5:03 AM Pierre Jolivet via petsc-dev > mailto:petsc-dev@mcs.anl.gov>> wrote: > OK, my solver is now working properly with a call to > PetscObjectCompose((PetscObject)isS, "pmat",

Re: [petsc-dev] MatNest and FieldSplit

2019-04-15 Thread Pierre Jolivet via petsc-dev
OK, my solver is now working properly with a call to PetscObjectCompose((PetscObject)isS, "pmat", (PetscObject) myS); I have two follow-up questions: 1) am I supposed to call this, or is it the sign of something done wrong in my sequence of SNESSolve/KSPSetUp/KSPSetFromOptions/KSPSetOperators…?