Configuring metrics for ap_verify¶
ap_verify handles metrics through the
Each metric has an associated
MetricTask, typically in the package associated with the metric.
For example, the code for computing
ip_diffim.numSciSources can be found in the
ip_diffim package, not in
The metrics computed by
ap_verify are configured as part of the pipeline.
The pipeline can be overridden using the
--pipeline command-line option.
ap_verify package provides a default-instrumented pipeline in
To make it easy to mix and match metrics, all
MetricTask configuration is done in separate sub-pipelines that are then included in