CanvasFeatures do not use the pre-generated histograms #475

Closed
cmdcolin opened this Issue May 9, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@cmdcolin
Contributor

cmdcolin commented May 9, 2014

This was originally posted on the mailing list by Danial Troesser

[Gmod-ajax] Histograms with CanvasFeatures in JBrowse

"Does anyone know how to get pre-generated histogram data to work with CanvasFeatures? We're using LazyNCList files. It's generating histograms, but it's generating it from the feature data (lf-{Chunk}.json) rather than hist-xxxxxx-{Chunk}.json.

Thanks,"

I was sort of naive in my replies to this thread but I think that CanvasFeatures tracks have some real problems with the histograms. I haven't dug into the code yet but it needs fixing since generating histograms on the fly takes huge RAM
See #474 for details about my test setup.

@cmdcolin

This comment has been minimized.

Show comment
Hide comment
@cmdcolin

cmdcolin May 9, 2014

Contributor

It seems like the default number of bins for CanvasFeatures is very high (200) compared with the HTMLFeatures (25) and there are generally no pre-generated histograms with that resolution. For the canvas based "Alignments", which have ‘Bigwig’ style histograms, this is ok, but the regular feature tracks have problems with it.

Contributor

cmdcolin commented May 9, 2014

It seems like the default number of bins for CanvasFeatures is very high (200) compared with the HTMLFeatures (25) and there are generally no pre-generated histograms with that resolution. For the canvas based "Alignments", which have ‘Bigwig’ style histograms, this is ok, but the regular feature tracks have problems with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment