Generally you will want to use an application directory for storing these
files (a la rappdirs) and, importantly, allow the user to consent to these
files being downloaded and installed, which should not be done on load.
On Sun, Mar 12, 2023 at 13:24 Ronald Bergmann wrote:
> Hi
This warning says to update to v2 of the action from r-lib:
Warning: r-lib/actions/setup-r@v1 is deprecated. Please update your
> workflow to use the 'v2' version. Also look at the examples at
> https://github.com/r-lib/actions/tree/v2/examples because '@v2' workflows
> are much simpler than 'v1'
Hello,
I noticed a strange error pop up for R-devel (2020-06-12 r78687) check on
travis:
https://travis-ci.org/github/grunwaldlab/poppr/jobs/697831376#L4653-L4654
* checking Rd cross-references ... WARNING
Non-file package-anchored link(s) in documentation object 'aboot.Rd':
Options are not persistent between sessions unless the user wants them to
be. You can have users set the options in their .Rprofile either in the
working directory of the project or their home directory. This is the
method that the {usethis} package has for storing default names. The only
downside
I've had a problem like this before and I also thought that it was due to
some weird magic in OpenMP, but it turned out to be a fence-post error on
my part [1]. Unfortunately, the valgrind output is not as helpful as
something like ASAN. My suggestion would be to go through that section of
the
/path/to/poppr
>
> Suggestion:
>
> Add a blank line before
>
>Examples of analyses are available in a primer written by Niklaus
> J. Grünwald, Zhian N. Kamvar, and Sydney E. Everhart at
> \url{http://grunwaldlab.github.io/Population_Genetics_in_R}.}
>
Zhian
On Tue,
y have to make
> more drastic omissions or additions in order for compilation to succeed.
>
> On Wed, 19 Jun 2019 at 12:37 am, Zhian Kamvar wrote:
>
>> Hello,
>>
>> I'm having a really strange problem that I cannot reproduce locally
>> (Ubuntu
>> bionic)
Hello,
I'm having a really strange problem that I cannot reproduce locally (Ubuntu
bionic) or on Rhub. I've run into an issue where the R package manual is
failing only on this platform with ancient LaTeX runes that I struggle to
decipher [0]
> * checking PDF version of manual ... WARNING
>
You can add
#' @noRd
to those functions and roxygen2 will not generate .Rd files for those
entries.
On Mon, Aug 13, 2018 at 2:08 PM Eggleston, Barry wrote:
> Hello,
>
> I am working through my first submission and making good progress with the
> CRAN review system, but now I need to
sage-
> From: R-package-devel [mailto:r-package-devel-boun...@r-project.org] On
> Behalf Of Zhian Kamvar
> Sent: 10 August 2018 12:26
> To: Alexandre Courtiol
> Cc: R-list Package Devel
> Subject: Re: [R-pkg-devel] Printing examples conditionally on another
> package in Suggests
>
equireNamespace("some.package", quietly = TRUE))
> print(x)
> Print("Hi")
> Print("Hello")
> Print("Goodbye")
>
>
>
> On Fri, 10 Aug 2018 at 12:33, Zhian Kamvar wrote:
>
>> Mainly, I would like to see the value printed after the print
Hello,
I know it's good practice to use
if (require("some_package")) {
# some code that needs some_package
}
In R examples that needs a package listed in Suggests.
The problem with this approach is that if there are any print statements
within this structure, then they only get printed after
Copy this output into a file called .Rbuildignore at the top of the directory:
> .DS_Store
> .RData
> .Rhistory
> ._*
> .gitignore
> .travis.yml
> R/.DS_Store
> R/._*
> data/.DS_Store
> data/.Rapp.history
> man/.Rapp.history
> vignettes/._*
> vignettes/.gitignore
> .Rproj.user
>
Using dplyr like that is for exploratory data analysis. You'll want to refer to
dplyr's "Programming with dplyr" vignette for using dplyr in a package:
https://cran.r-project.org/web/packages/dplyr/vignettes/programming.html
Perhaps you could add a Makefile with a rule that compiles the vignettes into
the inst/doc directory? This might avoid the build process.
-
Zhian N. Kamvar, Ph. D.
Postdoctoral Researcher (Everhart Lab)
Department of Plant Pathology
University of Nebraska-Lincoln
> On Apr 20, 2017, at
The way several packages have implemented OpenMP is to wrap it in pre-compiler
statements i.e.:
// Include openMP if the compiler supports it
#ifdef _OPENMP
#include omp.h
#endif
This way, all compilers can build the code and those that have OpenMP (even
modified versions of clang:
16 matches
Mail list logo
