Although, since you (Philipp) are the maintainer of the nbconvertR package, you
may want to create an INSTALL file in that package. It's up to you.
Dan
Haha, yeah. Thanks, Dan!
I’m already in the process of submitting nbconvertR 1.1, which only uses
jupyter (Using ipython nbconvert is
Hi Steffen,
I also develop on Linux, so I'm at a loss with compiling Bioconductor libs on
Windows.
As a guess, if there are no compiler errors but 'mzR.dll' cannot be found, I
suppose the final linking of the compiled objects failed?
I did a quick search and there seems to be a precedence for
Hi,
On Mi, 2016-10-05 at 12:08 +, jason.r...@csiro.au wrote:
>
> ...
> As a guess, if there are no compiler errors but 'mzR.dll' cannot be
> found, I suppose the final linking of the compiled objects failed?
I now have a working version here locally, and several minutes ago
Laurent Gatto me
hi,
there's a warning issued by GenomeInfoDb::keepStandardChromosomes()
because of multiple compatible sequence styles, that i guess it should
be corrected. this warning can be reproduced minimally as follows;
library(GenomicRanges)
library(GenomeInfoDb)
gr <- GRanges(seqnames="1", IRanges(1
Hi Steffen,
Any reason you're linking mzR.dll against your own precompiled
libnetcdf.a? (located in mzR/src/win/). This masks the libnetcdf.a
that I installed on tokay1 per your request a couple of weeks ago
(by just extracting Ripley's spatial324.zip inside C:\local323).
Why not remove these pre
On 10/04/2016 05:09 PM, Martin Morgan wrote:
On 10/04/2016 05:07 PM, McDavid, Andrew wrote:
BiocCheck throws a warning when a package is listed as Imports: in
DESCRIPTION but not used in the NAMESPACE. This may happen when a
developer uses the fully qualified names of objects within a package.
Hi Jason,
On 10/05/2016 05:08 AM, jason.r...@csiro.au wrote:
Hi Steffen,
I also develop on Linux, so I'm at a loss with compiling Bioconductor libs on
Windows.
As a guess, if there are no compiler errors but 'mzR.dll' cannot be found, I
suppose the final linking of the compiled objects faile
Will we be using R-3.3.2 or 3.3.1?
Best,
Kasper
On Tue, Sep 13, 2016 at 3:11 PM, Hervé Pagès wrote:
> Dear all,
>
> The tentative release date for Bioconductor 3.4 is Tuesday October 18.
> Please read full schedule here:
>
> http://bioconductor.org/developers/release-schedule/
>
> One importa
I just uploaded a fix. This should be corrected in version 1.9.14
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-devel on behalf of Ro
Hi Kasper,
IIUC R-3.3.2 will be released at the end of the month, so after
our release (scheduled for Oct 18). We'll update R on the build
machines as soon as R-3.3.2 becomes available.
Cheers,
H.
On 10/05/2016 11:40 AM, Kasper Daniel Hansen wrote:
Will we be using R-3.3.2 or 3.3.1?
Best,
Kas
Hello,
I submitted a new package after the deadline, so I understand it won't
be available to users until the next release in 6 months (assuming it's
acceptable).
I'm not clear on what happens once a package is accepted into
Bioconductor. At that point, if I make changes, are they visible to
user
On 10/05/2016 05:33 PM, Tyler Smith wrote:
Hello,
I submitted a new package after the deadline, so I understand it won't
be available to users until the next release in 6 months (assuming it's
acceptable).
I'm not clear on what happens once a package is accepted into
Bioconductor. At that point
12 matches
Mail list logo
