Fixes to quality plots with fwd & rev reads#2116
Conversation
|
Should add this commit too: |
|
Big improvement on layout obviously. Overall I like the colours, but there's one slight issue that going through very light colours in two places (the very top and around aqua) can lead to confusion when you have a very dotty image instead of the more continuous gradations we see on NovaSeqs. See these examples. The second picture, to my red/green colourblind eyes, I don't easily distinguish the two light shades. The blue colours are Q10 are easier to see though. I wonder if we just need a slightly truncated colour-wheel? |
|
Yes, the rainbow heatmap is not ideal for this. This one was based on a MatLab heatmap in the gnuplot documentation. It's OK for smooth contours, like plotting mathematical functions, but where there are adjacent areas from different parts of the heatmap we need one where it's obvious which is larger. I'll have to a go at choosing one which is consistently dark > light alongside any colour change. |
|
Thanks James |
|
I think we want one of the perceptually uniform matplotlib colourmaps. |
|
It's a better gradation, but personally I think it's a bit too washed out at low frequencies. With I agree with what you were attempting to do by moving away from a black background, but this feels too light to me. Thoughts on this change? (Just a quick hacked up tweak of the lowest two thresholds) |
|
Or alternatively moving the 0 entry to 1 and making a new 0 (even black) really highlights the difference going from zero or negligble amounts to significant. Have a play with a few data sets I think |
Yes, that sounds like a good idea. |
|
I suggest you play with some single ended runs too. I see this change also broke things there, removing the xtics and colourwheel. A stab at fixing it is below (with other colour hacks as I was just experimenting): |
|
The yticks could be improved when we start looking at longer reads too. Eg: Although frankly A Revio example though: |
|
Any update on this James? |
|
Sorry, I haven't had time to look at this. I was hoping to submit a quick fix and move on, and not end up rewriting it, in which case I'd probably choose a plotting library other than gnuplot! I'd also want to add a diverse set of example input, but I only have examples of NovaSeqX stats. We don't use bamstats for PacBio data. |
|
Your improvements are clearly significantly improving things, so thanks. If it helps I'm happy to pick up from where you got to and add my changes above too in a second commit. It's obviously better than it languishing due to insufficient data or time for you to progress on it. |
Fix single-ended run plots. Reduce rate of tick labels for long-reads. Adjust colour wheel to bring out more fidelity with very low qualities so we have better distinction between all zero and some low qual. Replaces / fixes samtools#2116
Fix single-ended run plots. Reduce rate of tick labels for long-reads. Adjust colour wheel to bring out more fidelity with very low qualities so we have better distinction between all zero and some low qual. Replaces / fixes samtools#2116
Fix single-ended run plots. Reduce rate of tick labels for long-reads. Adjust colour wheel to bring out more fidelity with very low qualities so we have better distinction between all zero and some low qual. Replaces / fixes samtools#2116 (cherry picked from commit aa8cb59)











Fixes warning:
which resulted in missing ticks on
quals2plot.Fixes
quals-hmbroken plot layout:to:
and changes heatmap to a (hopefully) more interpretable one which avoids dark zones between blue and green and between green and red.
Fixes broken table HTML in gallery file and broken links when file names contain characters which need to be URI escaped.