There are two relevant queries:
1) What are the methods where at least one signature component is (or
extends) this class?
2) What are the methods for this class that are defined in a specific package?
#1 is along the lines of what Vince said. I prefer that definition,
because I often want to see
This seems like a pretty simple solution, so I like that :)
On Mon, Jun 27, 2016 at 10:46 AM, Hervé Pagès wrote:
> Hi Mike,
>
> IIUC you want to do something like
>
> setdiff(methods(class="DESeqDataSet"),
> methods(class="RangedSummarizedExperiment"))
>
> Maybe this could be handled
Hi Mike,
IIUC you want to do something like
setdiff(methods(class="DESeqDataSet"),
methods(class="RangedSummarizedExperiment"))
Maybe this could be handled by methods() itself e.g. with
an extra argument that lets the user choose if s/he wants to see
all the methods (i.e. specific +
1) I guess if someone else defined methods for the FooData class then those
could be of interest, but I think nearly all of the time I want to know
just what this specific package author has defined.
2) This is getting down to my (perhaps idiosyncratic) wants, but I would
like a quick and short pr
1) is the package connection key, or is it the 'directness' of the method
in connection
with the class of interest? (sorry to be so vague, there must be a more
scientific term...)
2) it seems useful to get the signature too. this uses string operations
to get at something that
the class system
hi,
Following on a conversation from Bioc2016, I think it would be good to have
a function available to Bioconductor users that helps in the following
situation:
I'm a user, trying out a new package 'foo', which defines the FooData
class, that builds on top of SummarizedExperiment. The package au
