Skip to content

Parameter name Consistency in FastTree #2375

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

Closed
srsaggam opened this issue Feb 1, 2019 · 5 comments · Fixed by #2753
Closed

Parameter name Consistency in FastTree #2375

srsaggam opened this issue Feb 1, 2019 · 5 comments · Fixed by #2753
Assignees
Labels
API Issues pertaining the friendly API
Milestone

Comments

@srsaggam
Copy link
Member

srsaggam commented Feb 1, 2019

public Double LearningRates = Defaults.LearningRates;

Should this be LearningRate? The Options have it named wrongly.

The named parameter for the FastTree is named correctly as learningRate.

double learningRate = Defaults.LearningRates)

It would be great if you can check the same with all the trainers and transforms. i.e the named parameters(in the method) resemble the Actual Property name(in the options). In my opinion these all should be consistent. In case of named params (camel case) and for actual Property (of course is pascal case)

@srsaggam
Copy link
Member Author

srsaggam commented Feb 1, 2019

@srsaggam
Copy link
Member Author

srsaggam commented Feb 1, 2019

@abgoswam Can you please take a look at this? and verify the same for all other trainers available in the catalog.

@srsaggam srsaggam changed the title Parameter name wrong Parameter name wrong in FastTree Feb 1, 2019
@srsaggam srsaggam changed the title Parameter name wrong in FastTree Parameter name Consistency in FastTree Feb 1, 2019
@justinormont
Copy link
Contributor

We should go one step further and take up the larger task of verifying a unified naming scheme for all parameters across all components before the v1.0 release. After the release renaming parameters will be difficult.
/cc @glebuk

@abgoswam
Copy link
Member

abgoswam commented Feb 1, 2019

Also related to #2172 to bring consistency in naming convention.

@Ivanidzo4ka Ivanidzo4ka added the API Issues pertaining the friendly API label Feb 14, 2019
@wschin wschin self-assigned this Feb 27, 2019
@wschin
Copy link
Member

wschin commented Feb 27, 2019

It will be a part of #2617.

@wschin wschin mentioned this issue Feb 27, 2019
4 tasks
@shauheen shauheen added this to the 0319 milestone Mar 5, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
API Issues pertaining the friendly API
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants