Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Jackken
    Member
    • Dec 2012
    • 10

    Genotyping problem using VarScan 2

    Hi,

    Tried to use VarScan 2 to get SNP calls (tumor/normal paired samples). However, I don't think the output makes sense.

    For example, the pileup file for the normal looks like,

    chr1 11765 N 6 GgGGGG AG@?AF
    chr1 11766 N 6 TtTTTT AG6:4E
    chr1 11767 N 6 GgGGGG CEBA=F
    chr1 11768 N 6 TtTTTT CF@;AG

    The VarScan 2 output:

    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
    ...

    chr1 11766 N T 0 9 100% T 0 9 100% T Germline 1.101911
    9461502356E-10 1.0 0 0 6 3 0 0 7 2


    Not sure what went wrong when the pileup file show read count is 6 (bold) at location 11766, but the VarScan has a count of 9 (bold).

    Thanks!
  • Jackken
    Member
    • Dec 2012
    • 10

    #2
    Any suggestions?

    By the way, the script I used is,

    java -jar VarScan.v2.3.3.jar somatic pileup.file1 pileup.file2 output.file


    Thanks!

    Comment

    • dkoboldt
      Member
      • Mar 2009
      • 62

      #3
      Jackken,

      That's a bit puzzling... it looks like you didn't provide a reference to SAMtools mpileup (-f) when generating the pileup file, which is why the reference base is always "N". This can cause some issues in read counting.

      Further, I can't replicate your result if I use the pileup and command that you provided, at least, not without having the tumor pileup. Would you send me your pileup files for tumor and normal?

      Also, we're kind of moving away from the two individual pileup files model for VarScan. It's still supported, but I think you're better off running a single mpileup command with both samples, and then calling VarScan somatic with the --mpileup 1 option:
      samtools mpileup -f reference.fa normal.bam tumor.bam >both.mpileup
      java -jar VarScan.jar somatic both.mpileup both.varScan.output --mpileup 1

      Comment

      Latest Articles

      Collapse

      • GATTACAT
        Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
        by GATTACAT
        Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
        07-01-2026, 11:43 AM
      • SEQadmin2
        Nine Things a Sample Prep Scientist Thinks About Before Sequencing
        by SEQadmin2


        I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

        Here are nine questions we think about, in roughly the order they matter, before...
        06-18-2026, 07:11 AM

      ad_right_rmr

      Collapse

      News

      Collapse

      Topics Statistics Last Post
      Started by SEQadmin2, 07-02-2026, 11:08 AM
      0 responses
      22 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-30-2026, 05:37 AM
      0 responses
      23 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-26-2026, 11:10 AM
      0 responses
      22 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-17-2026, 06:09 AM
      0 responses
      55 views
      0 reactions
      Last Post SEQadmin2  
      Working...