-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trimmomatic logs not parsed properly #864
Comments
Thanks for the detailed issue 👍 I'll look into it as soon as I can. Phil |
Hi @cgirardot, The problem here is that Trimmomatic gets it's sample names from the command line used. As you pointed out, this is the same for every file in your case. The To get around this, I've added a new option to the code which allows you to set a config flag to tell the module to use the filename instead of the file contents. To use it, add the following config option: trimmomatic:
s_name_filenames: true Once you have this, everything should work as excepted. Let me know how you get on! Phil |
right on time fro Christmas ! Thx |
this is working great , thanks again. |
Hi all, Old issue, but wanted to note that I have added this behaviour as a general feature for any module / file search pattern in fa84c47 and will be included in the MultiQC v1.11 release. The documentation for this new feature is here: https://multiqc.info/docs/#using-log-filenames-as-sample-names I haven't removed the Trimmomatic-specific config described above, so that should still work. But I would recommend switching to the new system if you can as it may be removed in the future. Cheers, Phil |
Description of bug:
I try to assemble a report with Trimmomatic logs (amongst others). Trimmomatic was run in Galaxy, all the logs therefore refer to a fastq_r1 input file used to name the sample. To circumvent this, I am using the instruction:
to extract sample names from file names like
180518_mATAC_t1_1_trimmomatic.err
.Strangely this instruction is ignored for trimmomatic logs while the regex perfectly works for other modules ; so I end up with a single sample (i.e.
fastq_r1
) in the report section.MultiQC Error log:
File that triggers the error:
Attached is a zip with 10 logs and the config file
trimmomatic.zip
MultiQC run details (please complete the following):
Command used to run MultiQC:
multiqc -c multiqc_ATAC_config.yaml -n trimmo_test qc/trimmomatic/
MultiQC Version:
MultiQC v1.6
Operating System:
CentOS Linux release 7.4.1708 (Core)
Python Version:
Python 2.7.15
Method of MultiQC installation:
conda
The text was updated successfully, but these errors were encountered: