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

iVar miss-priming issues? #91

Open
dcm9123 opened this issue Mar 22, 2021 · 1 comment
Open

iVar miss-priming issues? #91

dcm9123 opened this issue Mar 22, 2021 · 1 comment

Comments

@dcm9123
Copy link

dcm9123 commented Mar 22, 2021

Hi!
I am currently working on the IDseq metagenomics platform to identify mapped reads to SARS-CoV-2. Basically my project consists on the sequencing of all reads from a clinical samples with COVID-19, and assemble the viral genome. The wet lab protocol is from MSSPE, so I enrich the sequencing library preparation with 73 primers spanning the viral genome. To test the pipeline, I have uploaded negative controls (water controls with the primers), and iVar seems to report a few reads that partially match the primers (about 10, 20, and up to 200 reads). Could this be some sort of miss-priming issue? Would this be fixed by using the ivar getmasked? Or is this something else? (I am attaching a picture of how my results look in this pipeline)
Screen Shot 2021-03-21 at 11 21 02 PM

The IDSeq pipeline uses the following commands:


ivar trim -e -i ivar.bam -b "~{primer_bed}" -p ivar.out

ivar consensus -q "~{ivarQualThreshold}" -t "~{ivarFreqThreshold}" -m "~{minDepth}" -n N -p "~{prefix}primertrimmed.consensus"

Thanks a lot for your help!

@gkarthik
Copy link
Member

Hi, ivar will trim any reads that start or end within the coordinates provided in the BED file. It does not take the sequence of bases itself into account. So, it's possible that a few reads started at primer positions and iVar trimmed those. Does that answer your question?

ivar getmasked is used to report if there are mismatches between the primer and the reference sequence. That is for downstream filtering for variant calling so should not affect primer trimming.

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

No branches or pull requests

2 participants