# Reports with large sample numbers

**URL:** <https://community.seqera.io/t/reports-with-large-sample-numbers/349>\
**Category:** Ask for help\
**Tags:** multiqc\
**Created:** [December 14, 2023, 7:02pm UTC](https://community.seqera.io/t/reports-with-large-sample-numbers/349 "2023-12-14T19:02:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![acboulet](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/acboulet/32/358_2.png) [@acboulet](https://community.seqera.io/u/acboulet)\
**Post date:** [December 14, 2023, 7:02pm UTC](https://community.seqera.io/t/reports-with-large-sample-numbers/349/1 "2023-12-14T19:02:47Z")

</div>

A general question.

I’ve been using MultiQC for a few years, and am now dealing with larger sample numbers. While MultiQC supports both flat and interactive plots, each has its drawbacks. Flat plots lack the interactivity that MultiQC offers, making them hard to review. On the other hand, interactive plots can be slow and cumbersome when dealing with multiple modules and hundreds to thousands of samples.

Does anyone have tips or strategies for presenting results from large sample sets more effectively in MultiQC? I’m interested in hearing about any creative solutions from those with more experience.

---

<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:** [December 15, 2023, 8:39am UTC](https://community.seqera.io/t/reports-with-large-sample-numbers/349/2 "2023-12-15T08:39:17Z")

</div>

There aren’t a lot of great solutions to this that I know of - as you say, both approaches are somewhat compromises. One option you haven’t mentioned is using the parsed data that is generated in `multiqc_data` and pulling that into custom scripts / notebooks etc. to generate your own bespoke plots for presentation. This allows a bit more flexibility in how you display outputs. It’s a bit of a pain to need to write your own script though, and kind of goes against the whole point of MultiQC.

Dealing with huge numbers of samples was one of the motivations for starting the [MegaQC](https://github.com/ewels/MegaQC) project long ago:

> **[GitHub - ewels/MegaQC: Web application to collect and visualise data across...](https://github.com/ewels/MegaQC)**
>
> Web application to collect and visualise data across multiple MultiQC runs. - GitHub - ewels/MegaQC: Web application to collect and visualise data across multiple MultiQC runs.

That project has largely stalled though and is not super usable. I’m hoping that we can build something new before long (2024?) which will meet this need.

Phil