-
Notifications
You must be signed in to change notification settings - Fork 30
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
Get better demo data and code #8
Comments
I could probably contribute some Banksia and Hakea data from SW Australia if that would help? |
I was thinking something with two species on a relatively small island, maybe two environmental layers. Something a lot like the ahli/allogus data that's already in there, but with more occurrence points. Size of test data gets to be a real issue when you're submitting packages to CRAN. |
What sort of island size are we talking? Depending on when I can get my Brachymeles manuscript shipped off, there might be a species pair that would work well for one of the islands in the Philippines. |
It's more about file size than geographic size, so of course resolution can be a huge component of that. Actually, the ideal situation would be: A small clade (maybe ~5 species) Ideally all would compress into about 4 MB. |
Perhaps we should also include some simulated data? Then we can make it whatever size we want, and make it demonstrate whatever functionality we want. Plus it would probably make sense to have some simulated data for making testthat tests.. |
Yeah, actually that might be the most size-efficient way to do it. We could set up some code to specify some simple niches and a tree for a small clade of organisms, and then for "environments" have some spatially-autocorrelated random fields in a raster stack. That way we could just generate the demo data on the fly as we write example code, storing nothing. That is, of course, as long as the demo data can be simulated quickly. CRAN also has a requirement about runtime for sample code. |
Okay so we may not want to do this bit on the fly, but we can simulate spatially autocorrelated rasters and zip those up as part of the sample data. Simulating the species with base R code and stuff we're already importing should be significantly easier. Based on code from here: http://santiago.begueria.es/2010/10/generating-spatially-correlated-random-fields-with-r/ Along with some janky post-processing to generate correlations between predictors. |
I've actually attached some demo data to the Cranify branch. It's a clade of Iberian lizards and a low-res European set of Worldclim layers. I'm rewriting demo code now to work with the included data set. |
No description provided.
The text was updated successfully, but these errors were encountered: