Thank you very much Peter. Your advice helped me find the error. I had not
previously known where to find the package's -Ex.R file, and I didn't even
realize that this was a timeout error. (The -Ex.R file was in my working
directory, not the package directory.) One function did have some long
examp
On Tue, 30 Apr 2019 19:53:49 +
"Zhang, Lixiang" wrote:
> I don't know why is that happening and how should I fix it. Thanks a
> lot for your help.
The e-mail from CRAN also said,
>> More details are given in the directory:
followed by a link scrambled by your e-mail software. When you foll
On 30/04/2019 3:53 p.m., Zhang, Lixiang wrote:
Sorry to interrupt, but I have some problems that I don't understand about the
check result. It shows that it passes the check using R CMD check --as-cran.
But when I submit to cran, it shows me an error on Debian:
* checking whether package ‘cps’
On Tue, 30 Apr 2019 at 22:06, Zhang, Lixiang wrote:
>
> Sorry to interrupt, but I have some problems that I don't understand about
> the check result. It shows that it passes the check using R CMD check
> --as-cran. But when I submit to cran, it shows me an error on Debian:
>
> * checking whethe
Sorry to interrupt, but I have some problems that I don't understand about the
check result. It shows that it passes the check using R CMD check --as-cran.
But when I submit to cran, it shows me an error on Debian:
* checking whether package ‘cps’ can be installed ... [8s/8s] ERROR
Installation
-Original Message-
From: Ivan Krylov
Sent: Tuesday, April 30, 2019 10:17 AM
To: Wang, Zhu
Cc: R-package-devel@r-project.org
Subject: Re: [R-pkg-devel] parallel computing slower than sequential computing
On Mon, 29 Apr 2019 23:44:42 +
"Wang, Zhu" wrote:
> sessionInfo()
> R version
On Mon, 29 Apr 2019 23:44:42 +
"Wang, Zhu" wrote:
> sessionInfo()
> R version 3.5.2 (2018-12-20)
> Platform: x86_64-pc-linux-gnu (64-bit)
> Running under: Ubuntu 18.04.2 LTS
Which BLAS implementation do you use? One popular implementation,
OpenBLAS, spawns multiple threads to do some opera
That line is a generic part of the timing (it records current time so that at
the end you can do what amounts to "Time used:" proc.time() - .ptime).
It is not likely to contain the actual error -- notice that the message just
gives you a best guess of the error location and that may fail. You p
