-
Notifications
You must be signed in to change notification settings - Fork 68
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
Implementing a custom optimizer #441
Comments
I think MMA would be a great addition to JAXopt. If you do want to copy/adapt an existing implementation, consider using the implementation from nlopt, whose MIT license is compatible with the rest of JAXopt. |
Hi @shoyer, In the meantime, could you provide me with some pointers on key aspects of the JAXopt codebase that I should focus on for implementing a custom solver? Any insight into potential challenges or best practices during the integration process would be much appreciated as well. |
I haven't written much of the JAXopt code so I don't have any particular guidance. @mblondel may have thoughts to share here |
Hi @acse-itk22. We don't have documentation yet on writing a custom JAXopt-compatible solver. The best would be to mimic what we did in the sources. We'll try to add some documentation soon. |
Hi @mblondel, thank you for the response. I will have a closer look at the source code and will get back to you if I run into any issues. |
Hello,
I have been using jaxopt in my latest project related to structural optimisation and I'm highly impressed with its capabilities. I have come across a specific optimization method called Svanberg's Method of Moving Asymptotes (MMA), which is known to perform well in structural optimisation tasks. To fully leverage the benefits of jaxopt and maintain a consistent interface in my codebase, I would like to implement a custom optimizer based on Svanberg's MMA within the jaxopt framework.
I would greatly appreciate your guidance on the following aspects:
Thanks in advance!
The text was updated successfully, but these errors were encountered: