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 is
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 to
Actually there is currently no way to PetscInitialize from Fortran without
adding the command line options to the database. In the middle
of petscinitialize_() is the code fragment
PETScParseFortranArgs_Private(&PetscGlobalArgc,&PetscGlobalArgs);
FIXCHAR(filename,len,t1);
*ierr = PetscOp
Please send a complete code that you think should work that doesn't so we can
understand the exact issue.
> On Jul 26, 2016, at 10:54 PM, Safin, Artur wrote:
>
> Barry,
>
>> Do you have a call to KSPSetFromOptions() before the call
>> PCFieldSplitGetSubKSP()? I am guessing not which mea
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 command line?
>> Since our code is controlled by
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, it
> leads to a mess, w
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,
Volk
> 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 KSPSetFromOptions() for the globa