You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for amazing work on this pipeline, it's very comprehensive.
I am wondering if there is any way to specify --2colour / --nextseq flag during trimming step. I reviewed few samples from Zymo RRBS library and sequenced with NovaSeq. All of the samples have G over call at the end of the reads, leading to high GC content. See https://sequencing.qcfail.com/articles/illumina-2-colour-chemistry-can-overcall-high-confidence-g-bases/
Hello,
Thank you for amazing work on this pipeline, it's very comprehensive.
I am wondering if there is any way to specify
--2colour
/--nextseq
flag during trimming step. I reviewed few samples from Zymo RRBS library and sequenced with NovaSeq. All of the samples have G over call at the end of the reads, leading to high GC content. See https://sequencing.qcfail.com/articles/illumina-2-colour-chemistry-can-overcall-high-confidence-g-bases/Describe the solution you'd like
Have an option to enable or disable
--2colour
/--nextseq
trimming capabilities, I believe--trim_nextseq
in nf-core/sarek/2.7.2 does the same thing: https://nf-co.re/sarek/2.7.2/parameters#trim_nextseqDescribe alternatives you've considered
Manually trimming FastQ first and then disable "trimming" step during "nf-core/methylseq"
The text was updated successfully, but these errors were encountered: