BUGFIX for sparse expression matrices #20
Merged
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.
Hi,
arboreto seems to nominally support sparse matrices (according to the docs/docstrings),
however I ran into a couple of errors:
len()
andnp.delete()
doesn't work on sparse matricessklearn.ensemble.GradientBoostingRegressor
can handle sparse matrices forX
,but
y
has to be dense!Except for potential memory saving, this unfortunately doesn't speed things up much. Not an expert in boosting, but I don't see how to exploit sparsity for speed in boosting, so that's expected I guess.
Actually sparse matrices slow down
GradientBoostingRegressor
quite a bit.This seems to be due to some conversions of sparse matrices internally (csc vs csr):
GradientBoostingRegressor
wants crsGradientBoostingRegressor
it does some weird csr->csc conversion internally. Not sure whats going on there.So maybe it makes the most sense in the future to have the original expression matrix sparse, pull out the transcription factor matrix and target gene vector and cast them into dense matrices (the tf-matrix shouldnt be too large either, around 2000 columns)
Let me know what you guys think!