Skip to content
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

Improve consistency in parameter names #257

Closed
bellet opened this issue Oct 30, 2019 · 0 comments · Fixed by #324
Closed

Improve consistency in parameter names #257

bellet opened this issue Oct 30, 2019 · 0 comments · Fixed by #324

Comments

@bellet
Copy link
Member

bellet commented Oct 30, 2019

It would be nice to follow a consistent naming convention for parameters and be as consistent as possible with sklearn. For instance:

  • In supervised versions of weakly supervised algorithms, num_constraints should be renamed n_constraints, num_chunks to n_chunks
  • In LMNN, the parameter k could be renamed n_neighbors like in sklearn's KNeighborsClassifier
  • There is also tol and convergence_threshold which are both used to refer to optimization tolerance (we should always use tol which is quite standard, cf `scipy.optimize)
perimosocordiae pushed a commit that referenced this issue Jun 21, 2022
* Rename number_constrains to n_constraints

* Renamed num_chunks to n_chunks

* LMNN k parameter renamed to n_neighbors

* Replaced all 'convergence_threshold' with 'tol'

* Fix tests

* Fixed more test regarding rename of variable

* Warnings for n_constrains

* Add all warnings regarding n_constrains

* Deprecation warnings for n_chunks

* Add deprecation warn to n_neighbors

* Add convergence_threshold warnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant