← Fig WGS Lineage

Fig WGS lineage project · experiments at home

Experiments at home

Two ways to turn “these taste different” or “this one grows differently” into evidence: a blind triangle tasting scored with an exact p-value, and a simple, consistent record of how each plant grows and fruits.

A field guide for growers · no lab needed · the next steps page explains why these are the right questions

The short version

1 · The blind triangle test

Is there a difference anyone can taste?

A triangle test answers exactly one question: can tasters tell the two figs apart? It does not say which is better, why they differ, or whether the difference comes from the variety rather than the garden, the tree or the day. It is the standard sensory discrimination test used in food science (ISO 4120, ASTM E1885), and it works at a kitchen table.

Each taster receives three samples in coded cups. Two come from one fig, one from the other. The taster must pick the one that is different — even when unsure. If there were no perceptible difference, a taster would pick correctly one time in three by chance. So the question becomes: did more tasters pick correctly than chance explains? The probability that guessing alone would do at least that well is the p-value.

Plan before you taste

  1. Write the question down first — for example, “Can tasters tell Smith from Cessac at full ripeness?” — together with the number of tasters, the significance level (5% is conventional) and your definition of ripe. Deciding afterwards is how a coincidence turns into a finding.
  2. Source the fruit fairly. Ideally both varieties grow in the same garden under the same care. Fruit from two different gardens compares two gardens as much as two varieties; if that is what you have, say so when you report the result.
  3. Find the tasters: 12 at the very least, 24–30 to catch a modest difference (see “How many tasters?”). Tasters should not know which varieties are in the test, and the person who prepares the cups should not be the person who serves them.

Prepare the figs

Session planner

Run the tasting

Score it

Count the correct answers, k, out of n tasters. The p-value is the probability that guessing alone would give at least k correct — an exact binomial calculation with a one-in-three chance per taster:

p = Σi=kn C(n, i) (1/3)i (2/3)ni

p-value calculator

Or read the threshold from the table: the fewest correct answers that reach each significance level for a panel of that size.

Tastersp < 0.05p < 0.01p < 0.001
128910
18101213
24131516
30151719
36182022
Full table, 6–60 tasters
Tastersp < 0.05p < 0.01p < 0.001
656
7567
8678
9678
10789
117810
128910
138911
1491011
1591012
1691112
17101113
18101213
19111214
20111314
21121315
22121415
23121416
24131516
25131517
26141517
27141618
28151618
29151719
30151719
31161820
32161820
33171821
34171921
35171922
36182022
37182022
38192123
39192123
40192124
42202225
45212426
48222527
50232628
54252730
60273033

A dash means no score reaches that level with so few tasters. Values are exact binomial tails with a chance rate of one in three, computed when this page is built.

How many tasters?

Not everyone perceives a small difference. Suppose some share of your tasters genuinely can tell the figs apart and the rest guess: the table gives the chance that a panel of each size comes out significant at p < 0.05.

Tasters20% can tell30% can tell50% can tell
1214%26%63%
1830%52%89%
2430%55%93%
3043%71%98%
3641%72%99%
4860%88%>99%
6065%92%>99%

So a dozen friends will usually catch an obvious difference and usually miss a subtle one: if only 30% of tasters can perceive it, 12 tasters detect it 26% of the time and 30 tasters 71%.

If nothing is significant

A non-significant result means the test did not detect a difference — not that there is none. Claiming that two figs taste the same is a different, harder test, and it has to be planned as one: choose the largest share of discriminating tasters you would still call “no meaningful difference” (30% is a common choice), and use enough tasters that a low score becomes strong evidence. With a 5% risk of wrongly concluding “the same”, the most correct answers that still support the claim are:

TastersMost correct that still supports “the same”Chance average
1234
2488
301110
361312
481916
602520
723024
964232

With 12 tasters the claim needs 3 or fewer correct — fewer than guessing would give — so a small panel can almost never show that two figs taste alike. Showing “different” takes a dozen people; showing “the same” takes several dozen.

Common ways a tasting goes wrong

  1. The person who prepared the cups serves them, and gives the answer away without meaning to.
  2. One variety was picked a day earlier, is riper, or is warmer.
  3. Tasters confer, watch each other, or can see the fruit.
  4. “No difference” answers are accepted instead of a forced choice.
  5. Several tastings are run and only the one that “worked” is reported. Decide the comparison in advance and report every session.
  6. One tree’s fruit is treated as the whole variety.

