[Bioc-devel] [JOB] NIH-Wide Stadtman Tenure-Track Recruitment

2014-09-10 Thread Sean Davis
The National Institutes of Health is now accepting applications for tenure-track positions through the Earl Stadtman recruitment mechanism. Details are available here: http://goo.gl/vF95Pi Sean [[alternative HTML version deleted]] ___

[Bioc-devel] Fwd: [JOB] NIH-Wide Stadtman Tenure-Track Recruitment

2014-09-10 Thread Sean Davis
The National Institutes of Health is now accepting applications for tenure-track positions through the Earl Stadtman recruitment mechanism. Details are available here: http://goo.gl/vF95Pi Sean [[alternative HTML version deleted]] ___

Re: [Bioc-devel] Changing the name of a package

2014-09-10 Thread Dan Tenenbaum
Hi Thomas, - Original Message - From: Thomas J Hardcastle tj...@cam.ac.uk To: bioc-devel@r-project.org Sent: Monday, September 8, 2014 5:19:09 PM Subject: [Bioc-devel] Changing the name of a package I have a package on the development build called riboSeq; my biological

Re: [Bioc-devel] biocLite message R package not available is confusing

2014-09-10 Thread davide risso
I just wanted to add my support to Josef request. During the last few weeks I received several emails from users asking me if I plan to make a version of RUVSeq compatible with R 3.1. (My RUVSeq package is in devel). I understand the error comes directly from install.packages, but is there a way

Re: [Bioc-devel] biocLite message R package not available is confusing

2014-09-10 Thread davide risso
Thanks Martin, yes, you're right about the use the devel version, but perhaps biocLite could check if the package is available in the devel, just to distinguish between a package that is not in Bioconductor (mistyping?) and one that is not yet available in release. Just my two cents. Davide On

Re: [Bioc-devel] Please bump version number when committing changes

2014-09-10 Thread Martin Morgan
On 09/08/2014 06:15 AM, Gabe Becker wrote: Michael, Tags could work. Another approach would be to update the repository and then look in the log to see if the version number was changed in the most recent commit. In a sense this is the converse of what our GRANBase package does when locating

Re: [Bioc-devel] biocLite message R package not available is confusing

2014-09-10 Thread davide risso
Hi Martin, I wonder where the users are getting the notion that they _should_ be able to install RUVSeq in Bioc 2.14? I guess they follow the link in the Nature Methods paper to the devel landing page, then follow the 'Installation' instructions without paying attention to the various

[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

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

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

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.

[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 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

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

[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