Don't coerce sparse data to non-sparse during predict() #950
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 bug was first reported here: https://community.rstudio.com/t/predict-not-working-with-ranger-model-when-using-sparse-data/163352/7
When you call
predict()
you eventually get to runprepare_data()
, which didn't know about thealllow_sparse_x
encoding so it would try to turn it into matrices/data.frames. This was bad for 2 reasons. First we are losing some performance. Secondly, in the case of the ranger method, it wants the data as a data.frame which a sparse data can't be turned into, yielding the error seen below.Main
This PR