Skip to content
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

Issue34 #48

Merged
merged 14 commits into from
Mar 31, 2024
Merged

Issue34 #48

merged 14 commits into from
Mar 31, 2024

Conversation

bcjaeger
Copy link
Collaborator

puts construction of oobag_denom exclusively in grow, fixing #34

bcjaeger added 14 commits March 30, 2024 08:43
no change to the oobag denominator during tree growing yet, but this
commit sets up the inputs of grow functions for that.
because oobag denom is fixed after trees are grown
Now that oobag denom is managed by grow, these pointers are not needed. The only feature impacted by this change is computation of oobag prediction accuracy every X trees. It used to use dynamic oobag denom but now it's static, which means prediction accuracy looks much worse with smaller tree counts. This change makes no meaningful difference in forests other than computational efficiency during prediction.
this can occur is sample fraction is close to 1. This input doesn't matter when prediction is happening, but we need a vector to match cpp type expectations and avoid R crash.
using these functions with high values of sample fraction risks getting an empty value for oobag rows, which would end up getting filled with a dummy vector of length 1. This should not happen is sample fraction is kept at or below 9/10 and sample size is reasonable.
re-do initialization at time of prediction if the tree isn't grown with oobag error.
@bcjaeger bcjaeger merged commit 7f9462f into main Mar 31, 2024
10 checks passed
@bcjaeger bcjaeger deleted the issue34 branch March 31, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant