returned support for sparse matrixes (which was depricated) #310
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
fixed previous sparse matrix processing addings remove temp files for training
|
@aksnzhy @etveritas hi! any updates with it? |
|
@aksnzhy @etveritas Any updates on this? |
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.
In current version support of sparse matrixes was unexpectedly depricated and data conversion was switched to
DMatrixfunction only, which returns this message if we try to add sparse matrix as input data:[
xlearn/python-package/xlearn/data.py
Line 42 in 499a183
As previous interface included support and conversion of sparse matrixes, it would be a good point to keep it working.
Also it might be that
DMatrixfunction itself could be performed to be able to solve this issue.