Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Efficient line search in optimizer #153

Open
mhmukadam opened this issue Apr 11, 2022 · 2 comments
Open

Efficient line search in optimizer #153

mhmukadam opened this issue Apr 11, 2022 · 2 comments
Labels
enhancement New feature or request refactor Refactor library components

Comments

@mhmukadam
Copy link
Member

Current implementation is not friendly for the development of line search and will need some refactoring.

@mhmukadam mhmukadam added enhancement New feature or request refactor Refactor library components labels Apr 11, 2022
@tvercaut
Copy link

tvercaut commented Jul 26, 2024

I found the lack of line search to be a real bottleneck for the applications we have been looking at so far. For those where differentiability of the solution is not critical, we can rely on scipy.optimize.least_squares and exploit autograd from pytorch throughtorch.autograd.functional.jacobian however this also means having to go back to the CPU which may slow things down depending on the problem size.

Are there any plans to introduce line search to bridge the gap in convergence reliability with scipy, ceres and the like?

@luisenp
Copy link
Contributor

luisenp commented Jul 26, 2024

Hi @tvercaut. This feature is a the top of our wish list, but, unfortunately, we are extremely time constrained with other projects at the moment and don't have time for active development on Theseus. We don't have a concrete time line for this at the moment, really sorry about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactor Refactor library components
Projects
None yet
Development

No branches or pull requests

3 participants