Dearfriends , with your help I'm rapidly improving package development. When
documenting data, I seem to be helped mpst by making the rda directly from
RStudio via file, new file, R documentation then choosing data. However, my
data files have a lot of params, so I thought I might use
My current set-up in a variety of packages is that every parallelizable
function has a BPPARAM= argument. This makes it explicit about which steps are
being parallelized. Requiring users to respecify BPPARAM= in each function
isn’t as annoying as you’d think, because not many steps are actually
Please report.
Best,
Uwe Ligges
On 11.01.2019 22:15, Sam Albers wrote:
Oh you are totally right. And similarly, an .rds file bonks with R CMD build:
$ R CMD build foo.rds
* checking for file 'foo.rds/DESCRIPTION' ... OK
* preparing 'foo.rds':
* checking DESCRIPTION meta-information ... OK
*
Oh you are totally right. And similarly, an .rds file bonks with R CMD build:
$ R CMD build foo.rds
* checking for file 'foo.rds/DESCRIPTION' ... OK
* preparing 'foo.rds':
* checking DESCRIPTION meta-information ... OK
* checking for LF line-endings in source and make files and shell scripts
*
Hello,
I created a package for working with a new probability
distribution called unifed. The source code can be found at
https://gitlab.com/oquijano/unifed .
This distribution is suitable for GLMs. I have included a a
function called unifed in the package that returns a family that can
--- Begin Message ---
It looks like the ".rdata" in your package name is confusing R CMD BUILD into
thinking there is a .rdata file involved. Consider renaming it to "bcmaps.data"
or something similar.
-Original Message-
From: R-package-devel On Behalf Of Sam
Albers
Sent: Friday, 11
Hello all,
I am experiencing some issues with building a package that we are
hosting on GitHub. The package itself is quite large. It is a data
package with a bunch of spatial files stored as .rds files.
The repo is located here: https://github.com/bcgov/bcmaps.rdata
If we clone that package
Thanks a lot for your help - now it is fine!
BW
Troels
-Oprindelig meddelelse-
Fra: Iñaki Ucar
Sendt: 11. januar 2019 18:37
Til: Troels Ring
Emne: Re: [R-pkg-devel] NAMESPACE importFrom("stats", "uniroot")
See an example of usage here:
> Martin Maechler
> on Fri, 11 Jan 2019 09:44:14 +0100 writes:
> Michael Chirico
> on Fri, 11 Jan 2019 14:36:17 +0800 writes:
>> Identified as root cause of a bug in data.table:
>> https://github.com/Rdatatable/data.table/issues/3267
>> On my machine,
On Fri, 11 Jan 2019 at 17:31, Troels Ring wrote:
>
> Dear friends - I'm slowly learning to make packages in RStudio and it seems
> impressive. I managed now to have my acidbase package pass the check-package
> test with this result
>
>
>
> > checking R code for possible problems ... NOTE
>
>
Dear friends - I'm slowly learning to make packages in RStudio and it seems
impressive. I managed now to have my acidbase package pass the check-package
test with this result
> checking R code for possible problems ... NOTE
pH_general: no visible global function definition for 'uniroot'
Thanks for the report, fixed in R-devel (one gets NA_character_ as a
result and the path is treated as non-existent, so with a warning or
error when requested via mustWork argument).
Best,
Tomas
On 12/7/18 7:10 PM, Yihui Xie wrote:
Hi,
I just noticed normalizePath(NA_character_) returns
> Michael Chirico
> on Fri, 11 Jan 2019 14:36:17 +0800 writes:
> Identified as root cause of a bug in data.table:
> https://github.com/Rdatatable/data.table/issues/3267
> On my machine, strtoi("", base = 2L) produces NA_integer_
> (which seems consistent with
13 matches
Mail list logo
