Use when designing or defending the field-experiment or modelling design of a Field Crops Research (FCR) manuscript — multi-environment trials, randomization and replication, blocking and split-plot layouts, genotype-by-environment (G×E) structure, and crop-model calibration/validation. FCR expects field experiments to span at least two seasons and/or multiple environments. Strengthens the design; it does not write code.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-experimental-design --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fcr Experimental Design?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-fcr-experimental-design)More formats (shields.io, HTML) on the badges page.
---
name: fcr-experimental-design
description: Use when designing or defending the field-experiment or modelling design of a Field Crops Research (FCR) manuscript — multi-environment trials, randomization and replication, blocking and split-plot layouts, genotype-by-environment (G×E) structure, and crop-model calibration/validation. FCR expects field experiments to span at least two seasons and/or multiple environments. Strengthens the design; it does not write code.
---
# Experimental Design (fcr-experimental-design)
FCR is demanding about **field-experimental rigour**. The design must credibly connect the agronomic
question to evidence that generalises across environments. The single most important FCR-specific rule:
field experiments should, unless exceptional circumstances apply, span **at least two seasons and/or
multiple locations/environments**. Design for that from the start.
## When to trigger
- Planning a multi-environment trial (MET) or a season×site×treatment layout
- A reviewer questioned randomization, replication, blocking, or G×E inference
- Deciding how to characterise environments (soil, weather, phenology)
- Designing a crop-modelling study (calibration/validation, scenario design)
## Field-experiment design essentials
- **Multi-environment by design.** Plan ≥ 2 seasons and/or multiple sites; define what an
"environment" is (site×year, managed water/N regime). State why the set spans the target population
of environments.
- **Randomization & replication.** Use a proper randomized design (RCBD, **resolvable
incomplete-block / alpha-lattice**, split-plot for factor hierarchies, strip-plot, augmented for many
genotypes). State replication per environment and the randomization procedure — not "plots were
arranged."
- **Blocking & spatial control.** Block against known field gradients; plan for **spatial analysis**
(e.g., row/column or P-spline) where fields are large or heterogeneous.
- **Plot management detail.** Plot size, borders/guard rows, sowing density, dates, and the management
applied — enough to reproduce the experiment.
- **Environment characterisation.** Record **soil and weather** and present weather **in relation to
crop phenology**; this is what lets readers interpret G×E.
## Genotype/treatment × environment (G×E)
- Decide up front how G×E will be modelled: factorial structure, which effects are **fixed vs.
random**, and how environments enter (random sample vs. fixed targets).
- Plan stability/adaptation analyses (Finlay–Wilkinson regression, **AMMI**, **GGE biplot**) where
ranking across environments is the question.
## Crop-modelling design
- State the model and **version**, the **cultivar coefficients**, and the **calibration vs.
validation** split (independent data, not the same trials).
- Justify the scenario/factor design and the environments simulated; report what the model **adds**
beyond the field data (extrapolation, yield-gap decomposition, generalisation).
## The generalisation test (FCR-specific)
For your design, write one sentence: *"These environments represent ___, so the result is expected to
hold for ___ (and not for ___)."* If you cannot, the design does not yet support a general,
FCR-worthy claim — add environments or scope the claim.
## Anti-patterns
- One site, one season presented as sufficient (fails the multi-environment expectation)
- "Randomized" asserted with no design named, no replication count, no layout
- Treating a controlled-environment study as the main evidence (out of scope — see `fcr-topic-selection`)
- Ignoring spatial heterogeneity in large fields; pseudoreplication (sub-samples treated as reps)
- Calibrating and validating a model on the same data
## Output format
```
【Design】RCBD / alpha-lattice / split-plot / MET / modelling
【Environments】#seasons × #sites; what they represent
【Randomization & replication】procedure + reps per environment
【G×E plan】fixed/random structure; stability analysis if relevant
【Environment characterisation】soil + weather vs. phenology recorded? [Y/N]
【Generalisation sentence】represents ___ → holds for ___
【Next】fcr-data-analysis
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — design packages (agricolae, FielDHub) and crop models (APSIM, DSSAT, STICS)
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — the ≥2-seasons/-environments rule and reproducibility expectations
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!