Configuring metrics for ap_verify¶
ap_verify handles metrics through the MetricTask framework.
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 ap_verify.
The metrics computed by ap_verify are configured as part of the pipeline.
The pipeline can be overridden using the --pipeline command-line option.
The ap_verify package provides a default-instrumented pipeline in pipelines/ApVerify.yaml.
To make it easy to mix and match metrics, all MetricTask configuration is done in separate sub-pipelines that are then included in ApVerify.yaml.