2 · Plant data

Is there a difference in how they grow and fruit?

Growth and fruiting claims — “more vigorous”, “ripens a week earlier”, “bigger fruit”, “sweeter” — can be tested with a tape measure, a kitchen scale, a refractometer and a calendar. The rules that make the numbers mean something matter more than the tools.

Ground rules

  1. Grow them side by side. Same site, same pot size and mix (or the same bed), same watering, feeding and pruning. Alternate the positions (A, B, A, B) so that neither variety gets the sunny end.
  2. More than one plant of each. One plant is one plant, with its own history, root system and virus status. Three or more plants per variety — ideally from independent sources of verifiable provenance — is what lets you talk about the variety.
  3. Write the definitions down before the season starts, and keep them. A “first fig” or “ripe” date is only comparable if it means the same thing every time.
  4. Keep your own chain of custody. Record where every plant came from (seller, date, a photo of the label) and tag the plants so they cannot be swapped.
  5. Blind what you can. Where possible, have someone who does not know which plant is which weigh the fruit and read the refractometer.

What to measure

Bud break (“wake-up”)Spring, every 2–3 daysdate

The first date a leaf has fully unfolded anywhere on the plant.

First fig (fruit set)Every 2–3 days after bud breakdate

The first date a new main-crop fig is visible in a leaf axil at pea size (about 5 mm). Record breba figs separately: they form on last year’s wood.

Days from wake-up to fruit setComputeddays

First-fig date minus bud-break date.

Linear growth rateWeeklycm/week

Tag three comparable shoots per plant (for example the three strongest upright shoots). Measure each with a flexible tape from where this season’s growth starts — the end of last year’s wood — to the tip. Rate = change in length ÷ days between measurements × 7.

Node spacing (internode length)Once shoot growth stopscm

On the same shoots, measure from the 5th to the 15th node of this season’s growth and divide by 10. That skips the crowded base and the unfinished tip; on a shorter shoot, use the longest run you can and note which nodes.

Fruit massEvery harvestg

Weigh each ripe fig on the day it is picked, stem trimmed flush, on a scale that reads to 0.1 g. Note split or damaged fruit.

Fruit BrixEvery harvest°Bx

Zero a temperature-compensated refractometer with distilled water at the start of each session. Squeeze a few drops of juice from the pulp (not the skin), for example through a garlic press, onto the prism; wipe it clean between fruits. Take two readings per fig and average them. Pick in the morning, and note recent rain or watering, which dilutes sugar.

Days to ripenPer figdays

Tag each fig with a dated tie when it reaches pea size. Days to ripen = harvest date minus tag date, using your written definition of ripe.

Also record the context: location and climate zone; in the ground or in a container (and the pot volume); own-root or grafted; plant age; weekly high and low temperatures, or a nearby weather station; rain and irrigation; feeding; pruning dates; pests, disease, fruit drop and splitting.

Every “days to” figure is mostly a thermometer. Compare varieties within one garden and one season. To compare across gardens or years, convert days to growing degree days: for each day, add the day’s average temperature above a base — max(0, (high + low) / 2 − 10 °C), or − 50 °F in Fahrenheit — and sum from the start date. A base of 10 °C (50 °F) is a common choice.

Keep the data in one sheet

One row per measurement, so nothing needs re-typing later. The template has these columns and a few example rows:

date, plant_id, variety, source, measurement, item_id, value, unit, notes

Download the template (CSV)

Compare plants, not fruit

Summarize each plant first — its mean Brix, mean fruit mass, median days to ripen, bud-break date — and then compare the plant summaries between varieties. Twenty figs from one tree are not twenty replicates of a variety; they are twenty measurements of one tree. With three or more plants per variety, a two-sample comparison of the plant means (a Welch t-test, or a Mann–Whitney test for small or lopsided data) is the right tool. With fewer, report the numbers and do not claim a difference.

Whichever experiment you run, keep the raw sheets. They are what lets anyone else check the result.

Read next

Next stepsWhy a shared genome does not settle the phenotype question, and the common-garden test that would. Cessac = SmithThe sequencing evidence that the two names share one genome.