New optimizer class #879
Closed
MatteoRobbiati
started this conversation in
General
Replies: 1 comment 1 reply
-
Thanks @MatteoRobbiati, related to #235 and potentially #657, here some comments:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was thinking about the current status of the
optimizer
module.Current optimization status
We use the
optimize
function, in which we can set themethod
variable. This function calls different tools according to the selected method. The function's structure is the following:method
scipy.optimize.minimize
, setmethod
directly inside theminimize
function and use it.cmaes
algorithm.I think this procedure can lead to some misunderstanding, especially as a consequence of the fact that the default options for the optimizer are the same of
scipy.optimize.minimize
. It is clear the utility now, becauseminimize
covers the 99% of the choices, but I think we are going to have a larger spectrum of possibilities.New purposed structure
I think it can be useful to think about a general
Optimizer
class, withset_options
andoptimize
methods, in which we can customize the argument setting and the calling function. I try to explain in the following:Any suggestions/complains?
Roadmap
I purpose the following drawing as guideline for the future implementations.
Beta Was this translation helpful? Give feedback.
All reactions