On Tue, Nov 23, 2021 at 12:06 PM Gábor Csárdi wrote:
>
> On Tue, Nov 23, 2021 at 8:49 PM Henrik Bengtsson
> wrote:
> >
> > > Is there any reliable way to let packages to know if they are on CRAN, so
> > > they can set omp cores to 2 by default?
> >
> > Instead of testing for "on CRAN" or not,
On 23 November 2021 at 12:19, Hervé Pagès wrote:
| But why would you need to check for anything in the first place?
|
| If you only use 2 cores in your examples, vignettes, and unit tests, 'R
| CMD check' will run fine everywhere and not eat all the CPU power of the
| machine where it's
But why would you need to check for anything in the first place?
If you only use 2 cores in your examples, vignettes, and unit tests, 'R
CMD check' will run fine everywhere and not eat all the CPU power of the
machine where it's running.
H.
On 23/11/2021 12:05, Gábor Csárdi wrote:
On Tue,
On Tue, Nov 23, 2021 at 8:49 PM Henrik Bengtsson
wrote:
>
> > Is there any reliable way to let packages to know if they are on CRAN, so
> > they can set omp cores to 2 by default?
>
> Instead of testing for "on CRAN" or not, you can test for 'R CMD
> check' running or not. 'R CMD check' sets
> Is there any reliable way to let packages to know if they are on CRAN, so
> they can set omp cores to 2 by default?
Instead of testing for "on CRAN" or not, you can test for 'R CMD
check' running or not. 'R CMD check' sets environment variable
_R_CHECK_LIMIT_CORES_=TRUE. You can use that to
This may be more of a question for r-package-devel than for r-devel.
On 23 November 2021 at 14:11, Dipterix Wang wrote:
| I recently received an email from Prof. Ripley. He pointed out that my
package seriously violates the CRAN policy: "using 8 threads is a serious
violation of the CRAN
Dear R wizards,
I recently received an email from Prof. Ripley. He pointed out that my package
seriously violates the CRAN policy: "using 8 threads is a serious violation of
the CRAN policy”. By default the number of cores my package uses is determined
from system CPU cores. After carefully
