-
Notifications
You must be signed in to change notification settings - Fork 6
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
UMI-tools extract #71
Conversation
This reverts commit 38f586b.
Co-authored-by: Robrecht Cannoodt <[email protected]>
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.
Great job on reducing the test data size! This is so much better, thanks!
I have a small question:
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.
I'm a bit confused by some of the arguments in this component. I feel like maybe too much inspiration was drawn from the nf-core umitools/extract?
LMKWYT
- name: --bc_pattern | ||
type: string | ||
description: | | ||
The UMI barcode pattern to use e.g. 'NNNNNN' indicates that the first 6 nucleotides | ||
of the read are from the UMI. |
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.
Is this argument not required? Should there not be an alternative -p
? What is the difference between -p PATTERN
and --bc-pattern
and --bc-pattern2
?
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.
I didn't notice that, it only appears in the help message but not in the documentation! I will add it, I believe it is an alternative for --bc-pattern only based on the output i get when using it.
- name: --read1_out | ||
type: file | ||
required: true | ||
description: Output file for read 1. | ||
direction: output | ||
- name: --read2_out | ||
type: file | ||
description: Output file for read 2. | ||
direction: 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.
Currently:
umi_tools extract
:
- Inputs:
- R1:
-I
- R2:
--read2-in
- R1:
- Outputs:
- R1:
-S
- R2:
--read2-out
- R1:
This component:
- Inputs:
- R1:
--input
- R2:
--read2_in
- R1:
- Outputs:
- R1:
--read1_out
- R2:
--read2_out
- R1:
I propose changing the inputs of the component to something consistent. Options:
--input
,--read2_in
,--output
,--read2_out
--input
,--input_r2
,--output
,--output_r2
Co-authored-by: Robrecht Cannoodt <[email protected]>
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.
LGTM!
Description
UMI-tools extract
Checklist before requesting a review
I have performed a self-review of my code
Conforms to the Contributing guidelines
Proposed changes are described in the CHANGELOG.md
I have tested my code with
viash ns test --parallel -q <name or namespace>
Check the correct box. Does this PR contain: