Skip to content

Question: Interpretation of MEME Table Output (FEL Metrics, Beta Values, LRT Calculation) + Total Branch Length = 0 (No Runtime Errors) #1967

@wxijia03

Description

@wxijia03

Hi HyPhy team/community,
I am using the MEME method in HyPhy to detect episodic positive selection across ~50 species. I ran the analysis via [hyphy meme --alignment ace2_aln.fas --tree ace2_tree.nwk] and did not receive any runtime errors; however, I have several critical questions about the output table and unexpected results, and would greatly appreciate your guidance:

Context for Reference

Input data: CDS alignment (FASTA, ~1000bp, 50 species) + phylogenetic tree (Newick format, unrooted)

Key observations:

All "total branch length" values in the MEME table are 0 (no errors during run).
LRT values in the table do not match manual calculations using the LogL values from MEME/FEL.

Image Image

Specific Questions

  1. FEL-related metrics in the MEME table
    I noticed the MEME output table includes metrics associated with FEL (Fixed Effects Likelihood), even though I only executed the MEME workflow.
    What is the purpose of including FEL metrics in the MEME table (e.g., comparison, model component, validation)?
    What are the statistical hypotheses for these FEL metrics in the MEME output context?
  2. Two beta values in MEME and model hypotheses
    I am unclear about the meaning of the two beta values reported in the MEME table:
    What do these two beta values specifically represent in the MEME mixed-effects model?
    My current understanding of MEME’s hypotheses is below—could you confirm if this is accurate?
    Null hypothesis (H₀): Beta values can vary across branches, but β ≤ α (no positive selection, only neutral/purifying selection).
    Alternative hypothesis (H₁): Beta values can vary across branches, and β > α (episodic positive selection is allowed for some site-branch combinations).
    Additionally, what are the statistical hypotheses for the FEL metrics in the far-right column of the table?
    Is the FEL metrics same as the FEL method?What's the difference between them?I noticed the site10 above,which get FEL alpha 0.00 in MEME table with alpha 13.44 which identified as “purifying site” in FEL. That's so strange.
  3. LRT value calculation discrepancy
    I attempted to calculate LRT values using the formula I assumed for MEME:
    LRT = -2 × (MEME LogL - FEL LogL)
    However, this produces inconsistent results with the table:
    For example, at site 114:
    MEME LogL = -33.38
    FEL LogL = -32.52
    Manual calculation: LRT = -2 × (MEME LogL - FEL LogL) ≈ 1.72
    Table-reported LRT for site 114: 6.81
    Is the formula I used incorrect? If so, what is the correct mathematical formula for MEME’s LRT value calculation (per site)?
    Why does this discrepancy occur?
  4. All "total branch length" values = 0 (no runtime errors)
    All rows in the MEME table show "total branch length = 0", even though my phylogenetic tree has non-zero branch lengths (verified by visualizing the tree in FigTree).
    Could this indicate an input error (e.g., tree format, alignment formatting, species ID mismatch between alignment and tree)?
    What other factors might cause total branch length to be 0 in MEME output (despite no errors)?
    Are there checks I can run to validate the input data compatibility with MEME?

Additional Info (if applicable)

I have verified:
Species IDs in the alignment FASTA match exactly with the tree Newick file (no typos/extra spaces).
The alignment is a valid CDS (length is multiple of 3, no stop codons in the middle).
The tree is in standard Newick format (tested with other phylogenetic tools, e.g., IQ-TREE, which recognizes branch lengths).
Thank you very much for your time and expertise—your clarification will help me correctly interpret the MEME results and troubleshoot the unexpected branch length issue.
Best regards,
wxijia03

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions