DALiuGE graph patches¶

Graph patches are the final deterministic graph-shaping step before translation and deployment. The v2 YAML key is graph_patches; every match, expression result, changed field, and artifact checksum remains inspectable.

Preparation flow¶

INPUTlogical graphURL or path

CONTEXTmanifestpinned artifact

VALIDATEpatch reducermatch + evaluate + set

ARTIFACTpatched graphdiff + sha256

EXTERNALtranslatorthen deployment

Typed shape¶

Set the scatter count from manifest data:

graph_patches:
  - match:
      kind: node_name
      equals: Scatter/GenericScatterApp/Beam
    set:
      num_of_copies: "$count(sbids[].datasets[])"

match.kind is the closed enum node_name. match.equals identifies the full DALiuGE node name. Each set value is either a literal or one of the supported manifest expressions.

Expressions¶

Expression	Result	Typical use
`$count(path)`	Number of selected manifest elements	Scatter copies
`$sum(path)`	Numeric sum across selected values	Aggregate resource or workload field

Expressions run against the immutable manifest context. Put archive normalization in typed transforms and reserve WASM for survey logic that cannot be expressed safely in the built-in model.

Patch diagnostics¶

Graph preparation reports:

the patch index and target node;
whether zero, one, or multiple nodes matched;
each field before and after mutation;
expression input path and evaluated value;
graph checksum before and after mutation;
validation errors with a structured path and hint.

Precise matches are deliberate. A missing node is an error rather than a silent no-op; an ambiguous match is rejected rather than applied to multiple nodes.

Manifest injection¶

Existing graphs can use the beampipe-ingest palette. During preparation, Beampipe locates the named node, validates its manifest_path field, creates readonly graph configuration, and embeds the generated manifest JSON before translation.

Contract element	Meaning
`beampipe-ingest` node	Marker that the graph accepts a Beampipe manifest
`manifest_path`	Graph field or path where manifest JSON is exposed
Generated manifest	Project-shaped source, SBID, and dataset grouping

Use injection when graph applications consume the manifest directly. Use ordinary patches for structural settings such as scatter counts.

Operator preview¶

beampipe graph prepare \
  --project wallaby_hires \
  --source WALLABY_J123456-123456
beampipe graph diff --execution "$EXECUTION_ID"

Before live submission, confirm the target count, expression values, node/field diff, manifest injection path, and output checksums. Then use deployment profiles to select the translator and deployment boundary.