Unlike exptData(), metadata() returns an ordinary list. These methods
also need to be exported and have aliases in the man page for
RangedSummarizedExperiment. I'll add something like that to the
SummarizedExperiment package. Thanks Tim!
H.
On 05/12/2015 11:27 AM, Tim Triche, Jr. wrote:
one set
It's more general than SummarizedExperiment. I think people would
appreciate a simple way to load the core, without having to remember, for
example, that VCF reading is in VariantAnnotation.
On Mon, May 11, 2015 at 9:51 PM, Hervé Pagès wrote:
> Hi Michael,
>
> On 05/11/2015 05:35 PM, Michael Law
SummarizedExperiment was just an example. I agree it can be a
little challenging for end users to know where to find a particular
functionality but I'm not sure about using "meta" packages to address
that. At least I feel we should probably avoid creating new "meta"
packages out of the blue, with
I like the idea of having multiple, domain-specific cores. Those could also
serve as a vehicle for high-level documentation, including the workflows
but also more "cheat-sheet" and/or cookbook-style documentation. Rafa has
brought this up on the phone calls.
On Tue, May 12, 2015 at 4:10 PM, Hervé
Agreed that the workflow vehicle should get more attention. Do all
workflows correspond to packages?
On Tue, May 12, 2015 at 7:31 PM, Michael Lawrence wrote:
> I like the idea of having multiple, domain-specific cores. Those could also
> serve as a vehicle for high-level documentation, includin
