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-de
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-de
Hi Thomas,
- Original Message -
> From: "Thomas J Hardcastle"
> 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
> collaborators h
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 wa
On 09/10/2014 10:39 AM, davide risso wrote:
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 dir
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
O
On 09/10/2014 11:37 AM, davide risso wrote:
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 availa
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 hi
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 'dev
