Hi Khoong,
About your error: I now realized that's the output at your local console.
To test your package, you should run R CMD check --as-cran bwt_1.1.0.tar.gz
from the command line. So the error has nothing to do with CRAN but with
you testing your development directory structure as opposed to t
Hi Khoong,
I'm going to address the elephant in the room: your package is not ready
for CRAN, and I'm not even sure CRAN is the right place for that code.
There's two large issues with your package, next to the license problem
Hugh pointed out already:
1. R code needs to be in subdirectory R, th
Hi,
There are a few problems with the submission. Probably more than can
be resolved by people on the mailing list. Speaking generally, a
WARNING in a CRAN check is something that *must* be fixed, rather than
something which you can just acknowledge. The two warnings that you
mentioned are that yo
Hello Dirk,
Thank you for the advice. Currently I get a bug whenever I try to use R Builder
on my computer, no matter which browser I launch it from, but I will try the
Rocker images, as I have worked with Docker before and have some familiarity.
Gratefully,
Julia
__
Hi Martin
Thank you for your reply.
> On 30 May 2018, at 12:03, Martin Maechler wrote:
>
>> Christian Sigg
>>on Wed, 30 May 2018 11:08:38 +0200 writes:
>
>> I am updating the ’nsprcomp’ package to follow the recommendations of
>> Section 1.1.3.1 of the Writing R Extensions manual
> Christian Sigg
> on Wed, 30 May 2018 11:08:38 +0200 writes:
> I am updating the ’nsprcomp’ package to follow the recommendations of
Section 1.1.3.1 of the Writing R Extensions manual.
> Before the update, the example code for the `nsprcomp` function looked
like this:
I am updating the ’nsprcomp’ package to follow the recommendations of Section
1.1.3.1 of the Writing R Extensions manual.
Before the update, the example code for the `nsprcomp` function looked like
this:
> library(MASS)
> set.seed(1)
>
> # Regular PCA, with the tolerance set to return five PCs
