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

Reads have rejected SAM flags #38

Open
sinhaeti opened this issue Jan 22, 2019 · 3 comments
Open

Reads have rejected SAM flags #38

sinhaeti opened this issue Jan 22, 2019 · 3 comments

Comments

@sinhaeti
Copy link

Hi!

I'm having trouble with the output of the script smmipcollasper.py in tools. A large portion of my reads have rejected SAM flags. What flags are causing this? How can I avoid filtering via SAM flags?

Prior to running the script, basic filtering was already completed. For example (in the picture below), I started with 7450 reads. However, over 3000 filtered via SAM Flags.

image

@augustboyle
Copy link
Member

augustboyle commented Jan 22, 2019 via email

@sinhaeti
Copy link
Author

I already checked for the SAM flags. The flags I found were not concerning (83, 163, 2131). Is there a way to avoid filtering via SAM flags?

Prior data filtering already removed reads that were: too long/short, not paired, etc.

@augustboyle
Copy link
Member

It seems likely that the reads are being rejected because of a supplementary alignment (flag 2131), see this page: https://www.biostars.org/p/308853/

If you want to include those reads then add 2131, 2195, 2211, and 2147 to the good flags frozenset in the genome_sam_collapser.pyx on line 669.

However, given the way the MIP recognition works, it seems likely that it will fail MIP recognition. In that case, the MIP arms would not be trimmed. You can try a newer MIP analysis pipeline that may have more advanced QC: https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1007956

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