I think the more clean solution for Davide (if he inists on having separate
objects; I decided against it in minfi) is to extend the class to allow
this.
Kasper
On Thu, Jun 18, 2015 at 12:25 AM, Ryan r...@thompsonclan.org wrote:
Oh wow, I didn't know you could put a DataFrame into a single
yes, if a formal extension is warranted. the metadata slot could also be
used.
On Thu, Jun 18, 2015 at 2:59 PM, Kasper Daniel Hansen
kasperdanielhan...@gmail.com wrote:
I think the more clean solution for Davide (if he inists on having separate
objects; I decided against it in minfi) is to
you can just implement this by having reserved column names in the colData
slot; that will work and will take appr. 23 seconds to implement. I agree
it is not as clean from a design perspective, but you get 100% of the
functionality and you can write a separate checker for the colData argument.
Thanks Kasper,
I think that's a good solution.
Best,
Davide
On Thu, Jun 18, 2015 at 11:51 AM Kasper Daniel Hansen
kasperdanielhan...@gmail.com wrote:
you can just implement this by having reserved column names in the colData
slot; that will work and will take appr. 23 seconds to implement.
Thank you all for the responses.
I didn't think about the nested DataFrame solution. It should work.
I agree that an extension might be cleaner, but I clearly need to give it
more thought.
One of the reasons I wanted to have quality and metadata as separate slots
is that one could enforce that
On 06/17/2015 11:41 AM, davide risso wrote:
Dear list,
I'm creating an R package to store RNA-seq data of a somewhat large project
in which I'm involved.
One of the initial goals is to compare different pre-processing pipelines,
hence I have multiple expression matrices corresponding to the
Oh wow, I didn't know you could put a DataFrame into a single column of
another DataFrame. That actually solves a problem for me too (I don't
intend to expose nested DataFrames to the users though).
On 6/17/15 7:23 PM, Martin Morgan wrote:
On 06/17/2015 11:41 AM, davide risso wrote:
Dear
