You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some studies may consist of multiple sets of gene expression datasets (RNA-Seq, RT-PCR) or splicing datasets (Percent spliced-in on the 5' side and the 3' side of the intron, separately). The idea is that the expression datasets can be treated similarly, i.e. have similar assumptions about the data type (log-normal ish distribution for expression, between 0 and 1 for splicing), and can use the same underlying ExpressionData or SplicingData methods, but will act on separate underlying datasets. This can similarly be extended for location-style data types like ChIP-Seq, CLIP-Seq, Methyl-seq, RNA editing, etc.
I envision implementing this in the datapackage as:
Notice {rnaseq,rtpcr,psi3,psi5}_feature are the feature metadata objects for the datasets. They may change to be stored within the {rnaseq,rtpcr,psi3,psi5} entries.
This datapackage would then produce a Study object where you can do:
It's going to be hard to implement this such that initializing from Study isn't too complicated, because even the current implementation is really all over the place.
This feature will really change the game because it will make flotilla a true one-stop-shop for all your needs with a particular dataset.
The text was updated successfully, but these errors were encountered:
Some studies may consist of multiple sets of gene expression datasets (RNA-Seq, RT-PCR) or splicing datasets (Percent spliced-in on the 5' side and the 3' side of the intron, separately). The idea is that the expression datasets can be treated similarly, i.e. have similar assumptions about the data type (log-normal ish distribution for expression, between 0 and 1 for splicing), and can use the same underlying
ExpressionData
orSplicingData
methods, but will act on separate underlying datasets. This can similarly be extended for location-style data types like ChIP-Seq, CLIP-Seq, Methyl-seq, RNA editing, etc.I envision implementing this in the
datapackage
as:Notice
{rnaseq,rtpcr,psi3,psi5}_feature
are the feature metadata objects for the datasets. They may change to be stored within the{rnaseq,rtpcr,psi3,psi5}
entries.This datapackage would then produce a
Study
object where you can do:It's going to be hard to implement this such that initializing from
Study
isn't too complicated, because even the current implementation is really all over the place.This feature will really change the game because it will make flotilla a true one-stop-shop for all your needs with a particular dataset.
The text was updated successfully, but these errors were encountered: