Comparative And Ancestral Methods¶
Comparative analysis treats related species as statistically dependent. Ancestral reconstruction uses the same tree, branch lengths, and evolutionary assumptions to estimate unobserved states inside the tree. The runtime keeps the fitted model, uncertainty, and tree context attached to both kinds of result.
flowchart LR
traits["Tip traits"]
tree["Rooted tree<br/>with branch lengths"]
covariance["Evolutionary covariance"]
comparative["Signal · PGLS<br/>mode comparison"]
ancestral["Node states · branch changes<br/>transition histories"]
review["Diagnostics · sensitivity<br/>structured artifacts"]
tree --> covariance
traits --> comparative
covariance --> comparative
traits --> ancestral
tree --> ancestral
comparative --> review
ancestral --> review
Read Coefficients And Ancestors As Different Estimands¶
A comparative coefficient and an ancestral estimate may use the same tree and trait table, but they answer different questions:
| Result | Conditional question | Interpretation boundary |
|---|---|---|
| regression coefficient | how does the modeled response change with one design column after accounting for the declared phylogenetic covariance? | specific population, formula, contrast coding, transform, units, and covariance family |
| signal estimate | how compatible is observed trait resemblance with the named phylogenetic null or transformation? | statistic-specific scale and null; not a predictor effect |
| mode parameter | which process parameter best fits the declared tree and trait observations? | candidate family, tree time scale, identifiability, and bounds |
| ancestral value or state | what internal quantity is supported under the fitted model and rooted tree? | unobserved conditional estimate with node and tree uncertainty |
Accordingly, a coefficient does not describe an ancestral trajectory, and an ancestral reconstruction does not validate a regression mechanism. Even a numerically stable result changes meaning when the admitted taxa, observation unit, factor reference level, trait transform, or tree-derived covariance changes.
The Shared Contract¶
Every analysis begins with an explicit mapping between tree tips and trait rows. Missing taxa, duplicated identifiers, non-finite values, rooting, and branch-length units are scientific inputs rather than clerical details. A result is reviewable only when that mapping and the transformations applied to the traits are retained.
| Question | Native method families | Result that must remain visible |
|---|---|---|
| Do close relatives resemble one another? | contrasts, signal estimation and review | statistic, null or reference rule, fitted transformation, warnings |
| Does a predictor explain a response after phylogeny is modeled? | Brownian and OU covariance, PGLS, categorical contrasts, interactions | design terms, coefficients, covariance parameters, residual diagnostics |
| Which evolutionary mode best describes a continuous trait? | Brownian motion, OU, early burst, regime-rate and mode comparison | likelihood, parameters, information criteria, identifiability diagnostics |
| How does a discrete trait change? | Mk-family fitting, constrained transition models, mode recovery | state coding, rate matrix, transition constraints, model comparison |
| What states are supported at internal nodes? | continuous and discrete reconstruction, tree-set aggregation | node estimates or probabilities, intervals, ambiguity, tree sensitivity |
| How do lineages accumulate or partition diversity? | lineage, clade, trait-linked and sampling-aware diversification summaries | rate assumptions, sampling treatment, clade definitions, uncertainty |
Method And Record Locators¶
| Analysis | Public locator | Record to inspect first |
|---|---|---|
| phylogenetic regression | bijux_phylogenetics.comparative.run_pgls |
PGLSResult, design/covariance diagnostics, coefficient tables |
| phylogenetic signal | bijux_phylogenetics.comparative.summarize_phylogenetic_signal and estimate_pagels_lambda |
statistic, fitted lambda, permutation/profile evidence, exclusions |
| continuous mode fitting | fit_brownian_motion_model and fit_ornstein_uhlenbeck_model |
likelihood, parameters, optimizer and identifiability diagnostics |
| continuous ancestors | bijux_phylogenetics.ancestral.reconstruct_continuous_ancestral_states |
node estimates, uncertainty, branch changes, exclusions |
| discrete ancestors | bijux_phylogenetics.ancestral.reconstruct_discrete_ancestral_states |
state probabilities, transition model, optimizer state, exclusions |
These are runtime entry points, not claims of study parity. Evidence Book bundles identify which source analyses and result fields have governed comparisons.
Choose The Method From The Estimand¶
| Intended estimand | Required design choices | Common category error |
|---|---|---|
| strength of phylogenetic signal | trait, null/reference rule, tree scale, fitted or fixed transformation | treating signal as evidence for a predictor or causal mechanism |
| predictor effect conditional on phylogeny | response, design matrix, covariance family, taxon set | comparing coefficients from different reference levels or transformations |
| evolutionary mode | candidate family, likelihood convention, parameter count, tree time scale | treating the lowest information criterion as proof of biological truth |
| continuous ancestral value | evolutionary model, root treatment, node identity, uncertainty rule | reporting a conditional estimate as an observed historical value |
| discrete ancestral state | state coding, transition constraints, root prior, ambiguity policy | comparing probabilities under different state spaces |
| conclusion across plausible trees | tree-set identity, aggregation unit, between-tree summary | presenting one favored tree as though topology were fixed by the data |
Begin with the estimand, then select the runtime surface. Beginning with an available function and searching afterward for a biological interpretation reverses the scientific decision order.
Model Identity Before Values¶
A comparative result is identified by more than its formula. Record the taxa and order, tree and branch-length scale, response and predictor transforms, design-matrix columns and reference levels, covariance family and fitted parameters, missing-data policy, optimizer objective, bounds, and convergence state. An ancestral result additionally needs state coding, root treatment, transition constraints, and the node-identity convention.
Compare coefficients, likelihoods, or ancestral states only after this identity matches. Otherwise a small numerical difference can conceal a different model, and a large difference can be the expected consequence of a declared parameterization change.
PGLS And Trait Covariance¶
Phylogenetic generalized least squares replaces the independence assumption of ordinary regression with a covariance matrix derived from the tree and an evolutionary model. Brownian covariance, OU covariance, and fitted lambda transformations encode different dependence structures; they are not interchangeable labels for the same correction.
Interpret coefficients together with the formula, categorical reference levels, interaction parameterization, trait transformations, fitted covariance parameters, and residual checks. A small p-value cannot repair a taxon mismatch, an unidentified covariance model, or a predictor whose effect changes under modest tree perturbations.
Evolutionary Modes And Model Comparison¶
Brownian motion models accumulated change along branches. OU models add attraction toward an optimum. Early-burst and regime-rate models alter how evolutionary variance changes through time or among mapped regimes. Their parameters have meaning only under the tree scale and implementation convention used to fit them.
Information criteria rank the declared candidate set; they do not establish that the winning model is biologically true. Retain candidate definitions, parameter counts, likelihood convention, optimizer diagnostics, and weight or delta calculations. Weak OU identifiability and boundary estimates should be reported as limitations, not converted into categorical conclusions.
Ancestral Reconstruction¶
Continuous reconstruction produces node estimates, uncertainty, and branch changes under a named continuous-trait model. Discrete reconstruction produces state probabilities or supported state sets under an explicit state coding and transition model. Ordered states, forbidden transitions, unresolved tips, and root treatment can materially change the answer.
Tree-set workflows repeat reconstruction across plausible trees and aggregate the results. This separates conditional uncertainty on one tree from topological uncertainty across trees. Neither should be summarized by a single favored-node value when the distribution is broad or multimodal.
For discrete models, continue with Discrete Ancestral States And Transitions. It separates fitted rates, full node-state probabilities, derived branch transitions, opportunity denominators, and stability across a tree set.
Sensitivity Is Part Of The Result¶
Review the fitted analysis across the assumptions that could change its interpretation:
- alternative rooting and branch-length treatments;
- taxon inclusion and influential clades;
- trait transformations, missing-data policy, and imputation;
- covariance or evolutionary-mode candidates;
- transition constraints and state ordering;
- single-tree versus tree-set conclusions;
- optimizer starts, boundary estimates, and reference implementations.
Publish A Comparative Result Packet¶
A reviewable result keeps five layers together:
- Population: included taxa, exclusions, duplicate policy, and exact tree–trait reconciliation.
- Design: formula, design columns, transformations, factor coding, and missing-value policy.
- Evolutionary model: covariance or transition family, tree scale, fitted parameters, and constraints.
- Fit and uncertainty: objective, estimates, intervals or probabilities, optimizer state, diagnostics, and warnings.
- Sensitivity: alternative trees, codings, models, starts, and inclusion rules that could change the conclusion.
For ancestral reconstruction, add stable node identities and distinguish within-tree uncertainty from variation across trees. For regression, retain the coefficient-to-design-column mapping so a table remains interpretable without reconstructing the formula by hand.
The result packet supports review of the computation. A separate Evidence Book bundle is required before claiming correspondence with a named study source.
The PCM1 signal and ancestral results and PCM2 model comparisons show how these conditions become bounded evidence claims.