Seqanswers Leaderboard Ad



No announcement yet.
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Samtools mpileup with -B or -E falg for Varscan

    I just ran varscan on mpileup data with -B or -E flag. And there is quite a difference indeed (see below). Should varscan always be used on mpileup data generated with the -B flag?

    samtools mpileup -d 10000 -S -B -C 50 -P Illumina -f hg19.fa normal.bam > normal.mpileup
    samtools mpileup -d 10000 -S -B -C 50 -P Illumina -f hg19.fa tumor.bam > tumor.mpileup
    java -jar VarScan.v2.2.10.jar somatic normal.mpileup tumor.mpileup tumor_vs_normal
    java -jar VarScan.v2.2.10.jar processSomatic tumor_vs_normal.snp
    48198 VarScan calls processed
    3168 were Somatic (1229 high confidence)
    37882 were Germline
    6937 were LOH


    samtools mpileup -d 10000 -S -E -C 50 -P Illumina -f hg19.fa normal.bam > normal.baq.mpileup
    samtools mpileup -d 10000 -S -E -C 50 -P Illumina -f hg19.fa tumor.bam > tumor.baq.mpileup
    java -jar VarScan.v2.2.10.jar somatic normal.baq.mpileup tumor.baq.mpileup tumor_vs_normal.baq
    java -jar VarScan.v2.2.10.jar processSomatic tumor_vs_normal.baq.snp
    7593 VarScan calls processed
    517 were Somatic (191 high confidence)
    6406 were Germline
    636 were LOH


    • #17
      Right, it's definately samtools pileup that is causing the problem. If you comapre the .sam file, and the two pileups (with and without -B) in regions where SNPs are being missed, you can see the problem. pileup -B will faithfully represent the letter quality scores found in the .sam file. pileup without -B will sometimes report the quality of those letters as being terrible, which causes SNP calling softwares to ignore them as too poor quality.

      Using -B is supposed to reduce the number of false positives. There might be applications where that potential trade off is worth it, but for what it's worth, I'm skeptical. In my work, I'd much rather sift through false positives than miss real mutations.


      • #18
        Hello everyone,
        I'm currently also experiencing problems with Varscan somatic, but they seem different from what has been described here. I've tried using the -B option for samtools pileup, but still I get completely wrong allele counts for my tumor sample for supposedly somatic mutations with very low p-values.
        One example:
        Create samtools pileup files with the command:
        samtools pileup -Bf ref.fasta in.bam > out.pileup
        run varscan somatic:
        java -Xmx16g -jar /home/sukmb205/software/VarScan.v2.2.11.jar somatic normal.pileup tumor.pileup outfile.var
        output varscan:
        chrom	position	ref	var	normal_reads1	normal_reads2	normal_var_freq	normal_gt	tumor_reads1	tumor_reads2	tumor_var_freq	tumor_gt	somatic_status	variant_p_value	somatic_p_value	tumor_reads1_plus	tumor_reads1_minus	tumor_reads2_plus	tumor_reads2_minus
        chr5	88171909	A	T	46	0	0%	A	91	95	51.08%	W	Somatic	1.0	6.837592912705086E-13	0	91	0	95
        Looks like quite a good somatic mutation concerning the p-value, but when I look into IGV, NOT ONE read actually supports the T in the tumor sample. Instead, there is a single read at this position that has been aligned with a 308bp deletion, could this be the problem??

        pileup tumor:
        chr5	88171909	A	63	.,,,,,,,,,,,,,,,,,,,,,,..,,,.$.,.,,,,,,.,,,..,,-308actcctcaaactaccttcccacaaagccatttaagttaaatggtacatttacagactcacctacatgaaggatataacttaaaacatctgcttagacacatacgttctgttcagatataaaaaatgtggcaaaaatttttaaaaatataggaccactatattcttaaaatgtgtgttcttctgtgtgtgtgtgttcattcattcaagagatctttgactgcaattaggtagtcggtcctataaaggcttccttgtgtgacgataatttctaaaagtaaaatgctccagtgaatatttctgctaaataa,,,,,,.,....,,...	/2.*114I,1<(%040":+3/--+?%.-.CE2;/3*0-B8=).0II--7,+,II%I09@*CII
        pileup normal:
        chr5	88171909	A	71	...$.,,,,,,,,,,,.,,,,,,,,,.,,,,.,,.,,,,,,..,,,.,.,,,..,,,,,,.,...,....^X.^(.	BE,9=2++H8I31.)89,=I).2II=1I,+/8I51I>*2,7+.1I.I%-*-1I/2A-I/3@:I.5I8II(I
        I'm seeing similar things at all the high quality somatic mutations that were called and I've tried using mpileup instead of pileup, with option -B, without -B etc. I just don't know what the problem is!
        I would really appreciate some comments on this, thanks!


        • #19
          Am I the only one with this issue? I still can't figure out what the problem is, in other datasets Varscan worked fine for me, but if this isn't fixed I'm going to have to use a different tool...


          • #20

            I've just landed in this post after a long time without using somatic calling tools.

            I am wondering if you solved this, I have no idea why it happened.

            Anyway, I've just downloaded the Varscan2, and I've noticed that it incorporates a filter that, among other things, it seems to remove those SNPs which appear close to indels. Could it help to you?


            • #21
              Varscan results vs Genomeview

              Dear all,
              I am using /VarScan/x86_64/2.3.3
              VarScan Somatic
              I seem to have really big differences in SNP coverages in the SNP output file of Varscan and that of the visualized .bam file in Genomeview (similar to IGV).
              Has anyone found out yet what causes this?


              Latest Articles


              • seqadmin
                Latest Developments in Precision Medicine
                by seqadmin

                Technological advances have led to drastic improvements in the field of precision medicine, enabling more personalized approaches to treatment. This article explores four leading groups that are overcoming many of the challenges of genomic profiling and precision medicine through their innovative platforms and technologies.

                Somatic Genomics
                “We have such a tremendous amount of genetic diversity that exists within each of us, and not just between us as individuals,”...
                Yesterday, 01:16 PM
              • seqadmin
                Recent Advances in Sequencing Analysis Tools
                by seqadmin

                The sequencing world is rapidly changing due to declining costs, enhanced accuracies, and the advent of newer, cutting-edge instruments. Equally important to these developments are improvements in sequencing analysis, a process that converts vast amounts of raw data into a comprehensible and meaningful form. This complex task requires expertise and the right analysis tools. In this article, we highlight the progress and innovation in sequencing analysis by reviewing several of the...
                05-06-2024, 07:48 AM





              Topics Statistics Last Post
              Started by seqadmin, Yesterday, 07:15 AM
              0 responses
              Last Post seqadmin  
              Started by seqadmin, 05-23-2024, 10:28 AM
              0 responses
              Last Post seqadmin  
              Started by seqadmin, 05-23-2024, 07:35 AM
              0 responses
              Last Post seqadmin  
              Started by seqadmin, 05-22-2024, 02:06 PM
              0 responses
              Last Post seqadmin