On Thu, Feb 4, 2016 at 9:08 AM, John Peterson wrote:
>
>
> On Wed, Feb 3, 2016 at 5:48 PM, Roy Stogner
> wrote:
>
>>
>> On Wed, 3 Feb 2016, John Peterson wrote:
>>
>> On Wed, Feb 3, 2016 at 4:31 PM, Junchao Zhang
>>> wrote:
>>>
>>> I find libmesh does not accept some PETsc KSP options, such as
The oldest thing I still test against occasionally is 2.3.3-p15. :+1:
on removing support for anything older.
---
Roy
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Moni
On Wed, Feb 3, 2016 at 5:48 PM, Roy Stogner
wrote:
>
> On Wed, 3 Feb 2016, John Peterson wrote:
>
> On Wed, Feb 3, 2016 at 4:31 PM, Junchao Zhang
>> wrote:
>>
>> I find libmesh does not accept some PETsc KSP options, such as -ksp_rtol
>>> 0. It is likely that libmesh calls KSPSetFromOptions() t
On Thu, Feb 4, 2016 at 11:08 AM, John Peterson wrote:
>
> but how would
> people feel about removing the PETSc 2.x #ifdefs from libmesh? Looks like
> some of the code in PetscLinearSolver goes all the way back to pre-2.2.0
> (and still refers to SLES!) which was released Feb 27, 2004.
> petsc_li
On Wed, 3 Feb 2016, John Peterson wrote:
> On Wed, Feb 3, 2016 at 4:31 PM, Junchao Zhang
> wrote:
>
>> I find libmesh does not accept some PETsc KSP options, such as -ksp_rtol
>> 0. It is likely that libmesh calls KSPSetFromOptions() too early, before
>> other customization routines.
>
> I'd be
On Wed, Feb 3, 2016 at 4:31 PM, Junchao Zhang
wrote:
> I find libmesh does not accept some PETsc KSP options, such as -ksp_rtol
> 0. It is likely that libmesh calls KSPSetFromOptions() too early, before
> other customization routines.
>
I'd be very surprised if that's the case. We've been sett
