-
Notifications
You must be signed in to change notification settings - Fork 5
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
Normalize results by fraction of reads in some MultiQC plots #36
Comments
I am realizing that some of these are already available (for STAR, FastQC). For Cutadapt it may be too much of a hassle to change the existing MultiQC plugin. However, for the tin-score-calculation plugin, this may still be a reasonable feature. |
I would advise against adjusting official plugins. |
My understanding of TIN scores is that it measures for each transcript its integrity. |
This is the repo with the plugins: In order to adjust which TIN scores are plotted one needs to modify this script: It would be nice to get a decision here - do we just remove |
Have TIN score as |
Is your feature request related to a problem? Please describe.
Some MultiQC plots (e.g., from FastQC, tin-score-calculation, STAR), report absolute numbers of reads rather than fractions of reads. While it is useful to know the sequencing depths of the different samples/libraries, it is perhaps not very informative/helpful to represent these differences in multiple plots, as this makes it hard to compare key metrics across samples, e.g., the fraction of (uniquely) mapped reads across samples. This is especially problematic when these plots are exported and put in publications as static images.
Describe the solution you'd like
Have one plot that reports sequencing depths/library sizes for each sample as bar plots. Have all other plots report fractions of reads instead.
Additional context
It may not be possible to configure MultiQC in a way that read fractions are visualized instead of read numbers. In that case, it is probably too much of a hassle to implement the desired solution.
The text was updated successfully, but these errors were encountered: