-
Notifications
You must be signed in to change notification settings - Fork 437
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
Fastp - Format_source to ensure WF usability and remove non-sanger input formats #6499
Conversation
@@ -379,10 +335,10 @@ $read_mod_options.base_correction_options.correction | |||
</inputs> | |||
|
|||
<outputs> | |||
<data name="out1" format="auto" label="${tool.name} on ${on_string}: Read 1 output"> | |||
<data name="out1" format_source="in1" label="${tool.name} on ${on_string}: Read 1 output"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does fastp compress the output if the input is compressed ?
I would assume all output is uncompressed ?
<data name="out1" format_source="in1" label="${tool.name} on ${on_string}: Read 1 output"> | |
<data name="out1" format="fastqsanger" label="${tool.name} on ${on_string}: Read 1 output"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tool itself produces a compressed output if the output name has the ext .gz regardless whether the input is compressed or not.
Actually i had it this way at the beginning, but changed to format_source to be able to connect the output to fastqsanger.gz inputs..
Co-authored-by: Marius van den Beek <[email protected]>
If there any other suggestions, please let me know. |
Fixes #6560 |
FOR CONTRIBUTOR:
format_source
to ensure WF usability. However 'paired' and 'paired_collection' useformat_source="in1"
orformat_source="in2"
which is not affecting functionality, but it is still wrong!('paired_collection' should useformat_source="paired_input['forward']"
orformat_source="paired_input['reverse']"
). I still didn't figure out how to solve that rather than creating distinct outputs for each 'paired' and 'paired_collection, Any Ideas, before I do this?@mvdbeek, @wm75 Could you review this please?