Re: [R-pkg-devel] Warning: parse error in file 'Rraven-Ex.R'

2020-02-05 Thread Uwe Ligges
On 05.02.2020 04:44, Jeff Newmiller wrote: In your examples. On February 4, 2020 5:53:08 PM PST, Marcelo Araya Salas wrote: Hi all I got this error from CRAN tests: Warning: parse error in file 'Rraven-Ex.R': '\.' is an unrecognized escape in character string starting ""\." ... Where

Re: [R-pkg-devel] CXX14 not defined on Windows

2020-02-05 Thread Ralf Stubner
On Tue, Feb 4, 2020 at 5:51 PM Guido Kraemer wrote: > I have also set `~/.R/Makevars.win` as suggested in the manual "Writing > R extensions", Section 1.2.5 "Using C++14 code". What exactly do you have in src/Makevars.win? Just the simple CXX_STD = CXX14 or the more complex set-up from the end of

Re: [R-pkg-devel] CXX14 not defined on Windows

2020-02-05 Thread Dirk Eddelbuettel
On 5 February 2020 at 11:47, Ralf Stubner wrote: | On Tue, Feb 4, 2020 at 5:51 PM Guido Kraemer wrote: | > I have also set `~/.R/Makevars.win` as suggested in the manual "Writing | > R extensions", Section 1.2.5 "Using C++14 code". | | What exactly do you have in src/Makevars.win? Just the simp

[R-pkg-devel] "found non-ASCII strings" with save(version = 2)

2020-02-05 Thread Vincent Arel-Bundock
Hi everyone, My `countrycode` package ships with two data frames of characters in several languages: codelist and codelist_panel. I converted all strings to UTF-8 using the `enc2utf8` function, but I also tried several other ways, with the stringi package, etc. As far as I can tell, the string

[R-pkg-devel] Winbuilder 'experimental' toolchain 4-5x slower than all other architectures

2020-02-05 Thread Brian G. Peterson
We've noticed over the past week that Winbuilder/R-Hub's 'experimental' Rtools4 toolchain images for Windows are approximately 4-5x slower than all other containers to build and check several packages we maintain. This affects everything, including example timings, where this architecture is the o

Re: [R-pkg-devel] Winbuilder 'experimental' toolchain 4-5x slower than all other architectures

2020-02-05 Thread Gábor Csárdi
Can you please show some numbers? Thanks, Gabor On Wed, Feb 5, 2020 at 2:40 PM Brian G. Peterson wrote: > > We've noticed over the past week that Winbuilder/R-Hub's 'experimental' > Rtools4 toolchain images for Windows are approximately 4-5x slower than > all other containers to build and check

[R-pkg-devel] Conditionally use packages from Bioconductor

2020-02-05 Thread Daniel Lüdecke
Dear all, for a package that is already published on CRAN, we plan to include a function that relies on the M3C-package, which is on Bioconductor only. Since this function in M3C is not essential for most other functions of our package, we thought about adding M3C to the "Suggests" field in the DE

Re: [R-pkg-devel] Conditionally use packages from Bioconductor

2020-02-05 Thread Uwe Ligges
On 05.02.2020 16:05, Daniel Lüdecke wrote: Dear all, for a package that is already published on CRAN, we plan to include a function that relies on the M3C-package, which is on Bioconductor only. Since this function in M3C is not essential for most other functions of our package, we thought ab

Re: [R-pkg-devel] Conditionally use packages from Bioconductor

2020-02-05 Thread Daniel Lüdecke
Thanks for the quick reply! I was a bit uncertain about this due to the CRAN check notes from this package: https://cran.r-project.org/web/checks/check_results_BiocManager.html That made me think that the reason why the packages which are not available for testing are hosted on Bioconductor. Da

Re: [R-pkg-devel] Winbuilder 'experimental' toolchain 4-5x slower than all other architectures

2020-02-05 Thread Brian G. Peterson
For every other architecture, Travis-CI and R-Hub take approximately 10-12 minutes to build and check PerformanceAnalytics. On the Windows Rtools4 experimental toolchain, the build/check on Winbuilder and R-Hub take over an hour, sometimes as much as an hour and a half. Non-trivial example timin

Re: [R-pkg-devel] Winbuilder 'experimental' toolchain 4-5x slower than all other architectures

2020-02-05 Thread Uwe Ligges
Then this is specific to your package, see the overall timings for the whole CRAN check: https://cran.r-project.org/web/checks/check_timings.html which is 2379156 sec for old and 2516120 sec for the new toolchain, i.e. roughly a 6%. Given the machines runs with very different loads it could e

Re: [R-pkg-devel] Winbuilder 'experimental' toolchain 4-5x slower than all other architectures

2020-02-05 Thread Uwe Ligges
On 05.02.2020 16:42, Uwe Ligges wrote: Then this is specific to your package, I meant the new one, not the one on CRAN which is also similarly quick (less than 10% difference). Best, Uwe Ligges see the overall timings for the whole CRAN check: https://cran.r-project.org/web/checks/check

Re: [R-pkg-devel] Winbuilder 'experimental' toolchain 4-5x slower than all other architectures

2020-02-05 Thread Dirk Eddelbuettel
On 5 February 2020 at 08:39, Brian G. Peterson wrote: | We've noticed over the past week that Winbuilder/R-Hub's 'experimental' Are you refering to winbuilder, or to rhub? | Rtools4 toolchain images for Windows are approximately 4-5x slower than | all other containers to build and check several

Re: [R-pkg-devel] function name conflict problem

2020-02-05 Thread sierrastew
Thanks to all who responded. Correct that package ‘karon’ is the problem. The current package has a more meaningful name. ‘karon’ was the earlier name; functions have been renamed. I deleted all the old function files, though they had been Committed to GitHub. A colleague working with me wro