Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • arkilis
    Senior Member
    • Jul 2013
    • 119

    Geneious SNP detection parameter setting

    Is there anyone here using Geneious. Not quite sure about the parameters setting on "Find Variations/SNPs." Here is what I did in my project.

    Any suggestion is welcome. thx



    Last edited by arkilis; 10-03-2013, 05:09 PM.
  • ThePresident
    Member
    • Jun 2012
    • 72

    #2
    I'm quite in it those days, but I'm not using Geneious. However, this is what I can see from the printscreen above:

    1. Minimum coverage: I would set it higher, perhaps around 10. That's the number of times your SNPs will be covered. Logically, if you have only two reads covering the SNPs, that chance that both reads are errors is quite bigger than if you had 20 reads covering the same base.

    2. Minimum Variant Frequency: for every SNPs that your program will find, you will have a certain number of reads that match the reference sequence, and a certain number of reads that match the alternative (SNP) call. Minimum Variant Frequency of 0.25 means that you have 1 alternative call and 3 reference calls (1/4=0.25). You can set it low in the beginning, but keep in mind that higher values are "better" for accurate calls.

    3. Maximum Variavnt p-value: you control the risk of the call being made purely by chance. Go logically and set it according to the risk you want to take.

    I think the rest of the options speak for itself.

    Comment

    • arkilis
      Senior Member
      • Jul 2013
      • 119

      #3
      Originally posted by ThePresident View Post
      I'm quite in it those days, but I'm not using Geneious. However, this is what I can see from the printscreen above:

      1. Minimum coverage: I would set it higher, perhaps around 10. That's the number of times your SNPs will be covered. Logically, if you have only two reads covering the SNPs, that chance that both reads are errors is quite bigger than if you had 20 reads covering the same base.

      2. Minimum Variant Frequency: for every SNPs that your program will find, you will have a certain number of reads that match the reference sequence, and a certain number of reads that match the alternative (SNP) call. Minimum Variant Frequency of 0.25 means that you have 1 alternative call and 3 reference calls (1/4=0.25). You can set it low in the beginning, but keep in mind that higher values are "better" for accurate calls.

      3. Maximum Variavnt p-value: you control the risk of the call being made purely by chance. Go logically and set it according to the risk you want to take.

      I think the rest of the options speak for itself.
      Thanks for your reply.

      1. minimum coverage. I think it is more depended on platform. For NGS data, you are right. 10 reads at least is more secured. For Sanger, I think two might be enough. Since Sanger data always has a good quality.

      2. What you saying makes much sense.

      3. HARD PART! since I don't know a proper value here. If I decrease the value, less 'SNPs' will come out. Hope those who play Geneious can see this post and provide with a moderate value..

      Thanks!
      Last edited by arkilis; 10-03-2013, 08:05 PM.

      Comment

      • vishnuamaram
        Member
        • Jun 2013
        • 41

        #4
        Hey Arkilis,

        Geneious is a commercial tool. So, i dont think much people use it.

        But, the option parameters are more or less same in all available variant calling tools.

        Say, for example VarScan. just have a look into it.

        Comment

        • arkilis
          Senior Member
          • Jul 2013
          • 119

          #5
          Originally posted by vishnuamaram View Post
          Hey Arkilis,

          Geneious is a commercial tool. So, i dont think much people use it.

          But, the option parameters are more or less same in all available variant calling tools.

          Say, for example VarScan. just have a look into it.
          That is a good idea.

          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, Today, 11:05 AM
          0 responses
          6 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 07-02-2026, 11:08 AM
          0 responses
          27 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          25 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          25 views
          0 reactions
          Last Post SEQadmin2  
          Working...