Developers,
On 11/16/2015 11:39 PM, Hervé Pagès wrote:
Hi Aaron,
On 11/16/2015 09:39 AM, Hervé Pagès wrote:
[...]
Anyway, you convinced me that we should not try to follow too closely
the names model for how we treat metadata columns. If nobody objects,
I'll change the behavior of the
Hi Aaron,
On 11/15/2015 12:37 PM, Aaron Lun wrote:
Hi Herve,
I would have expected GRanges behaviour, where the metadata is affected
by the replacement. For example, with GRanges objects, I often use the
metadata to store statistics or descriptors relevant to each genomic
interval, e.g., peak
Hi Aaron,
On 11/16/2015 09:39 AM, Hervé Pagès wrote:
Hi Aaron,
On 11/15/2015 12:37 PM, Aaron Lun wrote:
Hi Herve,
I would have expected GRanges behaviour, where the metadata is affected
by the replacement. For example, with GRanges objects, I often use the
metadata to store statistics or
Hi Herve,
I would have expected GRanges behaviour, where the metadata is affected
by the replacement. For example, with GRanges objects, I often use the
metadata to store statistics or descriptors relevant to each genomic
interval, e.g., peak scores, log-fold changes and so on. If I did a
Hello all,
I've encountered some unexpected behaviour with some of the base classes
while developing stuff for genomic interactions. The first issue lies
with the subset replacement in the Vector class. Let's say I make a
derived class "foo" inheriting from Vector, as below:
>
