Table 4.
No. | Scenario | MIAPPE modelling |
---|---|---|
(1) | Heterozygous parent genotypes are used to derive a crossing population exhibiting significant phenotypic segregation. Genotype tracing is necessary. | The cross of the parents is mentioned in the material source. Each of the progeny is treated as a biological material derived from the same material source, and is attributed a unique ID. |
(2) | Each tree in a field is observed through several sensors, at the roots and near its top. | Observation unit levels: “plant”. Each tree is a single observation unit. Each sensor measures one or many observed variables, (e.g. “Canopy temperature”, “Cork thickness”, …) |
(3) | A sensor is placed in the middle of the field. | An observation unit is created for the sensor. No plants have to be present for an observation unit to be valid, as long as that observation unit is used to produce measurements or express experimental factor values. |
(4) | Multilocal, multiyear field phenotyping network |
Observation unit levels: “study”> “genotype”> “plot”. The whole network is an investigation. Each location is a study over several years. The biological material list is shared for the whole investigation. The list of observed variable definitions is also shared by all studies. The measured data and observations can be at the “plant” or “plot” level, or as a per‐genotype average within each study. Study‐level observations can be measurements from a meteorological station. |
(5) | Time series of event or observation. |
Observation unit levels: any. Study type: any. Observed variables list the time scale they use. In the data file, a single observed variable is measured several times, each value being timestamped in julian days, growing degree days or any other time scale. The same applies with events with a given event type recorded several times at different time stamps. |
The table shows more specific scenarios that may be necessary to accommodate in MIAPPE, and the proposed modelling for them inside the standard.