- Original Message -
> From: "Stephanie M. Gogarten"
> To: bioc-devel@r-project.org
> Sent: Thursday, December 4, 2014 1:46:56 PM
> Subject: [Bioc-devel] bug in source control HOWTO
>
> Using the URLs exactly as given on the "Source Control" HOWTO results
> in
> the following error:
>
Using the URLs exactly as given on the "Source Control" HOWTO results in
the following error:
svn co
https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_3_0/madman/Rpacks/MYPACKAGENAME
svn merge -c140
https://hedgehog.fhcrc.org/gentleman/bioconductor/trunk/madman/Rpacks/MYPACKAGENAME
sv
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-
Hello,
I’m working with cummeRbund in R 3.1.1 and I’m trying to get a different point
size for my csVolcano plot. I’ve tried two approaches an neither see to work.
after loading library and the data as
library(cummeRbund)
cuff <- readCufflinks(“diff_out”)
1)use the mapping setting for the csV
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
Hi,
Can we harmonize the default parameters for =ScanVcfParam= and
=VRangesScanVcfParam=? It even seems that we could drop
=VRangesScanVcfParam= since it is mainly a wrapper for =ScanVcfParam=.
Currently, the defaults for importing fields from a VCF are:
ScanVcfParam: fixed = character(), inf
