Skip to contents

The writers need three things about each run: what to call it, how to record it in the database, and what to put in the run manifest that the sensitivity analysis post-processing reads back. All three follow from the design labels, so they are built here rather than as a side effect of writing configs.

Usage

sa_run_descriptions(design_matrix, site_id, pft_names)

Arguments

design_matrix

The design from generate_OAT_SA_design.

site_id

Site id, used as the last part of each run id.

pft_names

Names of the PFTs in the run, used to describe the median run, which moves nothing.

Value

A data.frame with one row per design row: id, paramlist, and the pft_name, trait, quantile and type the manifest carries. This is what write.ensemble.configs takes as run_descriptions.