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

Heatmaps break with report "Show only matching samples" #1172

Closed
ewels opened this issue Apr 29, 2020 · 1 comment
Closed

Heatmaps break with report "Show only matching samples" #1172

ewels opened this issue Apr 29, 2020 · 1 comment
Labels
bug: core Bug in the main MultiQC code
Milestone

Comments

@ewels
Copy link
Member

ewels commented Apr 29, 2020

Reported by @sergpolly in #1137 (comment)

working on this I realized another potential issue with applying toolbox to the heatmaps ...
screaming, when one chooses to hide in Show only matching sa mples-regime - see another demo:
hide_show_matching
SRR106 matches a bunch of samples but none of the xcats - column labels - which makes heatmap yield "blank" - should I open another issue to keep this in the record ?

So this specifically is a problem when using Show only matching samples in the report "Show / Hide" panel in combination with heatmaps that do not have sample names on both axes.

This is tricky to fix as we don't currently know which things in heatmaps are categories and which are sample names. I think that we might need to have a new plot config option to handle this (and a new lint test for it so that we can go through and implement this in all existing heatmaps).

@ewels ewels added the bug: core Bug in the main MultiQC code label Apr 29, 2020
@ewels ewels added this to the MultiQC v1.9 milestone May 23, 2020
@ewels ewels closed this as completed in c2abbd9 May 26, 2020
@ewels
Copy link
Member Author

ewels commented May 26, 2020

Hi @sergpolly,

Thanks again for reporting this, good spot! I have now implemented a fix by adding two new config options that allow you to specify that a heatmap axis does not contain sample names (see c2abbd9).

I went through all of the heatmaps in core MultiQC modules and I think this issue only affected FastQC status and the new iVar module. I've added the options there and it seems to work well.

Let me know if you spot any others!

Phil

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

1 participant