What is the minimum read lenght to filter in modern samples?
1
0
Entering edit mode
2.9 years ago
lud_0911 • 0

Hi,

I have 2x150 pb NovaSeq 6000 platform reads. I am familiarized to work with ancient DNA, but now I have to work with modern data. I used the cutadapt to filter out reads with min lenght of 35 bp and quality 30. Should I have used different values? What would be the difference if I use 80 bp for the minimum read lenght? By now, does someone has papers that support the values to use in modern data?

Thanks so much.

minimum lenght DNA modern read • 928 views
ADD COMMENT
2
Entering edit mode
2.9 years ago
GenoMax 141k

If you are aligning to a reference then no trimming, both based on quality and length, should be needed. Aligner should take care of clipping parts of reads that don't align. That said, if you have 150 bp reads and you end up with reads of length < 35 bp after trimming then you may have bad libraries (short inserts) or crappy sequencing (poor Q scores) (for normal DNA samples). Trimming at Q30 is really strict and should only be needed for de novo work.

ADD COMMENT
0
Entering edit mode

Thanks for your answer GenoMax. So you are saying that I donĀ“t need to be worry with the reads <35 bp in lenght because they won't pass in quality? Because I did my analysis filtering reads <35 bp, not <80 bp (a longer lenght for example). Should I redo with longer reads only?

ADD REPLY
0
Entering edit mode

What I was saying was that with normal (non-ancient DNA) data you should not have reads getting trimmed down to < 35 bp unless you have extremely short inserts or have very poor quality sequencing (which would lead to a large part of the read being trimmed off using your trimming criteria).

In practice, you can get away without trimming if you are aligning to a good reference. Most aligners will soft-clip reads as needed.

ADD REPLY

Login before adding your answer.

Traffic: 1524 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6