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

MNV or two SNV #42

Open
aledj2 opened this issue Mar 8, 2019 · 1 comment
Open

MNV or two SNV #42

aledj2 opened this issue Mar 8, 2019 · 1 comment

Comments

@aledj2
Copy link

aledj2 commented Mar 8, 2019

How does Varscan (v2.4.3) determine that two consecutive SNVs are part of the same event and call the variants as a MNV?

I have multiple examples where BAM files (which have gone through differing preprocessing/alignment steps) have resulted in different descriptions of the same variants.

There are two adjacent SNVs on the same strand. In one BAM file varscan calls this as a MNV, but in another it calls it as two SNVs.
Variants are called as SNVs even with near identical MAFs (40.11% and 40.17%) and similar read counts.

I am using varscan v2.4.3 and the mpileup2cns command:
samtools mpileup -f genome/grch37.fa -B -d 500000 -q 1 input.bam | java -Xmx12030m -jar /usr/bin/VarScan.v2.4.3.jar mpileup2cns --min-coverage 10 --min-reads2 5 --min_avg_qual 15 --min-var-freq 0.01 --min-freq-for-hom 0.75 --p-value 0.05 --strand-filter 0 --output-vcf 1 --variants

@zgtman
Copy link

zgtman commented Sep 8, 2022

Hi did you please solve this issue? I am facing the same problem. Or is there any tool to convert two phased SNV to MNV?

Best,

Paul

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