make_injection_pipeline

Make an expanded source injection pipeline.

This script takes a reference pipeline definition file in YAML format and prefixes all post-injection dataset type names with the injected prefix. If an optional injection pipeline definition YAML file is also provided, the injection task will be merged into the pipeline. Unless explicitly excluded, all subsets from the reference pipeline containing the task which generates the injection dataset type will also be updated to include the injection task. A series of new injection subsets will also be constructed. These new subsets are copies of existent subsets, but with tasks not directly impacted by source injection removed. Injected subsets will be the original existent subset name with the ‘injected_’ prefix prepended.

usage: make_injection_pipeline -t TEXT -r FILE [-i FILE] [-e] [-x task]
                               [-f FILE] [--overwrite] [--prefix PREFIX]
                               [--instrument instrument] [-c CONFIG]
                               [-a FILE [FILE ...]] [-s FILE] [-d FILE] [-h]

More information is available at https://pipelines.lsst.io.

options

-t <text>, --dataset-type-name <text>

Name of the datset type being injected into.

-r <file>, --reference-pipeline <file>

Location of a reference pipeline definition YAML file.

-i <file>, --injection-pipeline <file>

Location of an injection pipeline definition YAML file stub. If this is not explicitly provided, an attempt to infer the injection pipeline stub will be made using the injected dataset type name.

-e, --exclude-subsets

Do not update pipeline subsets to include the injection task.

-x <task>, --excluded-tasks <task>

Comma-separated set of task labels to exclude from the pipeline.

-f <file>, --filename <file>

Path to save a modified pipeline definition YAML file.

--overwrite

Overwrite the output saved pipeline definition file if it already exists.

--prefix <prefix>

Prefix to prepend to each affected post-injection dataset type name.

--instrument <instrument>

Add instrument overrides. Must be a fully qualified class name.

-c <config>, --config <config>

Config override for a task, in the format ‘label:key=value’.

-a <file>, --additional-pipelines <file>

Location(s) of additional input pipeline definition YAML file(s).Tasks from these additional pipelines will be added to the output injection pipeline.

-s <file>, --subset-name <file>

All tasks from any additional pipelines will be added to this subset.The subset will be created if it does not already exist.

-d <file>, --subset-description <file>

The description given to a new subset which holds tasks from additional pipelines provided.Note: this argument is ignored if the subset already exists.

-h, --help

Show this help message and exit.