-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default to 3 standard deviations #87
Comments
@AlistairNWard, the vue branch is currently defaulting to 4 standard deviations. Do we want to change it to 3? |
Ok now I'm confused. I tried it with a different data set and now it says "multiples of median" instead of standard deviations. Which part of the UI are we talking about, the "Zoom y axis" widget? |
Yes, we're talking about the "Zoom y axis" widget. Should have been clearer. I also wonder if the slider is the best element to control this as it is very laggy. This might do better as just having the number of standard deviations listed and the user can just change the value? This isn't responsive enough to move the slider and watch its effect. And yes, this was actually implemented as multiples of the median coverage. The purpose of this is to try to find the median coverage and assume that this represents the coverage of standard diploid genome. A heterozygous deletion would then appear at half the median coverage and duplications/CNVs would have coverage increases in multiples of half of the median, if this makes sense. There are lots of big coverage spikes, and this chart was automatically scaling to accommodate all data, which meant you couldn't really pick out what was happening around the median coverage. So if we set the max on the y axis to a few multiples of the median coverage, we should be able to pick out large CNVs. I would really like to see a way of smoothing this data to make it more legible, but that is another issue (#84)! |
When bam.iobio is opened, set the default in the read coverage chart to less standard deviations (maybe 3 or 4)
The text was updated successfully, but these errors were encountered: