r-pkgs | Building R packages | Build Tool library

Following advice about NAMESPACE and External Data formatting/setup, I have:

A. My data files in mypackage/data/datafilename.RData

B. The data script as mypackage/R/data.R with data files individually named and described within that one file, having just changed "itemize" to "describe" and changing the format of those item lines:

C. I've document()-ed this, commit-pushed to github, and install_github reinstalled locally.

Help for the data files works:

But I can't access those data, whereas I can access data in other packages using the same method:

Can anyone think why this would be? NAMESPACE doesn't include these as exports:

But it's autogenerated by document() so that's arguably out of my control. By comparison, mapplots' NAMESPACE has exportPattern(".")

Environment for the package also doesn't include them, but I don't know if this is expected or not, based on lazy loading (which is true):

Any ideas welcome. I've tried data(gbm.auto:grids) with 1, 2 & 3 colons, to no avail. Based on the answer to this related question (also by me), I get the suspicion that there might be some issue whereby only the last named object in data.R is important/accessible?

usethis has been created since I've been updating this package and has use_data and create_package but I'm reluctant to try these out since ostensibly everything in my package should already be in order and I don't want to make things worse.

Thanks in advance. Reprex would be

My apologies in advance if this is an obvious question but I have searched both stack overflow and what have been otherwise very useful resources like R packages by Hadley Wickham or this blog and can not find an answer.

My issue occurs when trying to run build_vignettes() on my developed R package (myPackage). The vignette for the package (myPackage.Rmd) will create as expected using knit in RStudio but when I run build_vignettes(), I get the following error:

(This question is also asked at Github here)

After an upgrade of R to 4.0.2 tests fail because it seems, the algorithm of sort in testthat changed. The following shows, that base::sort() and browser() are fine in R 4.0.2 (See this question, why this check is added.):

I would like to use R objects (e.g., cleaned data) generated in one RStudio project in another RStudio project.

Specifically, I have multiple RStudio projects (that hold drake plans) that do various things for my thesis experiments (e.g., generate materials, import and clean data, generate reports/articles). I want to import objects (mainly data and materials) that I generated in these projects into another RStudio project that generates my thesis report. It seems to make sense to keep the individual experiments as separate projects (with separate git repositories) because they each have so many components.

At the moment I can see three ways of doing this:

1. Re-create the data cleaning process
   • But: this involves copy/paste, which I'd like to avoid, especially if things change upstream.
2. Access the relevant scripts/functions by changing the working directory
   • But: even if I used here it seems that this would introduce poor reproducibility.
3. Make the source projects into packages and make the objects I want to "export" into exported data (as per the data section of Hadley's R packages guide)
   • But: I'd like to avoid the unnecessary metadata, artefacts, and noise (e.g., see Miles McBain's "Project as an R package: An okay idea") if I can.

Is there any other way of doing this?

I am writing an R package, and started to include C code in it. Following instructions from here, under "getting started with .C()", I created a c function in src/, and an r wrapper to it, linking via the roxygen tag @useDynLib(, ).

However, after running devtools::document(), I get the following error:

I am writing a package for my use. I created objects of class marco, say.

Then I wrote some methods, like print.marco, plot.marco, etc, which I would like to be applied with print(obj) where class(obj) = "marco". In the NAMESPACE file (created with roxygen2::document()), these functions are simply exported as such and not as S3methodand are not recognized as such by sloop::is_s3_method.

I searched the internet and I can't find an answer or clear example. Following In Hadley Wickham's R packages in my R script I simply document the functions adding #' @export print.marco, etc.

A minimal example

I'm trying documenting datasets for a r-package as here http://r-pkgs.had.co.nz/data.html#documenting-data. Each data consist in single vectors and I wrote in each data1.R something like this:

I get this warning

My package will not install, either on my machine or on travis-ci.org. The only update from the version on CRAN is that I added a vignette. I have been following the examples of Rcpp - package and R-packages; compiled code.

The error is related to these prior questions but not a duplicate.

1. Q40922814 -- problem here was the use of both C and C++ code. I only use C++ code
2. Q36952571 -- I'm on Mac OS, so no access to ldconfig, though perhaps my problem is related.

from the package directory: