-
Notifications
You must be signed in to change notification settings - Fork 125
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
Custom protocol patch #42
Conversation
A quick patch to fix the handling of --protocol (specifically custom) options when passing off to miRtrace.
Amended documentation around `--protocol` to better reflect that the user can use a custom protocol and provide their own adapter and trimming parameters.
main.nf
Outdated
@@ -722,7 +723,7 @@ process mirtrace { | |||
mirtrace qc \\ | |||
--species $params.mirtrace_species \\ | |||
$primer \\ | |||
--protocol $protocol \\ | |||
$protocol_opt $protocol \\ |
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.
$protocol_opt $protocol \\ | |
$protocol_opt \\ |
I think that the current code will output the protocol name twice..
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.
Resolved within fixing the merge conflicts
Merging despite failing tests so that I can bring this change into #55 |
Implemented a fix for issue 41, where
--protocol custom
wasn't being accepted. This was due to miRtrace not having a defined argument for custom, which caused it to error out.Also added some documentation to make it clearer that there is a custom option for users to define their own adapter and trimming parameters if required.