Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 9:52 PM, Barry Smith wrote: > > > The magic handling of _1_ etc is all done in PetscOptionsFindPair_Private() > so you need to put a break point in that routine and see why the requested > value is not located. I haven’t tracked down the source of the problem with usin

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 9:40 PM, Barry Smith wrote: > >> >> On Aug 4, 2016, at 9:26 PM, Boyce Griffith wrote: >> >>> >>> On Aug 4, 2016, at 9:01 PM, Barry Smith wrote: >>> On Aug 4, 2016, at 8:51 PM, Boyce Griffith wrote: > > On Aug 4, 2016, at 8:42 PM, Barry Smith

Re: [petsc-users] PCASMType

The magic handling of _1_ etc is all done in PetscOptionsFindPair_Private() so you need to put a break point in that routine and see why the requested value is not located. Barry > On Aug 4, 2016, at 9:46 PM, Boyce Griffith wrote: > > >> On Aug 4, 2016, at 9:41 PM, Boyce Griffith wr

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 9:41 PM, Boyce Griffith wrote: > > >> On Aug 4, 2016, at 9:26 PM, Boyce Griffith > > wrote: >> >>> >>> On Aug 4, 2016, at 9:01 PM, Barry Smith >> > wrote: >>> On Aug 4, 2016, at 8:51 PM, Boyce Griffith >

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 9:26 PM, Boyce Griffith wrote: > >> >> On Aug 4, 2016, at 9:01 PM, Barry Smith > > wrote: >> >>> >>> On Aug 4, 2016, at 8:51 PM, Boyce Griffith >> > wrote: >>> On Aug 4, 2016, at 8:42 PM, Barry Smith >>>

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 9:26 PM, Boyce Griffith wrote: > >> >> On Aug 4, 2016, at 9:01 PM, Barry Smith wrote: >> >>> >>> On Aug 4, 2016, at 8:51 PM, Boyce Griffith wrote: >>> On Aug 4, 2016, at 8:42 PM, Barry Smith wrote: History, 1) I originally implem

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 9:01 PM, Barry Smith wrote: > >> >> On Aug 4, 2016, at 8:51 PM, Boyce Griffith wrote: >> >>> >>> On Aug 4, 2016, at 8:42 PM, Barry Smith wrote: >>> >>> >>> History, >>> >>> 1) I originally implemented the ASM with one subdomain per process >>> 2) easily extended to s

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 8:51 PM, Boyce Griffith wrote: > >> >> On Aug 4, 2016, at 8:42 PM, Barry Smith wrote: >> >> >> History, >> >> 1) I originally implemented the ASM with one subdomain per process >> 2) easily extended to support multiple domain per process >> 3) added -pc_asm_type restri

Re: [petsc-users] PCASMType

> On Aug 4, 2016, at 8:42 PM, Barry Smith wrote: > > > History, > > 1) I originally implemented the ASM with one subdomain per process > 2) easily extended to support multiple domain per process > 3) added -pc_asm_type restrict etc but it only worked for one subdomain per > process because

Re: [petsc-users] PCASMType

History, 1) I originally implemented the ASM with one subdomain per process 2) easily extended to support multiple domain per process 3) added -pc_asm_type restrict etc but it only worked for one subdomain per process because it took advantage of the fact that restrict etc could be achie

Re: [petsc-users] false-positive leak report in log_view?

Patrick Sanan writes: > On Thu, Aug 4, 2016 at 10:18 AM, Dave May wrote: >> >> >> On 4 August 2016 at 10:10, Patrick Sanan wrote: >>> >>> I have a patch that I got from Dave that he got from Jed which seems >>> to be related to this. I'll make a PR. >> >> >> Jed wrote this variant of the VTK vi

[petsc-users] PCASMType

With PETSc 3.7.2, changing the ASM type does not seem to have any effect for serial jobs. E.g. using ksp/examples/tutorials/ex2: $ ./ex2 -m 32 -n 32 -pc_type asm -pc_asm_blocks 8 -ksp_view -ksp_monitor_true_residual -pc_asm_type basic 0 KSP preconditioned resid norm 7.227368482718e+00 true res

Re: [petsc-users] block matrix without MatCreateNest

On Thu, Aug 4, 2016 at 3:43 AM, Klaij, Christiaan wrote: > OK, looking forward to the fix! > > Related to this, the preallocation would need to depend on the > type that is given at runtime, say > > if type=XXX, call MatXXXSetPreallocation() > > That would work for say seqaij and mpiaij, probably

[petsc-users] [Alibaba Notification]Gabriel from CANADA placed an order with you

The following message was generated before 3 August 2016 09:41(PST) This message was sent to you only Registered Location and Message Origin: CANADA Message IP: 205.204.92.* Dear Supplier, I'm interested in your product and will like to know the MOQ.

Re: [petsc-users] block matrix without MatCreateNest

OK, looking forward to the fix! Related to this, the preallocation would need to depend on the type that is given at runtime, say if type=XXX, call MatXXXSetPreallocation() That would work for say seqaij and mpiaij, probably even without the if-statement, right? And since there's no MatNestSetPr

Re: [petsc-users] false-positive leak report in log_view?

On Thu, Aug 4, 2016 at 10:18 AM, Dave May wrote: > > > On 4 August 2016 at 10:10, Patrick Sanan wrote: >> >> I have a patch that I got from Dave that he got from Jed which seems >> to be related to this. I'll make a PR. > > > Jed wrote this variant of the VTK viewer so please mark him as a review

Re: [petsc-users] false-positive leak report in log_view?

On 4 August 2016 at 10:10, Patrick Sanan wrote: > I have a patch that I got from Dave that he got from Jed which seems > to be related to this. I'll make a PR. > Jed wrote this variant of the VTK viewer so please mark him as a reviewer for my bug fix. > > > On Wed, Aug 3, 2016 at 8:18 PM, Moha

Re: [petsc-users] false-positive leak report in log_view?

I have a patch that I got from Dave that he got from Jed which seems to be related to this. I'll make a PR. On Wed, Aug 3, 2016 at 8:18 PM, Mohammad Mirzadeh wrote: > OK so I just ran the example under valgrind, and if I use two VecViews, it > complains about following leak: > > ==66838== 24,802

Re: [petsc-users] Reference for multi-grid tuning

Guidelines for tuning AMG are really hard to do. There is some discussion on this in the manual and I am writing a GAMG paper now (slowly, with others) that has another shot at this sort of thing. I can share that with you privately. Because this sort of one-way text documentation has been inadeq