Re: [R-pkg-devel] Issue with CPU time > 2.5 times elapsed time

2023-07-16 Thread Rodrigo Tobar Carrizo
Hi Jan, I faced a similar issue recently with the imager package, see https://stat.ethz.ch/pipermail/r-package-devel/2023q2/009042.html for the email thread on this list. In your case, it's probably data.tables creating more threads than what you think are being created, but you might want to

Re: [R-pkg-devel] OpenMP and CRAN checks

2023-04-05 Thread Rodrigo Tobar Carrizo
. The vignettes and tests were not as bad. We'll try a resubmission and see how we fare. Thanks again, Rodrigo Von: Dirk Eddelbuettel Gesendet: Dienstag, 4. April 2023 22:00 An: Rodrigo Tobar Carrizo Cc: r-package-devel@r-project.org Betreff: Re: [R-pkg-devel

[R-pkg-devel] OpenMP and CRAN checks

2023-04-04 Thread Rodrigo Tobar Carrizo
Hi list, We are having an issue with submitting a new version of the imager package to CRAN, and would like to understand how we are getting a particular NOTE. The package uses OpenMP for parallelisation of tasks. While we have a routine to set the number of threads that OpenMP should use (it

Re: [R-pkg-devel] WARNING: A complete check needs the 'checkbashisms' script.

2020-08-12 Thread Rodrigo Tobar
Hi Brian, On 12/8/20 10:21 am, brian knaus wrote: [...] It sounds like I can assume that CRAN machines will have ```checkbashisms``` installed where necessary That's my reading, yes. and handle this appropriately when not? I don't think you need to handle this at all. As you

Re: [R-pkg-devel] WARNING: A complete check needs the 'checkbashisms' script.

2020-08-10 Thread Rodrigo Tobar
Hi Brian, The checkbashisms script is invoked by the R checks automatically: https://github.com/wch/r-source/blob/trunk/src/library/tools/R/check.R#L1216-L1267 Thus there shouldn't be any need for you to invoke it manually in your configure script, even less so to worry about its presence.

Re: [R-pkg-devel] MacOS flat namespace

2020-05-06 Thread Rodrigo Tobar
Hi, On 6/5/20 6:17 pm, Fabio Corradini Santander wrote: ... Cutting the long paths of CRAN, the problem looks like (for r-oldrel-osx-x86_64): ... ** testing if installed package can be loaded from temporary location Error: package or namespace load failed for ‘uFTIR’ in dyn.load(file, DLLpath

Re: [R-pkg-devel] Calling R's tempdir() from C

2018-08-10 Thread Rodrigo Tobar
Hi, On 10.08.18 3:10 PM, Duncan Murdoch wrote: On 10/08/2018 12:01 AM, Rodrigo Tobar wrote: [...] Why not pass the result of tempdir() in your call from R to your C++ function, or in an initialization call for your package?  It won't change during a session. This is indeed a good

[R-pkg-devel] Calling R's tempdir() from C

2018-08-09 Thread Rodrigo Tobar
Dear all, I want to create a temporary directory from within my C++ R extension. On the other hand, CRAN's policy dictates that one cannot write anything outside the boundaries of the session's temporary directory, so I need to create it exactly there. The R API offers R_tmpnam and

Re: [Rd] Dialect for shell scripts

2017-12-18 Thread Rodrigo Tobar
Hi all, Thanks to all for your responses. As pointed out by a few of you, using expr is indeed safer, and is what we ended up using in our script to get it accepted in CRAN. On 19/12/17 07:26, peter dalgaard wrote: (I suspect that the text in WRE is actually older than the current POSIX

[Rd] Dialect for shell scripts

2017-12-17 Thread Rodrigo Tobar
Dear all, During a recent package submission, we were highlighted that some lines in our configure script didn't follow the correct syntax. The lines looked like this: x=$(($y/10)) We were indicated at the time that this is because the statement does not use Bourne shell syntax, which is

Re: [R-pkg-devel] Dialect for shell scripts

2017-12-15 Thread Rodrigo Tobar
Hi all, I'm just bumping this up in case somebody can shed any light on it -- otherwise I will try again to submit this question to r-devel. Regards, Rodrigo On 12/12/17 06:56, Rodrigo Tobar wrote: Dear all, During a recent package submission, we were highlighted that some lines in our

[R-pkg-devel] Dialect for shell scripts

2017-12-11 Thread Rodrigo Tobar
Dear all, During a recent package submission, we were highlighted that some lines in our configure script didn't follow the correct syntax. The lines looked like this: x=$(($y/10)) We were indicated at the time that this is because the statement does not use Bourne shell syntax, which is