scipy.optimize.line_search returns None
See original GitHub issueI’m trying to use the scipy.optimize.line_search
command but instead of giving me the three values promised by the docs, it gives me (None, 13, 0, None, 853161.73010506318, None)
with the optimal alpha nowhere to be found.
Issue Analytics
- State:
- Created 9 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
scipy.optimize.line_search — SciPy v1.9.3 Manual
The line search accepts the value of alpha only if this callable returns True . If the callable returns False for the step...
Read more >scipy.optimize.minimize line search parameters - Stack Overflow
I tried to do this by changing the default values in line_search , but it had no effect. Here is a simple example...
Read more >Line Search Optimization With Python
In this tutorial, you will discover how to perform a line search optimization in Python. After completing this tutorial, you will know:.
Read more >optimize/linesearch.py · stream/scipy - Gemfury
Returns ------- stp, f_count, g_count, fval, old_fval As in `line_search_wolfe1` gval : array Gradient of `f` at the final point """ if gfk...
Read more >Potential BUG in Scipy Optimize · Issue #9696 - GitHub
Hi! I have encountered an issue with scipy.optimize.minimize, which returns the following error: ValueError: The truth value of a Series is ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The documentation does not mention it, but
None
means that a suitable step length was not found. Can happen e.g. if the direction is not a descent direction.@pv This issue is a bit old. Not sure if there are still documentation issues here, if so I’m happy to resolve. Are there still remaining issue(s) to resolve? The first 2 issues listed by @argriffing with links have been merged and the referenced PR has also been merged.