Skip to content

Fix some NaN problems and a few other fixes. #42

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

Merged
merged 1 commit into from
Dec 15, 2020
Merged

Conversation

andreasnoack
Copy link
Member

Handle prediction at tree split points separately. Always use qr
factorization when solving the local system to avoid error when
the system is singular. Also fix a one-off error in the median
calculation in the KDTree implementation.

This fixes some of the issues mentioned in #28 though not all
of them. The solution is to error out informatively in some cases
when the local system becomes too small. I think the main remaining
item is to handle ties differently. I expect that we'd have to construct
the tree only based on unique elements but that is for a future PR.
For now, I've added the test cases with ties from #28 but marked
some of them with @test_broken.

@ararslan
Copy link
Member

Also looks like CI here is dead. Guess we'll have to migrate to GitHub Actions if we want to actually test things.

@andreasnoack
Copy link
Member Author

Thanks for the review. I'll handle the migration to GA.

factorization when solving the local system to avoid error when
the system is singular. Also fix a one-off error in the median
calculation in the KDTree implementation.
@andreasnoack
Copy link
Member Author

andreasnoack commented Dec 14, 2020

I've enabled GA and updated the PR with the recommendations.

Copy link
Member

@ararslan ararslan left a comment

Choose a reason for hiding this comment

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

Awesome work!

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