Justin,
Could you provide more details or an example how
> "DIVERGED_LINE_SEARCH" which essentially "resets" my solution to zero and
> messes everything up
In the VI RSLS solver the code looks like
if (lssucceed) {
if (++snes->numFailures >= snes->maxFailures) {
On Wed, Nov 30, 2016 at 8:54 PM, Justin Chang wrote:
> Generally speaking, yes. But this is VIRS where I am enforcing maximum
> principles. From what I have seen, the residual typically exhibit this
> behavior if there are very few violations in the first place.
>
So you
Also, -snes_stol does not seem to work for vinewtonrsls?
On Wed, Nov 30, 2016 at 8:54 PM, Justin Chang wrote:
> Generally speaking, yes. But this is VIRS where I am enforcing maximum
> principles. From what I have seen, the residual typically exhibit this
> behavior if
Generally speaking, yes. But this is VIRS where I am enforcing maximum
principles. From what I have seen, the residual typically exhibit this
behavior if there are very few violations in the first place.
How would I "terminate on stagnation"?
On Wed, Nov 30, 2016 at 8:48 PM, Matthew Knepley
On Wed, Nov 30, 2016 at 8:38 PM, Justin Chang wrote:
> By manually terminating I meant setting -snes_max_it to 5 if I know
> DIVERGED_LINE_SEARCH
> occurs after 6 iterations. In a transient simulation I cannot do this
>
Let me elaborate. I mean that using
By manually terminating I meant setting -snes_max_it to 5 if I know
DIVERGED_LINE_SEARCH
occurs after 6 iterations. In a transient simulation I cannot do this
On Wed, Nov 30, 2016 at 8:35 PM, Matthew Knepley wrote:
> On Wed, Nov 30, 2016 at 8:27 PM, Justin Chang
On Wed, Nov 30, 2016 at 8:27 PM, Justin Chang wrote:
> Hi all,
>
> I am running some transient simulations using SNESVINEWTONRSLS. At
> certain timesteps, I get a "DIVERGED_LINE_SEARCH" which essentially
> "resets" my solution to zero and messes everything up. I notice that