My multiqc-config-yml is based on another multiqc-config-yml which I inherited, and it might contain some suboptimal or even nonsensical parts, but it works fine for just one input png-file.
I also tried fn: "raw_mgc.png", that is, without the astrix; same result.
I tried giving the input-png-images prefixes like:
Thanks for your prompt answer, Phil. (I know you’ve recently been super busy teaching )
I’m a multiqc newbie. I have no problem with the soapnuke-plots going into separate report sections. However, the number of soapnuke-jobs is variable, so I guess the number of “soapnuke-sections” in the report will also need to be variable I’m not sure how that can be handled in the multiqc-config-yml, but I’ll have a look and probably come back for help
The best solution is to not embed images in MultiQC reports
Images are supported for Custom Content, but I generally don’t allow them for full MultiQC modules:
No images
MultiQC doesn’t know how many samples it will need to handle for a report, and as such every module should work with anything from 1-1000 samples. With images, you can’t have more than a couple before the report is unusable. Worse, the file size will bloat the HTML file and it will crash the browser surprisingly fast. It’s not accessible and the data cannot be exported into multiqc_data for downstream use.
Plots should be recreated within MultiQC by parsing the raw data and generating dynamic plots instead.
I almost never merge modules that include images into reports. If you really need images in your report, you can do this either via Custom Content or an unofficial plugin module. Feel free to discuss on the community forum if you think that your case is an exception. There have been one or two in the past.