Maybe tricky, maybe not: Is there a semantic way t...
# multiqc
i
Maybe tricky, maybe not: Is there a semantic way to deal with per-sample tables in MultiQC? I have a structure like this
Copy code
sample1.csv
gene,count
gene1,3
gene2,8

sample2.csv
gene,count
gene2,4
gene3,6
I would like to get a separate table for each sample, without mixing the data. The number and names of samples cannot be assumed. I have tried Seqera AI, but the solutions it suggests are somewhat convoluted (dynamic config generation).
m
We do a similar thing in #C06PHJM0Y3D
our idea was actually to generate a different seqinspector per tag
which I guess is not really what you want
i
This could be an alternative solution
m
that's the relevant part to get a different multiqc per tag https://github.com/nf-core/seqinspector/blob/dev/workflows/seqinspector.nf#L393-L411
p
You can achieve it a few different ways - custom content, multiqc as a library etc
It's generally not something that the core library / module will support for a tool. MultiQC modules have to work for 1-100000 samples. Having 100k tables in a report is non bueno