Dear Bioconductor Developers,
Big news! We are planning to migrate from SVN to git. This is a major change in
our version control model. We understand this may be disruptive to some
developers and are working to make the transition as smooth as possible. The
end goal is to provide a
On Fri, Mar 3, 2017 at 9:55 AM, Hadley Wickham wrote:
>> But, how you propose a warning-to-error transition should be made
>> without wreaking havoc? Just flip the switch in R-devel and see CRAN
>> and Bioconductor packages break overnight? Particularly Bioconductor
>>
On Fri, Mar 3, 2017 at 9:22 AM, Martin Maechler
wrote:
>> Henrik Bengtsson
>> on Fri, 3 Mar 2017 00:52:16 -0800 writes:
>
> > I'd like to propose that the whenever the length of condition passed
> > to an if or a while
I tried installing the 'ks' package from my interactive R session, it
failed with the following
Erreur dans .External2(C_loadhistory, file) :
aucun mécanisme d'historique des commandes disponible
Calls:
Exécution arrêtée
second line is french for "no command history mechanism available",
> Henrik Bengtsson
> on Fri, 3 Mar 2017 00:52:16 -0800 writes:
> I'd like to propose that the whenever the length of condition passed
> to an if or a while statement differs from one, an error is produced
> rather than just a warning as today:
> Boehnstedt, Marie
> on Fri, 3 Mar 2017 10:23:12 + writes:
> Dear all,
> I have found a bug in nlm() and would like to submit a report on this.
> Since nlm() is in the stats-package, which is maintained by the R Core
team, bug reports
On Fri, Mar 3, 2017 at 10:22 AM, Vincent Carey
wrote:
>
>
> On Fri, Mar 3, 2017 at 10:07 AM, Kasper Daniel Hansen <
> kasperdanielhan...@gmail.com> wrote:
>
>> Some comment on Aaron's stuff
>>
>> One possibility for doing things like this is if your code can be done
On Fri, Mar 3, 2017 at 10:07 AM, Kasper Daniel Hansen <
kasperdanielhan...@gmail.com> wrote:
> Some comment on Aaron's stuff
>
> One possibility for doing things like this is if your code can be done in
> C++ using a subset of rows or columns. That can sometimes give the
> necessary speed up.
Some comment on Aaron's stuff
One possibility for doing things like this is if your code can be done in
C++ using a subset of rows or columns. That can sometimes give the
necessary speed up. What I mean is this
Say you can safely process 1000 cells (not matrix cells, but biological
cells, aka
Dear all,
I have found a bug in nlm() and would like to submit a report on this.
Since nlm() is in the stats-package, which is maintained by the R Core team,
bug reports should be submitted to R's Bugzilla. However, I'm not a member of
Bugzilla. Could anyone be so kind to add me to R's Bugzilla
Kylie, thanks for reminding us of matter -- I saw you speak about this at
the first Bioconductor Boston Meetup, but it
went like lightning. For developers contemplating an approach to
representing high-volume rectangular data,
where there is no dominant legacy format, it is natural to wonder
I'd like to propose that the whenever the length of condition passed
to an if or a while statement differs from one, an error is produced
rather than just a warning as today:
> x <- 1:2
> if (x == 1) message("x == 1")
x == 1
Warning message:
In if (x == 1) message("x == 1") :
the condition has
Dear Aaron
Thank you. I think it's an important simplification of a potential API
when you are saying that what you mostly need are accessors
m[i, ] and m[, i]
with i scalar or a short contiguous range, such that the value of that
could be a relatively small ordinary matrix. (Compared to
13 matches
Mail list logo