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
In LassoCV, ElasticNetCV, ... we have two parameters, alphas and n_alphas, that have the same purpose, i.e. determine the alpha values to test.
I'd be in favor of deprecating n_alphas and make alphas accept either an int or an array-like, filling both roles.
I chose to keep alphas and not the other because RidgeCV has alphas and no n_alphas (although alphas can't be an int there, maybe an enhancement to make ?), and the most recent param of this kind, threshold in TunedThresholdClassifierCV, follows this naming pattern and fills both roles.
The text was updated successfully, but these errors were encountered:
@jeremiedbb Just created a PR, I believe it is linked. I followed the contributing guidelines to the best of my abilities, but happy to make any changes!
In LassoCV, ElasticNetCV, ... we have two parameters,
alphas
andn_alphas
, that have the same purpose, i.e. determine the alpha values to test.I'd be in favor of deprecating
n_alphas
and makealphas
accept either an int or an array-like, filling both roles.I chose to keep
alphas
and not the other becauseRidgeCV
hasalphas
and non_alphas
(althoughalphas
can't be an int there, maybe an enhancement to make ?), and the most recent param of this kind,threshold
inTunedThresholdClassifierCV
, follows this naming pattern and fills both roles.The text was updated successfully, but these errors were encountered: