Somewhat related to this topic, some folks made this package:
https://github.com/hilaryparker/explainr It could be related to
Wolfgang's idea of "learning" which methods are more important, its
just that people would have to write the explanation. Then a new user
can "learn" about it.
On Mon, Apr
I just noticed in the newsletter [1] that Martin fixed this in R-devel / R
3.2
> methods(class="GenomicRanges")
[1] !=[ [<- %in%
<
...
thanks Martin!
[1]
http://www.bioconductor.org/help/newsletters/2015_April/#new-and-noteworthy
On Sat, Dec 6,
On Sat, Dec 6, 2014 at 9:23 AM, Wolfgang Huber wrote:
>
> Also some interest on our side to contribute.
> Perhaps in particular the rendering a useful index (or graph) of man pages
> on the fly in HTML / graphically.
>
>
Great, that's the sort of thing I had in mind.
> Is it too ambitious to “l
Also some interest on our side to contribute.
Perhaps in particular the rendering a useful index (or graph) of man pages on
the fly in HTML / graphically.
Is it too ambitious to “learn” which methods are most important for objects of
a particular class from analysing (running) a large code base
nice. I will play around with this. thanks Gabe!
On Fri, Dec 5, 2014 at 6:37 PM, Gabe Becker wrote:
> Hey guys,
>
> Surgically removed from promptClass:
>
> classInSig <- function(g, where, cl) {
> cl %in% unique(unlist(findMethods(g, where)@signatures))
> }
> genWithClass <- fu
Hey guys,
Surgically removed from promptClass:
classInSig <- function(g, where, cl) {
cl %in% unique(unlist(findMethods(g, where)@signatures))
}
genWithClass <- function(cl, where) {
allgen <- getGenerics(where = where)
ok <- as.logical(unlist(lapply(allgen, clas
Cool. I see hypertext as being useful here, because the generics and
classes form an intricate and sometimes ambiguous web, especially when
multiple inheritance and dispatch are involved. I think we should first
build better tooling for introspecting S4 and for graph-based modeling and
analysis of
On Thu, Dec 4, 2014 at 4:01 PM, Michael Lawrence
wrote:
>
> I think this gets at the heart of at least one of the usability issues in
> Bioconductor: interface discoverability. Many simpler command line tools have
> a single-faceted interface for which it is easy to enumerate a list of
> featur
I think this gets at the heart of at least one of the usability issues in
Bioconductor: interface discoverability. Many simpler command line tools
have a single-faceted interface for which it is easy to enumerate a list of
features. There's definitely room for better ways to interrogate our
object-
fwiw sos::findFn("narrow") produces quite a few hits, including
http://finzi.psych.upenn.edu/R/library/GenomicRanges/html/intra-range-methods.html
it may be more effective to parse doc than to hope that the formal metadata
will yield the desired fruit?
On Thu, Dec 4, 2014 at 1:26 PM, Martin Morg
On 12/04/2014 09:56 AM, Michael Love wrote:
I was thinking about a request from someone at Bioc2014 (I can't
remember at the moment)
As an end-user, if I have an object x, how can I *quickly* recall the
main methods for that? As in, without breaking my flow and going to
?myClass or help("myClass
I was thinking about a request from someone at Bioc2014 (I can't
remember at the moment)
As an end-user, if I have an object x, how can I *quickly* recall the
main methods for that? As in, without breaking my flow and going to
?myClass or help("myClass-class"). Suppose x is a GRanges, how can I
re
12 matches
Mail list logo
