Re: [petsc-users] Nested Fieldsplit for custom index sets

2016-07-27 Thread Safin, Artur
Barry, Lawrence, > I think the SubKSPs (and therefore SubPCs) are not set up until you call > KSPSetUp(ksp) which your code does not do explicitly and is therefore done in > KSPSolve. I added KSPSetUp(), but unfortunately the issue did not go away. I have created a MWE that replicates the

[petsc-users] vec norm for local portion of a vector

2016-07-27 Thread Xiangdong
Hello everyone, I have a global dmda vector vg. On each processor, if I want to know the norm of local portion of vg, which function should I call? So far I am thinking of using DMDAVecGetArray and then write a loop to compute the norm of this local array. Is there a simple function available

Re: [petsc-users] Ignore command line arguments with fortran code using PETSc

2016-07-27 Thread Tim Steinhoff
2016-07-27 16:04 GMT+02:00 Matthew Knepley : > On Wed, Jul 27, 2016 at 4:59 AM, Tim Steinhoff > wrote: >> >> Hi all, >> >> we coupled PETSc with our fortran code. Is there any way to let PETSc >> (PetscInitialize) ignore all arguments passed by the

Re: [petsc-users] Ignore command line arguments with fortran code using PETSc

2016-07-27 Thread Matthew Knepley
On Wed, Jul 27, 2016 at 4:59 AM, Tim Steinhoff wrote: > Hi all, > > we coupled PETSc with our fortran code. Is there any way to let PETSc > (PetscInitialize) ignore all arguments passed by the command line? > Since our code is controlled by command line arguements as well,

[petsc-users] Ignore command line arguments with fortran code using PETSc

2016-07-27 Thread Tim Steinhoff
Hi all, we coupled PETSc with our fortran code. Is there any way to let PETSc (PetscInitialize) ignore all arguments passed by the command line? Since our code is controlled by command line arguements as well, it leads to a mess, when those arguments are read twice. Thanks and kind regards,

Re: [petsc-users] Nested Fieldsplit for custom index sets

2016-07-27 Thread Lawrence Mitchell
> On 27 Jul 2016, at 03:54, Safin, Artur wrote: > > Barry, > >> Do you have a call to KSPSetFromOptions() before the call >> PCFieldSplitGetSubKSP()? I am guessing not which means that the PC does not >> yet know that it is of type fieldplit. > > Yes, I call