MultiQC with large tables backed by sqlite DBs

Ask for help
1

Hi all:

In pmultiqc, a library that does MultiQC for proteomics workflows, we have the option of loading some of the data quatified MultiQC Report in a previous version of the multiqc tables we were able to paginate over the proteins, also we were able to search and when plotting summarizies for columns Sactter plots, we were able to render all proteins. Since 1.29 multiqc we haven’t able, we had to modified the table to load only a subset of the entries.

Questions, does anyone does something like this? Has anyone tried to paginate over a lot of entries in multiqc tables with a DB as backend.

2

Hi @Yasset_Perez-Riverol , sorry we missed this. Pinging @ewels in case he might be able to shed some light on this.

3

I’m not sure what happened in 1.29 sorry :thinking: If you’re able to narrow it down more (eg. with git blame= then I can take a look into what the change was.

Generally speaking, I try to avoid parsing large data within MultiQC reports and view that outside of the remit of core MultiQC. MultiQC reports should be stand-alone as single HTML files and not have any external dependencies.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.