[Rd] Preferred way to include internal data in package?
cboettig at gmail.com
Mon Aug 4 18:38:37 CEST 2014
I would think that putting them in an appropriate subdirectory in inst
might be preferable, e.g. inst/examples, and then reading the data in
with ?system.file where necessary?
(I have frequently been instructed that data ought not be mixed with
code, as it makes both code and data harder to read, maintain, or
reuse. On the other hand, if there's a good reason to avoid
system.file for this, I'd be happy to be enlightened so that I too
could improve my practices).
On Mon, Aug 4, 2014 at 9:23 AM, Gábor Csárdi <csardi.gabor at gmail.com> wrote:
> If you want to keep it as text, then you can just put it in the code:
> mydata <-
> "Mazda RX4",21,6,160,110,3.9,2.62,16.46,0,1,4,4
> "Mazda RX4 Wag",21,6,160,110,3.9,2.875,17.02,0,1,4,4
> "Datsun 710",22.8,4,108,93,3.85,2.32,18.61,1,1,4,1
> and then you can read from it via text connections:
> On Mon, Aug 4, 2014 at 12:11 PM, Keirstead, James E
> <j.keirstead at imperial.ac.uk> wrote:
>> I saw that, but actually I was wondering if there was a more general method. I’d like to use plain text files if I can, instead of Rda files, since they’re easier to maintain (and it’s a small file).
>> On 4 Aug 2014, at 16:30, Jeroen Ooms <jeroen.ooms at stat.ucla.edu> wrote:
>>>> I’m developing a package and would like to include some data sets for internal use only, e.g. configuration parameters for functions. What is the preferred way of doing this? If I put them in data/, then R CMD check asks me to document them but I’d prefer it if they floated beneath the surface, without the users awareness.
>>> Perhaps in sysdata.rda. See "Writing R Extensions".
>> R-devel at r-project.org mailing list
> R-devel at r-project.org mailing list
UC Santa Cruz
More information about the R-devel