-
-
Notifications
You must be signed in to change notification settings - Fork 192
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
Importance calculation takes too much memory and time #2
Comments
mnwright
pushed a commit
that referenced
this issue
Oct 12, 2015
mnwright
pushed a commit
that referenced
this issue
Oct 12, 2015
mnwright
added a commit
that referenced
this issue
Oct 12, 2015
Done. Thanks. |
Great, thanks. |
mnwright
pushed a commit
to rcannood/ranger
that referenced
this issue
Oct 23, 2019
mnwright
pushed a commit
to rcannood/ranger
that referenced
this issue
Oct 23, 2019
mnwright
added a commit
to rcannood/ranger
that referenced
this issue
Oct 23, 2019
mnwright
pushed a commit
to rcannood/ranger
that referenced
this issue
Oct 23, 2019
structured tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Computing importance (all kinds) in ranger involves first creating a numTrees x numFeatures matrix (made of
variable_importance
vectors in each tree object), and then averaging it by row, which has a substantial impact on memory use and speed for large numTrees; ranger should just accumulate those values in place, thus using at most numFeatures x numThreads memory.The text was updated successfully, but these errors were encountered: