Skip to content
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

Samtools stats: samples are mixed up in 'Stats' section #278

Closed
cjfields opened this issue Aug 5, 2016 · 5 comments
Closed

Samtools stats: samples are mixed up in 'Stats' section #278

cjfields opened this issue Aug 5, 2016 · 5 comments
Labels
bug: core Bug in the main MultiQC code
Milestone

Comments

@cjfields
Copy link

cjfields commented Aug 5, 2016

I'm seeing an worrisome odd bug for samtools stats output in the Stats section with the popup IDs (doesn't seem to be a problem in other sections).

The following two snapshots show the sample name for the highlighted spot as C12, but this is incorrect. For instance, in the Total Sequences pic the highlighed number appears to correspond to sample C4. In the 'Mapped & Paired' row the C12 sample is again incorrect and appears to correspond with N9. Both can be seen in the attached multiqc_samtools_stats.txt file, which seems to have the correct data based on a cursory look.

bad-stats
bad-stats2

I have also attached the MultiQC log and other output files. The stats within appear to be parsed correctly from the reports.

multiqc.log.txt
multiqc_general_stats.txt
multiqc_samtools_stats.txt
multiqc_sources.txt

@ewels
Copy link
Member

ewels commented Aug 5, 2016

Thanks for the detailed report! I'm on holiday at the moment but will look into this when I get back..

@cjfields
Copy link
Author

cjfields commented Aug 5, 2016

@ewels not a problem, about to go on a short trip myself. I may check into it when I get back, if I can work out the issue I may set up a pull request.

@ewels ewels added the bug: core Bug in the main MultiQC code label Aug 13, 2016
@ewels
Copy link
Member

ewels commented Aug 18, 2016

Hi @cjfields,

I've just spotted the same error in a different beeswarm / dot plot (this one for Bismark). So I think that this is a bug somewhere in the plotting code. Looking into it now.

Phil

@ewels ewels closed this as completed in f9ffac4 Aug 18, 2016
@ewels ewels added this to the v0.8 milestone Aug 18, 2016
@ewels
Copy link
Member

ewels commented Aug 18, 2016

Hi @cjfields,

I think I tracked it down - there was a sort statement in the Javascript that I'd added at some point to improve the stacking of the dots. However, this broke the association with the sample names. Nasty bug sorry, and I hadn't noticed it as the overall shape of the plot remained the same.

I just pushed a fix, it's now working as expected for me so I've closed this issue. If you could try your samples above again and confirm that it's working for you too then that would be brilliant.

Thanks again for reporting this.

Phil

@cjfields
Copy link
Author

Not a problem, thanks for the fix @ewels !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: core Bug in the main MultiQC code
Projects
None yet
Development

No branches or pull requests

2 participants