You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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!
The text was updated successfully, but these errors were encountered: