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

0 had sufficient coverage for comparison #50

Open
jingmeng-bioinformatics opened this issue Oct 22, 2019 · 1 comment
Open

0 had sufficient coverage for comparison #50

jingmeng-bioinformatics opened this issue Oct 22, 2019 · 1 comment

Comments

@jingmeng-bioinformatics
Copy link

jingmeng-bioinformatics commented Oct 22, 2019

I ran VarScan2 on my paired pileup files, and I do not think there are problems with the input files (please see attached a part of the input files), but I really do not understand why it gave me output like: 0 had sufficient coverage for comparison

java -jar ~/Downloads/varscan-master/VarScan.v2.4.4.jar somatic ~/normal.pileup ~/tumor.pileup --output-snp ~/snp.vcf --output-indel ~/indel.vcf --min-coverage-tumor 8 --output-vcf 1 --min-var-freq 0.075 --strand-filter 1

65821 positions in tumor
65821 positions shared in normal
0 had sufficient coverage for comparison
0 were called Reference
0 were mixed SNP-indel calls and filtered
0 were removed by the strand filter
0 were called Germline
0 were called LOH
0 were called Somatic
0 were called Unknown
0 were called Variant

normal.pileup.txt
tumor.pileup.txt

I tried other versions of VarScan2 and get the same result. Can you please help me check what caused the problem? Thanks very much for your time!

@ej354
Copy link

ej354 commented Aug 31, 2023

I'm having the same issue, did you solve this?

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