[Rd] install.packages misleads about package availability?

2014-09-10 Thread Martin Morgan
In the context of installing a Bioconductor package using our biocLite() function, install.packages() warns > install.packages("RUVSeq", repos="http://bioconductor.org/packages/2.14/bioc";) Installing package into '/home/mtmorgan/R/x86_64-unknown-linux-gnu-library/3.1-2.14' (as 'lib' is unspeci

Re: [Rd] Problem with order() and I()

2014-09-10 Thread MacQueen, Don
Early on I had been wondering if deprecating I() and the AsIs class would be a way to get the problem to go away. I imagine (based on no data at all!) that they are rarely used. If I were writing the same code today, I would use options(stringsAsFactors=FALSE) instead of sprinkling I() here and the

Re: [Rd] How to test impact of candidate changes to package?

2014-09-10 Thread Paul Gilbert
On 09/10/2014 06:12 AM, Kirill Müller wrote: If you don't intend to keep the old business logic in the long run, perhaps a version control system such as Git can help you. If you use it in single-user mode, you can think of it as a backup system where you manually create each snapshot and give

[Rd] CRAN form submission confirmation link

2014-09-10 Thread Jeroen Ooms
There is a small problem in the CRAN submission form, which is not super urgent but probably good to be aware of. So I noticed that after I submitted a package, the submission was confirmed without me actually clicking the link in the confirmation email (which could be a potential security risk).

Re: [Rd] How to test impact of candidate changes to package?

2014-09-10 Thread Kirill Müller
If you don't intend to keep the old business logic in the long run, perhaps a version control system such as Git can help you. If you use it in single-user mode, you can think of it as a backup system where you manually create each snapshot and give it a name, but it actually can do much more.

Re: [Rd] How to test impact of candidate changes to package?

2014-09-10 Thread Stephanie Locke
I have unit tests using testthat but these are typically of these types: 1) Check for correct calculation for a single set of valid inputs 2) Check for correct calculation for a larger set of valid inputs 3) Check for errors when providing incorrect inputs 4) Check for known frailties / past issues

Re: [Rd] How to test impact of candidate changes to package?

2014-09-10 Thread ONKELINX, Thierry
Dear Stephanie, Have a look at the testthat package and the related article in the R Journal. Best regards, ir. Thierry Onkelinx Instituut voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team Biometrics & Quality Assurance Kliniekstraat

[Rd] How to test impact of candidate changes to package?

2014-09-10 Thread Stephanie Locke
I use a package to contain simple functions that can be handled by unit tests for correctness and more complex functions that combine the simple functions with business logic. Where there are proposals to change either the simple functions or the business logic, a sample needs to be run before