Configure multiqc so that it can handle more than 500 rows

[sofstam]

Description

By default, MultiQC starts using violin plots when a table has 500 rows or more (https://docs.seqera.io/multiqc/getting_started/config) and the file multiqc_general_stats.txt was not generated for thoroughstingray case in production causing an issue in storing the case.

I am planning to move the configs of taxprofiler to servers as the rest of nf-pipelines.

#3853
https://github.com/Clinical-Genomics/servers/pull/1469

Fixed

• Configure multiqc so that it does not start using violin plots when a certain amount of rows has been reached.

How to prepare for test

• Ssh to relevant server (depending on type of change)
• Use stage: us
• Paxa the environment: paxa
• Install on stage (example for Hasta):

  bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_cg -t cg -b multiqc_patch -a

How to test

• Do ...

Expected test outcome

• Check that ...
• Take a screenshot and attach or copy/paste the output.

Tested the case on stage with the new configs and the file was being generated.

Review

• Tests executed by
• "Merge and deploy" approved by
  Thanks for filling in who performed the code review and the test!

This version is a

• MAJOR - when you make incompatible API changes
• MINOR - when you add functionality in a backwards compatible manner
• PATCH - when you make backwards compatible bug fixes or documentation/instructions

Implementation Plan

• Document in ...
• Deploy this branch on ...
• Inform to ...

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Karl-Svard]

Nice fix!

[henrikstranneheim]

👍

[sofstam]

Deploy on stage:

[sofstam]

Deploy on production: