How do distance methods and likelihood methods differ?
- Distance minimizes total steps while likelihood counts differences
- Distance compresses sequences into pairwise gaps, while likelihood picks the most probable tree
- Distance reads support values while likelihood draws branch lengths
Why does counting raw differences underestimate true change?
- Some sites were hit twice and some changes reversed, hiding change
- Models always add extra change that never happened
- Resampling removes differences before anyone counts them
What does a support value actually report?
- The age of the branch in millions of years
- How often resampling recovers that split
- The chance the branch is true
Why do good methods downweight rapidly evolving sites?
- Fast sites are likely saturated, so their similarity often misleads
- Fast sites never change, so they carry no information
- Slow sites are too rare to matter for the tree
A published tree shows 42 percent on the branch your claim needs. What should you do?
- Rest the claim on it, since published trees are always safe
- Redraw the tree by hand until the value looks higher
- Treat the split as undecided and narrow the claim to strong nodes
A node has poor support. Which fix targets the cause most directly?
- Adding informative characters and species to break up long branches
- Deleting the weak branch from the figure before publishing
- Counting raw differences instead of using any model
A branch with 95 percent support is 95 percent likely to be true.
Circle one: True False
Raw similarity groups two fast evolving species together, but a model based tree separates them. Why trust the model tree here?
- Models always agree with raw similarity, so this cannot happen
- Parsimony used more steps, which is always more accurate
- Convergent and reversed changes create false similarity that only model correction discounts