Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • morning latte
    Member
    • Jun 2013
    • 91

    MEGAN annotation

    Hello experts,

    I am using MEGAN to parse BLAST result and have a question regarding it. When I used the "inspect" function of MEGAN, all the contigs had identified taxonomic information to species level even though some of them (usually most of them) were only identified to family or genus level from tree view or exported DSV format. Does anyone have any idea why identified species information in not shown on the tree view or DSV file? Any advice would be greatly appreciated. Hope I am making myself clear.
  • lorendarith

    #2
    I'm not sure I understood the situation, but maybe this will help.

    I guess when you are referring to all contigs having identified taxonomic information to species level you are talking about the output of BLAST and then when you are saying that some or all of them were only identified to family or genus level it is an output of MEGAN. Am I right?
    If so then it's maybe because of the LCA algorithm that MEGAN uses to assign hits to certain levels. There are options in MEGAN which define the criteria for hits being assigned to a certain level like minsupport and if the same BLAST query had several best hits in the database you used (among other MEGAN parameters to discard or keep reads). The default value for minsupport is [5] I think, which means you will only see species nodes in the tree which have at least 5 BLAST hits and all other (e.g.) species hits will be assigned to the higher node which is in this case genus.

    I hope this makes sense and is what you are actually asking for, lol.

    Comment

    • morning latte
      Member
      • Jun 2013
      • 91

      #3
      Thanks for your clear explanation. This was really helpful.

      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.
        Yesterday, 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:08 AM
      0 responses
      6 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-30-2026, 05:37 AM
      0 responses
      11 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-26-2026, 11:10 AM
      0 responses
      18 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-17-2026, 06:09 AM
      0 responses
      52 views
      0 reactions
      Last Post SEQadmin2  
      Working...