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

Set min insert size with -I option. Why do I still get proper pairs with insert size < min insert size? #419

Open
js72587 opened this issue May 3, 2024 · 0 comments

Comments

@js72587
Copy link

js72587 commented May 3, 2024

I have used the -I parameter to set the mean, stdev, max, and minimum insert size instead of using BWA-MEM's insert size calculation. I've set it to -I 400,150,1500,100.

Setting the -I parameter, I would expect that pairs w/ insert size < 100 would not be flagged as a proper pair. However, I do get one mapped proper pair with the insert size 88. Am I misunderstanding this parameter? I did read from other forums that some people don't recommend using the "proper pair" flag, but I would still like to understand why this happens with the -I option and what I can do to set a minimum insert size correctly.

I would greatly appreciate any explanation on why this may happen with BWA-MEM. Thank you very much.

@js72587 js72587 changed the title Why does bwa-mem bam still contain reads with insert size < minimum insert size specified with -I? Set minimum insert size with -I option. Why do I still get proper pairs with insert size < min insert size? May 3, 2024
@js72587 js72587 changed the title Set minimum insert size with -I option. Why do I still get proper pairs with insert size < min insert size? Set min insert size with -I option. Why do I still get proper pairs with insert size < min insert size? May 3, 2024
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

1 participant