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

Add tin.py output to MultiQC report #746

Closed
drpatelh opened this issue Dec 17, 2021 · 3 comments
Closed

Add tin.py output to MultiQC report #746

drpatelh opened this issue Dec 17, 2021 · 3 comments
Milestone

Comments

@drpatelh
Copy link
Member

When adding the rseqc/tin the TIN files are being found by MultiQC (v1.11) but I can't seem to be able to get rid of the markdup.sorted.bam extension as shown in the image below:

image (4)

This doesn't work either:
169d547

So for now I am using the wrong search path intentionally as added in dabdfee. This means the files will all be staged in the MultiQC work directory but they won't be rendered in the report.

This behaviour needs to be tested with the dev version of MultiQC and added back in properly in the next release of the pipeline.

For now, users should be able to use their own --multiqc_config to add the TIN metrics if they so wish.

@drpatelh drpatelh added this to the 3.6 milestone Dec 17, 2021
@drpatelh
Copy link
Member Author

This will be fixed in MultiQC v1.12 MultiQC/MultiQC#1484

@drpatelh
Copy link
Member Author

MultiQC v1.12 was released recently but I found an issue with the rendering of the custom content of dupRadar that needs to be addressed before we bump versions and fix this issue too MultiQC/MultiQC#1629

@drpatelh drpatelh modified the milestones: 3.6, 3.7 Feb 20, 2022
@drpatelh drpatelh modified the milestones: 3.7, 3.8 Apr 26, 2022
drpatelh added a commit to drpatelh/nf-core-rnaseq that referenced this issue Sep 27, 2022
@drpatelh
Copy link
Member Author

Fixed in 77d49dd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant