Method Execute

Namespace

Pinwheel.Vista.Graph

Assembly

Pinwheel.Vista.Runtime.dll

Execute(string[], TerrainGenerationConfigs, GraphInputContainer, FillArgumentsHandler, GraphExecutionCache, CancellationSignal)

Starts a progressive graph execution and returns a handle that can be yielded and inspected.

public ExecutionHandle Execute(string[] nodeIds, TerrainGenerationConfigs configs, GraphInputContainer inputContainer = null, TerrainDataGraph.FillArgumentsHandler fillArgumentsCallback = null, GraphExecutionCache cache = null, CancellationSignal cancellationSignal = null)

Parameters

nodeIds string[]

The output node ids to resolve. The graph automatically expands these into the full dependency chain required for execution.

configs TerrainGenerationConfigs

Request-wide execution settings such as resolution, bounds, height scale, and seed.

inputContainer GraphInputContainer

Optional external inputs to bind into the execution context before node evaluation starts.

fillArgumentsCallback TerrainDataGraph.FillArgumentsHandler

Optional callback that appends extra values to the argument table after the standard graph arguments have been written.

cache GraphExecutionCache

Optional externally owned cache shared across graph executions.

cancellationSignal CancellationSignal

Optional read-only cancellation signal supplied by the caller. The caller retains its corresponding CancellationHandle to request cooperative cancellation, then waits for the returned execution handle to complete its cleanup. A null signal creates an uncancelled execution-local signal.

Returns

ExecutionHandle

An ExecutionHandle that owns the running coroutine, progress state, and the DataPool for this execution.

Remarks

Nodes that support split execution may run through their coroutine path here. Callers typically yield on the returned handle, then remove final outputs from data before disposing it. The execution can only observe the signal and cannot request cancellation itself. Cancellation is observed between nodes and after node work returns; Unity or GPU work already executing is not interrupted. When cancellation is requested, callers should wait for the handle to complete and dispose it without treating its pooled data as successful output.