Hi,
I'm going to start by summarizing the suggestions (for where to put the
script) that have been presented so far:
[1] in the /demo directory
[2] in /inst/SOMETHING, where Dirk lists four possible values for SOMETHING
[3] in /R , but hidden using .Rbuildignore
[4] in the Example section of a
Dear Kevin,
I would convert the script into a function and add it to the R folder. This
makes it easy to document the script using the standard R help files. Then
add the function to the examples in the helpfile of the data in a
\dontrun{}. Then it is clear to to user how the data was generated.
On Tue, 22 Mar 2016, Kevin Coombes writes:
> 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)
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
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
