Update FastQC/Falco wrappers to make output of pairs compatible with multiQC#7839
Update FastQC/Falco wrappers to make output of pairs compatible with multiQC#7839lldelisle wants to merge 16 commits intogalaxyproject:mainfrom
Conversation
Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
|
I think we want to encourage use of falco, that is supposed to be a faster drop-in replacement for fastqc, do we also need to update that wrapper ? |
|
I am doing the same modification on falco wrapper just now. |
Make output labels unique to pass lint Co-authored-by: Lucille Delisle <lucille.delisle@unige.ch>
|
Here is the new version with a single execution with one or 2 input files as @bgruening suggested. |
|
@bgruening / @mvdbeek would you have time to have a look? |
|
@lldelisle the changes look fine to me, but I'm a bit confused how much this really helps. Are you thinking of this in conjunction with #2028 ? Cause without this, the status quo is:
In contrast with the change here, you'd have to do:
So you really only save a step if MultiQC can deal with paired collections? Is that what it is, or am I simply wrong? |
|
You don't need to flatten before giving to MultiQC. You can give to MultiQC the list:paired and the sample name is taken from the report itself not from the identifiers. |
|
So before:
After:
|
|
With this PR, we don't need #2028 and we simplify tutorials and workflows |
|
Currently if you do:
The identifier is forward for all forwards and reverse for all reverse, then you get only one result. Even if you do:
You get the same result: only one forward and one reverse is displayed. |
|
Mmmh this is unfortunate. I will think about it. |
Co-authored-by: Wolfgang Maier <maw.public+github@posteo.de>
lldelisle
left a comment
There was a problem hiding this comment.
Maybe I should change the type of output collection
| <filter>generate_summary</filter> | ||
| <filter>input_type_select['input_type'] == 'individually' and generate_summary</filter> | ||
| </data> | ||
| <collection name="html_files" format="html" type="paired" label="${tool.name} on ${on_string}: Webpages"> |
There was a problem hiding this comment.
Maybe should be type="list"
| <data name="reverse" from_work_dir="*reverse_fastqc_report.html" /> | ||
| <filter>input_type_select['input_type'] == 'paired'</filter> | ||
| </collection> | ||
| <collection name="text_files" format="txt" type="paired" label="${tool.name} on ${on_string}: RawData text files"> |
There was a problem hiding this comment.
Maybe should be type="list"
| <data name="reverse" from_work_dir="*reverse_fastqc_data.txt" /> | ||
| <filter>input_type_select['input_type'] == 'paired'</filter> | ||
| </collection> | ||
| <collection name="summary_files" format="txt" type="paired" label="${tool.name} on ${on_string}: SummaryData text files"> |
There was a problem hiding this comment.
Maybe should be type="list"
| <data format="txt" name="text_file" from_work_dir="output.txt" label="${tool.name} on ${on_string}: RawData" > | ||
| <filter>input_type_select['input_type'] == 'individually'</filter> | ||
| </data> | ||
| <collection name="html_files" format="html" type="paired" label="${tool.name} on ${on_string}: Webpages"> |
There was a problem hiding this comment.
Maybe should be type="list"
| <data name="reverse" from_work_dir="output_reverse.html" /> | ||
| <filter>input_type_select['input_type'] == 'paired'</filter> | ||
| </collection> | ||
| <collection name="text_files" format="txt" type="paired" label="${tool.name} on ${on_string}: RawData text files"> |
There was a problem hiding this comment.
Maybe should be type="list"

I handle differently pairs to enable to keep both identifiers in report and therefore be compatible with multiQC directly.
Before, when given a collection: list:paired, it will create one job per fastq and in the report the filename would be forward/reverse for all pairs.
Now, it will create one job per pair and in the report the filename is blabla_forward blabla_reverse blublu_forward blublu_reverse.
FOR CONTRIBUTOR:
There are two labels that allow to ignore specific (false positive) tool linter errors:
skip-version-check: Use it if only a subset of the tools has been updated in a suite.skip-url-check: Use it if github CI sees 403 errors, but the URLs work.