-
Notifications
You must be signed in to change notification settings - Fork 23
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
ranger.unify fails on large models #13
Comments
@maksymiuks Any ideas how I might address this? Thanks again. |
@yovizzle I'm on my way to find a solution |
@maksymiuks great, thank you.
…On Wed, 21 Apr 2021, 3:29 am maksymiuks, ***@***.***> wrote:
@yovizzle <https://github.com/yovizzle> I'm on my way to find a solution
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNURENULLOEISDRCZ6EXS3TJW2WVANCNFSM42UJBFQA>
.
|
@maksymiuks Any updates on this? We'd love to make use of this package! |
@yovizzle hi! I've identified the problem with ranger.unify however I'll have time to rebuild it in the second part of June/early July. I'll keep you posted |
Awesome, thanks for the update!
…On Fri, 11 Jun 2021, 10:27 am maksymiuks, ***@***.***> wrote:
@yovizzle <https://github.com/yovizzle> hi!
I've identified the problem with ranger.unify however I'll have time to
rebuild it in the second part of June/early July. I'll keep you posted
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNURELVZ675U4I3MGEWLF3TSFJ57ANCNFSM42UJBFQA>
.
|
Hi @maksymiuks , just checking back to see how this is looking. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
We are training a large random forest model (rf object size is ~270mb) on a large dataset (dim 1,670,000 x 267, object size 3.3gb) and are hitting errors. The machine tested on has 96 cpus/354Gb ram.
Here is a repro.
We then got this error:
Any ideas as to what may be causing this issue? Is it a limitation of the current implementation of the package, or perhaps an issue related to our R environment?
Thanks.
The text was updated successfully, but these errors were encountered: