Use sparse vectors in PAV backend #379
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #379 +/- ##
==========================================
+ Coverage 99.38% 99.38% +<.01%
==========================================
Files 59 59
Lines 3727 3738 +11
==========================================
+ Hits 3704 3715 +11
Misses 23 23
Continue to review full report at Codecov.
|
|
Kudos, SonarCloud Quality Gate passed!
|
This was referenced Feb 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the way the PAV backend stores the true labels and scores returned by source projects during training. They are now kept as (SciPy) sparse vectors, which saves a significant amount of RAM. Training times and suggestion results are the same as before.
Part of #377