[petsc-users] Error: Too many KSP monitors set

[Dominik Szczerba]

The issue is gone in 3.2, at least with the same number of successive
calls to kspsolve.

Thanks,
Dominik

On Fri, Oct 21, 2011 at 4:05 PM, Dominik Szczerba <dominik at itis.ethz.ch> wrote:
> Unfortunately, I am still forced to use version 3.1. I will come back to
> this issue after the upgrade to 3.2, which should be next week.
> Many thanks,
> Dominik
>
> On Fri, Oct 21, 2011 at 3:28 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>
>>   Dominik,
>>
>>      This should not happen. Does this happen with petsc-3.2? Note that we
>> are now supporting PETSc 3.2 and if the problem does not exist in 3.2 we
>> will not fix it in 3.1. If it exists in 3.2 we will definitely fix it. Can
>> you send us a small piece of code that exhibits this behavior or point to a
>> PETSc example that exhibits this behavior so we can reproduce it and fix the
>> error in 3.2
>>
>>    Barry
>>
>>    We have specific code that prevents the
>> On Oct 21, 2011, at 4:18 AM, Dominik Szczerba wrote:
>>
>> > I am getting this error when performing a series of KSP solves. Removing
>> > "-ksp_monitor_true_residual" from options removes the error, but I would
>> > like to see the residues on screen.
>> >
>> > I do not seem to find any functions in the docu to set max number of KSP
>> > monitors, but even if there is one - is it really wasteful to monitor each
>> > solve of my system?
>> >
>> > Thanks,
>> > Dominik
>> >
>> > [0]PETSC ERROR: --------------------- Error Message
>> > ------------------------------------
>> > [0]PETSC ERROR: Argument out of range!
>> > [0]PETSC ERROR: Too many KSP monitors set!
>> > [0]PETSC ERROR:
>> > ------------------------------------------------------------------------
>> > [0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 8, Thu Mar 17
>> > 13:37:48 CDT 2011
>> >
>>
>
>