You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think Param groups have value in certain cases, where parameters really belong together tightly (i.e. filter params), but would make sense to be changed independently (so that the nested set_params call would be required.
Otherwise, maybe there are other options:
Group related parameters using namedtuples. Downside: Does not allow nested set_params
Write out all parameters, but provide new set_... methods to partially set the values. Users would then not set all parameters in the init, but chain set_... calls. This could make Algorithms with large number of Parameters much more readable without including additional nesting.
From a user side, users could also just group parameters into multiple dicts, before passing them to the init and then use dict unpacking. This could also help to make code more readable.
Bottom-line, I think a ParameterGroup would only add complexity that is rarely needed. But I will keep the issue open for further consideration
No description provided.
The text was updated successfully, but these errors were encountered: