-
Notifications
You must be signed in to change notification settings - Fork 38
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
Remove trimming #208
Remove trimming #208
Conversation
|
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, just suggesting to make it explicit that this is for Illumina samplesheets
(Apart from that I think trimming should be better documented, as mentioned in #207, but that can be a separate PR) |
Co-authored-by: Gregor Sturm <[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.
otherwise, looks good.
@@ -15,6 +15,7 @@ params { | |||
|
|||
// Options: trimming | |||
trim_fastq = true // [true, false] | |||
remove_adapter = true // [true, false] |
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.
When I first read this parameter, I interpret as trimming it, like removing from the sequence.
Reading the rest I know it refers to removing from the samplesheet to avoid trimmimg.
But, I just wanted to bring this up, as maybe the parameter can be more explicit to avoid such confusion.
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.
Thank you for your feedback. I understand the possible confusion about the parameter name. Since this parameter follows 10x's recommended method and is usually left as default, most users won't need to change it. If users do want to change it, they will likely have to read the documentation for details, so I don't think it should be too much of an issue.
This PR fixes this issue: #207
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).