On 23/03/16 10:08, Dirk Eddelbuettel wrote:
Note that there is a reasonable discussion in Writing R Extensions, but as
always, you have to find it first.
Fortune nomination!
cheers,
Rolf Turner
--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-759
Kevin,
The inst/ directory gives a good handle to pass arbitrary directory layouts
of your choosing through. You just need to avoid inst/data as it would clash
with an existing data/ directory.
I think I have seen
inst/rawData
inst/extData# as in 'external data'
and of
You can leave them in R/ (and write them as functions) but use
.Rbuildignore to exclude them from the distributed package. People can use
the source, eg github, to regenerate the package and all its data if they
wish. This way, R CMD check and tests can cover them easily while
developing.
However,
On Tue, 2016-03-22 at 08:52 -0400, Kevin Coombes wrote:
> I'm currently developing an R package that includes a small data set
> along with the functions that I want to export. I have an R script that
> generates the data set; the computation time is long (well, relative to
> the size of the dat
Hi,
I'm currently developing an R package that includes a small data set
along with the functions that I want to export. I have an R script that
generates the data set; the computation time is long (well, relative to
the size of the data set). So, my plan is to run the script and save()
the d
