-
Notifications
You must be signed in to change notification settings - Fork 1.9k
More trainer related naming alignment #2938
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
Comments
@shauheen would this be a candidate for Project 13? |
In general, it seems there isn't a 1:1 mapping between trainer and model parameter types.
However, there are some discrepancies that exists. Whenever possible we should align the trainer and model parameter types. Listing some of the trainers where we can fix this :
|
Update:
Here is a summary of the Trainer and ModelParameter class names
|
For multi-class LR trainer and its model, we will different names in #2976. Looks like they don't need
We can NOT have LogisticRegressionMulticlass because LogisticRegression is binary classification only. |
Take another pass over the trainers and the model parameter types, and align them, because now we have:
LogisticRegressionMulticlassClassificationTrainer
butMulticlassLogisticRegressionModelParameters
.I think following the same principles on the ModelParams might make them more relatable; so change
MulticlassLogisticRegressionModelParameters
toLogisticRegressionMulticlassModelParameters
The text was updated successfully, but these errors were encountered: