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

Misc estimator fixes #161

Merged
merged 10 commits into from
Sep 28, 2020
Merged

Misc estimator fixes #161

merged 10 commits into from
Sep 28, 2020

Conversation

timokau
Copy link
Collaborator

@timokau timokau commented Sep 25, 2020

Description

Cleaning up & pulling out this weeks changes from #116.

Motivation and Context

I'm trying to avoid piling up too many unreviewed "fixup" commits in #116. These changes are ready now, so I think its better to get them in now.

How Has This Been Tested?

Ran the pre-commit checks and the test suite for every commit.

Does this close/impact existing issues?

Impacts #94.

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.

@kiudee
Copy link
Owner

kiudee commented Sep 25, 2020

I wonder why the git fetch fails on travis - I will try restarting it.
edit: It still fails to fetch the pull request (cloning the repo works). Unsure what the cause could be - so far I did not find relevant issues online.

@timokau timokau force-pushed the misc-estimator-fixes branch from 52fff17 to 685cdb7 Compare September 25, 2020 17:17
@kiudee
Copy link
Owner

kiudee commented Sep 26, 2020

Seems to have fixed itself.

kiudee
kiudee previously approved these changes Sep 26, 2020
Merge can only be called on multiple layers, and in the case of
length-one rankings there will only be one layer.
Required by the scikit-learn estimator API for easier fit-predict
chaining.
This would previously fail due to a division by 0 if the ranking is
0-based and consists of only one object.

Concretely, this would fail the "check_fit2d_1sample" check from the
scikit-learn estimator test suite if we generate 0-based rankings.
@timokau
Copy link
Collaborator Author

timokau commented Sep 28, 2020

For some reason GitHub told me the branch is outdated, even though there were no conflicts. So I did a trivial rebase, please re-approve.

@timokau timokau merged commit 61864e2 into kiudee:master Sep 28, 2020
@timokau timokau deleted the misc-estimator-fixes branch September 28, 2020 11:56
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