rsmlToTable {archiDART}R Documentation

Import RSML Files Into a Single Data Frame

Description

Import RSML files located in a folder into a single data frame. More information about RSML files can be found in Lobet et al (2015) and Delory et al (2018).

Usage

rsmlToTable(inputrsml, unitlength="px", rsml.date=NULL, rsml.connect=TRUE,
            vertical3d="y", unitangle="d", fitter=FALSE, show.progress=FALSE)

Arguments

inputrsml

A character string specifying the path to the folder containing the RSML files. Mandatory.

unitlength

A character string specifying the unit of length that must be used in the final data frame. The value acceptable for this argument could be either “px” for pixels, “cm” for centimetres or “mm” for millimetres. The function will use the metadata inside each RSML file (unit and resolution) to make the conversion.

rsml.date

A numeric value specifying the root system age (the unit of time is defined by the user). If rsml.date=NULL (default), a default value of 1 is used by the function. If the root system age is stored as a continuous function along the root segments, a vector of character strings specifying the names/labels of the function can be used (see details).

rsml.connect

A logical value. Mandatory. If TRUE (default), the lateral roots are connected to their parent root (see details). If FALSE, no connection is made between daughter and mother roots.

vertical3d

The vertical axis for 3D RSA data (x, y, or z).

unitangle

A character string specifying the unit that must be used to express the calculated angles. The value acceptable for this argument could be either “d” for degrees (default value) or “r” for radians.

fitter

A logical value. Should the Fitter topological indices be computed? Yes is TRUE, No is FALSE. See details.

show.progress

A logical value. Should a progress bar be shown in the R console? Yes is TRUE, No is FALSE.

Details

To run rsmlToTable efficiently, RSML (.rsml) files must have been saved with their appropriate extension.

The argument rsml.date is used to create a tps file for each root system located in inputrsml. If the root system age is stored as a continuous function along the root segments, the rsml.date argument can be a vector of character strings specifying the names/labels of the function. For instance, the root system age at the first apparition of each node is stored as a continuous function called “age” in RSML files containing RSA data simulated with the ArchiSimple model (Pages et al (2013)). The “age” function attaches the root system age along the root segments, so that each node is associated with one age value. An RSML library containing 3D RSA data simulated with ArchiSimple is available here: doi: 10.5281/zenodo.208214.

The rsml.connect argument can be used to connect the lateral roots to their corresponding mother root. If rsml.connect=TRUE, each point starting a lateral root is connected to the nearest point located on its mother root. DBase is approximated by the distance between the parent root base and the point located on the mother root that is closest to the point starting a lateral root. Using RSML files, only RSA data associated with roots possessing a branching order lower or equal to 7 are used for the computation of RSA traits.

show.progress=TRUE can only be used if more than one RSML file is stored in inputrsml.

If fitter=TRUE, topological indices described in Fitter (1986, 1987) will be calculated. Here, we define each topological index as in Fitter (1986, 1987). We recommend the reading of these papers for more information.

The magnitude of a link is equal to the number of external links that feed into that link.

The path length of a link is equal to the number of links between a given link and the root system base.

Value

Returns a rsmlToTable object. Each line of the data frame gives the attributes of one segment. The data frame includes the following columns:

file: the name of each RSML file located in inputrsml.

plant: the plant identification number.

root: the root identification number.

order: the root branching order.

parentroot: the identification number of the parent root.

time: the date of apparition.

bran: the branching state (‘true’ denotes a branching link while ‘false’ denotes a continuing link).

apic: the apical state (‘true’ denotes a segment ending a root).

x1: the X coordinate of the node starting the segment (expressed in unitlength).

y1: the Y coordinate of the node starting the segment (expressed in unitlength).

z1: the Z coordinate of the node starting the segment (expressed in unitlength).

x2: the X coordinate of the node ending the segment (expressed in unitlength).

y2: the Y coordinate of the node ending the segment (expressed in unitlength).

z2: the Z coordinate of the node ending the segment (expressed in unitlength).

diameter1: the root diameter at the node starting the segment (expressed in unitlength).

diameter2: the root diameter at the node ending the segment (expressed in unitlength).

length: the length of the segment (expressed in unitlength).

blength: the cumulative length measured along each root (expressed in unitlength).

surface: the surface area of the root segment (expressed in unitlength^2).

volume: the volume of the root segment (expressed in unitlength^3).

orientation: the angle between each segment and a vertical direction vector (expressed in unitangle).

growth: the growth rate value of each segment (expressed in unitlength).

geodesic: the geodesic distance measured along the roots (expressed in unitlength).

magnitude: the magnitude of the segment. See details for more information. Computed only if fitter=TRUE.

pathlength: the path length of the segment. See details for more information. Computed only if fitter=TRUE.

Author(s)

Benjamin M. Delory, Guillaume Lobet

References

Delory B.M., Baudson C., Brostaux Y., Lobet G., du Jardin P., Pages L., Delaplace P. (2016) archiDART: an R package for the automated computation of plant root architectural traits, Plant and Soil, DOI: 10.1007/s11104-015-2673-4.

Delory B.M., Li M., Topp C.N., Lobet G. (2018). archiDART v3.0: a new data analysis pipeline allowing the topological analysis of plant root systems, F1000Research, 7:22, DOI: doi: 10.12688/f1000research.13541.1

Fitter A.H. (1986) The topology and geometry of plant root systems: influence of watering rate on root system topology in Trifolium pratense, Annals of Botany, 58, 91-101.

Fitter A.H. (1987) An architectural approach to the comparative ecology of plant root systems, New Phytologist, 106, 61-77.

Lobet G., Pound M.P., Diener J., Pradal C., Draye X., Godin C., Javaux M., Leitner D., Meunier F., Nacry P., Pridmore T.P., Schnepf A. (2015) Root System Markup Language: Toward a Unified Root Architecture Description Language, Plant Physiology, DOI: 10.1104/pp.114.253625.

Pages L., Becel C., Boukcim H., Moreau D., Nguyen C., Voisin, A-S. (2013) Calibration and evaluation of ArchiSimple, a simple model of root system architecture, Ecological Modelling, DOI: 10.1016/j.ecolmodel.2013.11.014.

Examples

## Locate folder with RSML file
path <- system.file("extdata", package="archiDART")

table<-rsmlToTable(inputrsml=path, unitlength="cm", rsml.date="age")

[Package archiDART version 3.4 Index]