You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running LBFGS optimization algorithm with MoreThuente linesearch algorithm.
I track the execution of the algorithm by damping the output of the trace into the terminal.
In some cases (which are, fortunately, rare), the optimization just gets stuck: there are no new messages in the trace.
My guess is that LineSearch algorithm gets stuck for some reason.
Could someone provide advice on how to better debug such cases where the LineSearch is stuck?
May be you have some ideas what the problem might be?
The text was updated successfully, but these errors were encountered:
Huh, good question. You don't have the example available to share, do you? I would guess there's some tolerance that's impossible to reach for your example.
Hi,
I am running LBFGS optimization algorithm with MoreThuente linesearch algorithm.
I track the execution of the algorithm by damping the output of the trace into the terminal.
In some cases (which are, fortunately, rare), the optimization just gets stuck: there are no new messages in the trace.
My guess is that LineSearch algorithm gets stuck for some reason.
Could someone provide advice on how to better debug such cases where the LineSearch is stuck?
May be you have some ideas what the problem might be?
The text was updated successfully, but these errors were encountered: