-
Notifications
You must be signed in to change notification settings - Fork 9
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
LargeN usage #44
Comments
@duccioa Yes, I think your analysis is correct. I'll try to prepare a fix in a branch during this week. May I ask you to review the changes when I'm ready? |
Roger (If I may call you by your name), I would be honored. I am a big fan of your work in the r-spatial community. |
@duccioa Thanks very much! I've merged into the main branch now. |
Submitted to CRAN. |
freebsd-git
pushed a commit
to freebsd/freebsd-ports
that referenced
this issue
Oct 9, 2023
- Take maintainership ChangeLog: Address LargeN usage: r-spatial/classInt#44
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I am a bit confused by the usage and the documentation of the parameters
largeN
inclassIntervals
and I would be grateful for some guidance.The documentation says
In
classIntervals()
,largeN
is used as following:Where
nobs <- length(unique(var))
.My understanding is that
largeN
is the threshold above which we considervar
to require sampling.What I find difficult to understand is that then
largeN
is not used to compute the sampling but we use the value 3000.3000 is also the default of
largeN
, but the two values are not used in the same way. One is used as a threshold and the other one is hard coded to calculate the sample size.This also gives a problem when
length(var) < largeN
:Created on 2023-08-22 by the reprex package (v2.0.1)
Shouldn't it be something like
nsamp <- min(largeN, nobs * samp_prop)
?Thank you very much for your time.
Duccio
The text was updated successfully, but these errors were encountered: