% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/retrieve_specific_barrier.R
\name{retrieve_specific_barrier}
\alias{retrieve_specific_barrier}
\title{Apply barriers' specific log-reduction to a config}
\usage{
retrieve_specific_barrier(
  config,
  barrierID,
  cropHeight,
  matrixID,
  popID,
  decay
)
}
\arguments{
\item{config}{A per-row config (list) from the scenario.}

\item{barrierID}{One or more supplementary barrier ids (a scalar or a vector);
each is applied in turn. \code{NA} matches no branch and is skipped.}

\item{cropHeight}{The crop height.}

\item{matrixID}{The exposure-matrix id.}

\item{popID}{The exposed-population id.}

\item{decay}{The number of decay days (for natural die-off barriers).}
}
\value{
The updated config.
}
\description{
For one or more supplementary barriers, updates the per-config log-reduction
according to each barrier's type: pathway-specific barriers use
\code{\link[=update_logreduction_path]{update_logreduction_path()}}, natural die-off uses
\code{\link[=update_logreduction_decay]{update_logreduction_decay()}}, and product/soil-specific barriers use
\code{\link[=update_logreduction_specific_barrier]{update_logreduction_specific_barrier()}}. Barriers are applied in turn so
their reductions accumulate; any other barrier leaves the config unchanged.
Extracted from \code{run_qmra_initial_situation()} /
\code{run_qmra_supplementary_process()} (was an inline anonymous function).
}
