ap_verify command-line reference¶

This page describes the command-line arguments and environment variables used by ap_verify.py.

Signature and syntax¶

The basic call signature of ap_verify.py is:

ap_verify.py --dataset DATASET --output WORKSPACE --id DATAID

These three arguments are mandatory, all others are optional.

Status code¶

ap_verify.py returns a status code of 0 if the pipeline ran to completion. If the pipeline fails, the status code will be an interpreter-dependent nonzero value.

Named arguments¶

Required arguments are --dataset, --id, and --output.

--id <dataId>¶

Butler data ID.

The input data ID is required for all ap_verify runs except when using --help.

Specify data ID to process using data ID syntax. For example, --id "visit=12345 ccd=1 filter=g".

Currently this argument is heavily restricted compared to its command line task counterpart. In particular, the dataId must specify exactly one visit and exactly one CCD, and may not be left blank to mean “all data”.

--dataset <dataset_name>¶

Input dataset designation.

The input dataset is required for all ap_verify runs except when using --help.

The argument is a unique name for the dataset, which can be associated with a repository in the configuration file. See Datasets as input arguments for more information on dataset names.

Allowed names can be queried using the --help argument.

-h, --help¶

Print help.

The help is equivalent to this documentation page, describing command-line arguments.

-j <processes>, --processes <processes>¶

Number of processes to use.

When processes is larger than 1 the pipeline may use the Python multiprocessing module to parallelize processing of multiple datasets across multiple processors.

Note

This option is provided for forward-compatibility, but is not yet supported by ap_verify.

--metrics-file <filename>¶

Output metrics file.

The name of a file to contain the metrics measured by ap_verify, in a format readable by the lsst.verify framework. If omitted, the output will go to a file named ap_verify.verify.json in the user’s working directory.

This argument can be used to run multiple instances of ap_verify concurrently, with each instance producing output to a different metrics file.

--output <workspace_dir>¶

Output and intermediate product path.

The output argument is required for all ap_verify runs except when using --help.

The workspace will be created if it does not exist, and will contain both input and output repositories required for processing the data. The path may be absolute or relative to the current working directory.

--silent¶

Do not report measurements to SQuaSH.

Disables upload of measurements, so that ap_verify can be run for testing purposes by developers.

Note

Ingestion of lsst.verify metrics is not yet supported by SQuaSH, so this flag should always be provided for now.

Environment variables¶

The SQUASH_USER, SQUASH_PASSWORD, and SQUASH_URL environment variables are used by the verify framework to configure SQuaSH upload. SQUASH_USER and SQUASH_PASSWORD must be defined in any environment where ap_verify.py is run unless the --silent flag is used.

SQUASH_USER¶: User name to use for SQuaSH submissions.

SQUASH_PASSWORD¶: Unencrypted password for SQUASH_USER.

SQUASH_URL¶: The location for a SQuaSH REST API. Defaults to the SQuaSH server at lsst.codes.

Navigation