Darwin’s Finch Beak Evolution Tree

ISEF Category: Animal Sciences

Subcategory: Systematics and Evolution  ·  Difficulty: Advanced  ·  Setup: Home Setup  ·  Time: 1 to 2 Months

The Hook

Darwin's finches look small, but they hold one of the clearest stories of species splitting apart. Their beaks act like different tools, each shaped for a different job. You can use public data to trace when those changes appeared on the tree. That turns a classic evolution example into a real research project.

What Is It?

A divergence-time tree is a family tree with a clock attached. It shows not just who is related, but when lineages split from one another. For Darwin's finches, you pair beak measurements with DNA data to see whether changes in shape lined up with the rise of new species.

Think of it like mapping cousins in a family, then adding birthdays to each branch. The morphology data tell you how the beaks differ in size and shape. The genomic data help you estimate ancestry, while the time tree helps you test whether beak diversification happened early, late, or in pulses across the finch radiation.

Why This Is a Good Topic

This topic works well for a science fair because you can ask a clear question, use public data, and produce a real analysis instead of a toy demo. It connects evolution, ecology, and data science, so you can learn how traits, genes, and time fit together. You can also compare methods, which gives you room to make the project stronger than a basic class report.

Research Questions

• How does adding more finch species change the estimated split times in the tree?
• What is the effect of using beak depth, beak width, or beak length on the inferred branching pattern?
• Does a tree built from nuclear DNA match a tree built from mitochondrial DNA?
• To what extent do different calibration choices change the age of the main divergence events?
• Which beak traits change fastest after a lineage split?
• How does island of origin relate to the timing of beak-shape diversification?

Basic Materials

• Laptop with internet access.
• Spreadsheet software such as Google Sheets or Excel.
• Public morphometric data table from a published finch study.
• Public DNA sequence records from GenBank or another open database.
• Reference article or supplement with species names, specimen IDs, and trait definitions.
• Project notebook for tracking data cleaning decisions.

Advanced Materials

• Laptop or workstation with enough memory for phylogenetic analysis.
• R and RStudio with phylogeny packages such as ape and phytools.
• Python with pandas, scipy, and matplotlib for data cleaning and plots.
• BEAST 2 or another tree dating program for divergence-time estimation.
• Geometric morphometrics software or ImageJ for landmark-based beak measurements.
• Access to published calibration literature or museum specimen metadata for cross-checking taxa.

Software & Tools

• R and RStudio: Fits phylogenetic models, compares trees, and plots trait evolution.
• Python: Cleans datasets, merges morphology with sequence metadata, and runs custom statistics.
• BEAST 2: Estimates divergence times from sequence alignments and calibration choices.
• FigTree: Visualizes tree branch lengths, node ages, and support values.
• ImageJ: Measures beak landmarks and distances from specimen images.

Experiment Steps

1. Define the finch species set and decide which beak traits and gene regions you will compare.
2. Match every morphology record to the correct species name, specimen source, and sequence record.
3. Choose a dating strategy and justify the calibration points you will use.
4. Build a baseline tree, then test whether different trait subsets change the branching order or node ages.
5. Plan validation checks for missing data, support values, and sensitivity analyses before you trust any result.

Common Pitfalls

• Mixing datasets that use different beak landmarks, which makes trait comparisons meaningless.
• Using species names that changed across papers without resolving synonyms, which creates duplicate or missing taxa.
• Building a time tree from too few calibration points, which makes divergence dates unstable.
• Treating branch length as evidence for beak adaptation, which confuses ancestry with trait change.
• Ignoring missing specimens or uneven sampling across islands, which can make one lineage look more distinct than it really is.

What Makes This Competitive

A strong version of this project goes beyond drawing a tree. You compare multiple data types, test more than one calibration scheme, and check whether your result stays stable when you drop weak taxa or traits. You also ask a sharper question, like whether beak divergence lines up with island history or with shifts in evolutionary rate. That kind of careful analysis makes the project feel like real systematics work, not just a class exercise.

Project Variations

• Compare only ground-finches versus tree-finches to see whether beak evolution followed the same tempo in each clade.
• Replace simple beak measurements with landmark-based shape analysis from specimen photos to test whether shape, not size alone, drives the tree.
• Use mitochondrial data versus nuclear loci to see how the inferred divergence times shift across marker sets.

Learn More

• NCBI GenBank: Search open finch sequence records and download DNA data for phylogenetic analysis.
• PubMed: Search review articles on Darwin's finches, adaptive radiation, and molecular clocks.
• NCBI Bookshelf: Read free chapters on phylogenetics, evolutionary trees, and divergence-time methods.
• Dryad: Look for published morphometric datasets from finch evolution papers and linked supplements.
• Proceedings of the Royal Society B: Search for peer-reviewed papers on finch diversification, beak evolution, and dating methods.