Conversation
Code Coverage SummaryResults for commit: 6d7ce0e Minimum allowed coverage is ♻️ This comment has been updated with latest results |
FilippoOlivo
left a comment
There was a problem hiding this comment.
Hi @dario-coscia, thank you for the PR. Could you please provide an example of how this new feature should be useful?
Moreover I am not convinced anymore about the need of both OptimizerInterface and TorchOptimizer. Specifically, creating a new optimizer from scratch, without inheriting from torch.optim is not straightforward and requires a lot of effort in my opinion. In this regard, I think we can combine together the two classes in a single one, called, for example, PinaOptimizer
4fdf1ae to
d04f75a
Compare
I agree with @FilippoOlivo |
|
Hi @GiovanniCanali @FilippoOlivo, This PR is not ready for review yet, but here’s the planned roadmap: Roadmap1. Restructure Optimizer / Scheduler Interface
2. Introduce Second-Order Optimizers
This roadmap should provide a clear view of the upcoming changes and priorities. |
* adding connectors for optimizers/schedulers * simplify configure_optimizers logic
Some updates on this…
|
|
I think we can start adding second order optimizers/new optimizers |
Description
This PR fixes #618.
Checklist