-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Fix an initial-value problem caused by unseen row/column #2525
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
Conversation
Can we have a test? |
As you wish. :) In reply to: 463012943 [](ancestors = 463012943) |
Codecov Report
@@ Coverage Diff @@
## master #2525 +/- ##
==========================================
+ Coverage 71.25% 71.26% +0.01%
==========================================
Files 798 797 -1
Lines 141252 141328 +76
Branches 16112 16118 +6
==========================================
+ Hits 100643 100720 +77
- Misses 36145 36146 +1
+ Partials 4464 4462 -2
|
test/Microsoft.ML.Tests/TrainerEstimators/MatrixFactorizationTests.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update LIBMF to have this fix. The problem is that when the largest row index in the training set doesn't match the number of rows in the specified matrix shape, rows' starting addresses may look like
[ptr_to_first_element_in_row_1, ptr_to_first_element_in_row_8, ptr_to_the_end_of_element_array, nullptr, nullptr]
but the correct value should be[ptr_to_first_element_in_row_1, ptr_to_first_element_in_row_8, ptr_to_the_end_of_element_array, ptr_to_the_end_of_element_array, ptr_to_the_end_of_element_array]
.Fixes #2488