Parsing a trackHub turns out to be relatively casual, at least if the hub
is well behaved. (If it isn't, must not be worthwhile... ;-))
R> dim(hubTracks)
[1] 11144 2
So that's a hub with 11144 tracks, which takes a while to parse (perhaps
2-3 minutes). There are a bunch of flat tracks right
On Sun, Dec 2, 2012 at 3:43 PM, Tim Triche, Jr. wrote:
> So, a trackHub as spec'd by UCSC ends up being a DAG. It may not be
> strictly directed, even; I'm pondering that. The file under a hub's root
> is title genomesall.txt and tells what trackDb is associated with a genome.
> Loading the cor
So, a trackHub as spec'd by UCSC ends up being a DAG. It may not be
strictly directed, even; I'm pondering that. The file under a hub's root
is title genomesall.txt and tells what trackDb is associated with a genome.
Loading the corresponding trackDb file provides a bunch of information
about th
I'm looking through the rtracklayer directory in SVN, specifically src, and
finding common files shared between bigWig and bigBed. It looks like
bigBed isn't supported yet, however, so I'm thinking of hacking up bigWig
to do something similar. How close is/was bigBed support, and if anyone
was/is
