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

Remove threshold instances #149

Merged
merged 2 commits into from
Aug 3, 2020

Conversation

timokau
Copy link
Collaborator

@timokau timokau commented Aug 1, 2020

Description

The next part in the #116 saga: I'm starting to remove instance attributes that are not parameters. The first one is instance_thresholds, which doesn't look like a useful feature to me. There is two distinct use cases, one simply reduces the dataset size and the other picks a simpler model. I have removed the first and replaced the second by an explicit parameter.

Motivation and Context

Less surprising behavior and #116.

How Has This Been Tested?

Test suite and lints.

Does this close/impact existing issues?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

@codecov
Copy link

codecov bot commented Aug 1, 2020

Codecov Report

Merging #149 into master will increase coverage by 0.15%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #149      +/-   ##
==========================================
+ Coverage   57.62%   57.77%   +0.15%     
==========================================
  Files         113      113              
  Lines        6994     6960      -34     
==========================================
- Hits         4030     4021       -9     
+ Misses       2964     2939      -25     
Impacted Files Coverage Δ
csrank/choicefunction/cmpnet_choice.py 92.30% <ø> (+8.21%) ⬆️
csrank/choicefunction/ranknet_choice.py 90.24% <ø> (+9.39%) ⬆️
csrank/core/cmpnet_core.py 87.37% <ø> (-0.13%) ⬇️
csrank/core/ranknet_core.py 87.37% <ø> (-0.13%) ⬇️
csrank/discretechoice/cmpnet_discrete_choice.py 96.77% <ø> (+10.66%) ⬆️
csrank/discretechoice/ranknet_discrete_choice.py 93.75% <ø> (+9.96%) ⬆️
csrank/objectranking/cmp_net.py 96.87% <ø> (+10.38%) ⬆️
csrank/objectranking/list_net.py 89.38% <ø> (-0.10%) ⬇️
csrank/objectranking/rank_net.py 96.87% <ø> (+10.38%) ⬆️
csrank/core/pairwise_svm.py 91.30% <100.00%> (ø)

kiudee
kiudee previously approved these changes Aug 3, 2020
Copy link
Owner

@kiudee kiudee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the change, since it is much more explicit. Also the threshold_instances was hardcoded to 1e10, which is not good.

The threshold was not configurable and the behavior somewhat unexpected.
Its better to let the library user decide themselves.
If the library user wants to reduce the dataset, they can just do so
themselves. The current behavior is unexpected, even more so since the
threshold is not configurable.
@timokau
Copy link
Collaborator Author

timokau commented Aug 3, 2020

Skimmed the changes again before merging and noticed a small typo (wether instead of whether). Please re-approve.

@timokau timokau merged commit 41351a8 into kiudee:master Aug 3, 2020
@timokau timokau deleted the remove-threshold-instances branch August 3, 2020 13:42
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 this pull request may close these issues.

2 participants