[R-pkg-devel] implications of staged install for data processing packages
||or|@n@o@w@|d @end|ng |rom gm@||@com
Fri Jun 28 10:16:57 CEST 2019
I ran into trouble with the changes starting to come in with R3.6 stemming
from the new staged installation, which checks and errors on hard coded
paths in R code. I understand there is an opt out, but still want to know.
here's the blog post:
I have several packages which look like that:
1. large messy dataset stored on disk as `filename`, maybe a csv.
2. R package has a function `clean(filename)` which reads the data and
brings it into useable form
3. R package does analysis
4. R package exports results
`filename` is hard coded. What is the proper way to do this instead? Should
I store the inital raw data inside the R package in `/inst`? These things
are typically very large, so I like to decouple the raw data from the
package (easier to share).
thanks for any suggestions!
[[alternative HTML version deleted]]
More information about the R-package-devel