Skip to content
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

Question on the use of paired end reads #8

Closed
carden24 opened this issue Oct 7, 2014 · 1 comment
Closed

Question on the use of paired end reads #8

carden24 opened this issue Oct 7, 2014 · 1 comment

Comments

@carden24
Copy link

carden24 commented Oct 7, 2014

You mention in the documentation that when paired end reads are available only one set of the pair should be use. Could you expand the reason for this? Running it with both pairs will generate a wrong results or it will decrease performance,
thanks

Erick

@lmrodriguezr
Copy link
Owner

The problem with paired reads is that they are not independent events. If your average insert size is longer than twice the read length, the coverage will likely be underestimated. On the other hand, if you have small average insert sizes (close to a read length), the coverage will likely be overestimated. However, if you have a small insert size and you can combine most pairs (e.g., using PEAR), the resulting merged reads are probably better estimators. In all other cases, I recommend simply using one of the sister reads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants