Centralized metric and specification definitions for the LSST Science Pipeline Verification Framework.
Metrics are measureable things. They can be astronomy concepts (an astrometric RMS), or computational (a task's timing or memory usage).
Metrics that are measured by packages are registered here in
verify_metrics by adding or extending a metric definition YAML file in the
See metrics/README.rst for more information.
Specifications are tests of metric measurements. A specification might say that a metric measurement should be less than a certain value if that measurement was made under a certain set of conditions (provenance). Whenever metrics are measured, DM's SQUASH harness tests those measurements against specifications. Depending on the pass/fail outcome, subscribers can receive notifications (alerts).
New specifications are registered here in
verify_metrics by adding or extending a specification definition YAML file in the
See specs/README.rst for more information.
Getting help and reporting bugs
If you're not part of the LSST Project, please post your question or issue in our support forum. It's easy to create a Community forum account.
We don't use GitHub Issues.
- This repository should only contain metric and specification YAML files.
Don't add Python code; instead consider extending the
lsst.verifyAPI in the verify package.
- Follow LSST Data Management's workflow for contributions.
This product's source code is licensed under the terms of GPLv3 (see LICENSE), and all documentation content is licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license.