# Adding custom data to multiqc

**URL:** <https://community.seqera.io/t/adding-custom-data-to-multiqc/1482>\
**Category:** Ask for help\
**Tags:** multiqc\
**Created:** [November 22, 2024, 2:04pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482 "2024-11-22T14:04:50Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kubranarci](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/kubranarci/32/264_2.png) [@kubranarci](https://community.seqera.io/u/kubranarci)\
**Post date:** [November 22, 2024, 2:04pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/1 "2024-11-22T14:04:50Z")

</div>

I have been trying to visualize

1. a histogram output from survivor/stats and
2. custom made `.png` plots

I followed the requirements [here](https://docs.seqera.io/multiqc/custom_content) (added `_mqc` suffix to stats and png), yet I cannot see them being added to the final report.

Thus, I really can use of a pair of expert eyes to take a look. I already have a PR on the concept, so that mentioned changes can be seen:

> <https://github.com/nf-core/variantbenchmarking/pull/108/files#diff-5b56e1387e322ba70ed9af7ec3cddc1f4e0e1b73459fc77fe0fe261223dcec55>
>
> \<!--
> \# nf-core/variantbenchmarking pull request
> 
> Many thanks for contributing… to nf-core/variantbenchmarking!
> 
> Please fill in the appropriate checklist below (delete whatever is not relevant).
> These are the most common things requested on pull requests (PRs).
> 
> Remember that PRs should be made against the dev branch, unless you're preparing a pipeline release.
> 
> Learn more about contributing: \[CONTRIBUTING.md\](https://github.com/nf-core/variantbenchmarking/tree/master/.github/CONTRIBUTING.md)
> \--\>
> 
> \## PR checklist
> 
> \- \[\] This comment contains a description of changes (with reason).
> \- \[\] If you've fixed a bug or added code that should be tested, add tests!
> \- \[\] If you've added a new tool - have you followed the pipeline conventions in the \[contribution docs\](https://github.com/nf-core/variantbenchmarking/tree/master/.github/CONTRIBUTING.md)
> \- \[\] If necessary, also make a PR on the nf-core/variantbenchmarking \_branch\_ on the \[nf-core/test-datasets\](https://github.com/nf-core/test-datasets) repository.
> \- \[\] Make sure your code lints (\`nf-core pipelines lint\`).
> \- \[\] Ensure the test suite passes (\`nextflow run . -profile test,docker --outdir \<OUTDIR\>\`).
> \- \[\] Check for unexpected warnings in debug mode (\`nextflow run . -profile debug,test,docker --outdir \<OUTDIR\>\`).
> \- \[\] Usage Documentation in \`docs/usage.md\` is updated.
> \- \[\] Output Documentation in \`docs/output.md\` is updated.
> \- \[\] \`CHANGELOG.md\` is updated.
> \- \[\] \`README.md\` is updated (including new tool citations and authors/contributors).

Best,

---

<div class="post-metadata">

**Author:** ![vlad.savelyev](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/vlad.savelyev/32/576_2.png) [@vlad.savelyev](https://community.seqera.io/u/vlad.savelyev)\
**Post date:** [November 25, 2024, 2:16pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/2 "2024-11-25T14:16:48Z")

</div>

Hi Kübra! I can’t see the issue off the top of my head. Could you please isolate the multiqc command so I could reproduce the issue locally?

---

<div class="post-metadata">

**Author:** ![kubranarci](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/kubranarci/32/264_2.png) [@kubranarci](https://community.seqera.io/u/kubranarci)\
**Post date:** [November 25, 2024, 2:52pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/3 "2024-11-25T14:52:12Z")

</div>

I can send you a directory from work?

How can we do it?

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [November 25, 2024, 9:42pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/4 "2024-11-25T21:42:04Z")

</div>

Yup! Ideally zip a directory that contains some input files, a config and a `.command.run`

It doesn’t have to be a lot, just enough to try to replicate locally.

---

<div class="post-metadata">

**Author:** ![kubranarci](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/kubranarci/32/264_2.png) [@kubranarci](https://community.seqera.io/u/kubranarci)\
**Post date:** [November 26, 2024, 9:44am UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/5 "2024-11-26T09:44:49Z")

</div>

[970045ac74d5c3f181ff58e1818983.zip](https://community.seqera.io/uploads/short-url/iEOyNoPwSLUMob5ZbwpcVTctxsn.zip) (2.8 MB)  
perfect, hoping this would work 🙂

---

<div class="post-metadata">

**Author:** ![kubranarci](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/kubranarci/32/264_2.png) [@kubranarci](https://community.seqera.io/u/kubranarci)\
**Post date:** [November 26, 2024, 11:27am UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/6 "2024-11-26T11:27:40Z")

</div>

hello all,

Big thanks to @kbestak, he solved my problem! Apperantly (for me easy to miss) I needed to add “custom\_content” to run\_modules 😅

```auto
run_modules:
  - custom_content

```

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [November 27, 2024, 12:48pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/7 "2024-11-27T12:48:32Z")

</div>

Hooray! Well done, and thank you @kbestak 🙂

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [March 28, 2025, 3:26pm UTC](https://community.seqera.io/t/adding-custom-data-to-multiqc/1482/8 "2025-03-28T15:26:06Z")

</div>