-
Notifications
You must be signed in to change notification settings - Fork 705
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
Add umicollapse as an alternative to umi-tools #1369
base: dev
Are you sure you want to change the base?
Conversation
TODO: - [ ] Benchmark paired ends mode - [ ] Include in multiqc
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.
Excellent work, clean and well-structured! I think, you found very smart solutions to not duplicate too much of the code.
Of course, we should wait for the lead developers of the pipeline to review as well prior to merging, but in general you have my support for this addition! Ideally, your fix for umicollapse
would also be included in the form of an updated tool version.
Please don't forget the Changelog later and also to add your name to the contributors (well deserved)!
@@ -30,6 +30,7 @@ params { | |||
with_umi = false | |||
skip_umi_extract = false | |||
umitools_extract_method = 'string' | |||
umi_dedup_tool = 'umicollapse' | |||
umitools_grouping_method = 'directional' |
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.
Reading that makes we wonder if we should be conservative regarding the parameter names or make them more generic, e.g. renaming umitools_grouping_method
to something like umi_grouping_method
/ umi_dedup_grouping_method
etc.
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.
Yes, I thought about that too. Depends on your policy for introducing breaking changes between versions. If the authors are OK, I can rename these parameters to be more generic.
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.
Thanks for the quick review. I am tracking all remaining items in the PR summary.
@@ -30,6 +30,7 @@ params { | |||
with_umi = false | |||
skip_umi_extract = false | |||
umitools_extract_method = 'string' | |||
umi_dedup_tool = 'umicollapse' | |||
umitools_grouping_method = 'directional' |
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.
Yes, I thought about that too. Depends on your policy for introducing breaking changes between versions. If the authors are OK, I can rename these parameters to be more generic.
Signed-off-by: Siddhartha Bagaria <[email protected]>
I checked the output of UMICollapse, and it definitely does not follow the assumptions stated in prepare_for_rsem.py. So |
@MatthiasZepper all remaining tasks are now done. Please take another look. |
Unfortunately, the UMICollapse module has not yet been upgraded... |
Checklist:
PREPARE_FOR_SALMON
is needed