The library documents itself · Concurrency & distribution
stzComputePipeline
18 own methods · 0 forms written with extensions, listed under their method
the source: base/cluster/stzComputePipeline.ring(opens in a new tab) · All classes · The area reference: Concurrency & distribution
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
init
(no comment in the source: the name reads as a sentence) initno extension
Name_
(no comment in the source: the name reads as a sentence) name_no extension
Stage
declaring the pipeline -------------------------------------------- Add a stage: fWork(input) -> output, handled by the FACET pcFacet.no extension
NumberOfStages
(no comment in the source: the name reads as a sentence) number of stagesno extension
Facets
The ordered facet sequence (the routing contract).no extension
Stages
(no comment in the source: the name reads as a sentence) stagesno extension
SetPool
Attach a worker pool so each stage is admitted into its facet's budget (load isolation across the pipeline; R8.1). Facets not in the pool run unbudgeted. NOTE: the pipeline works on ITS pool (Haro stores a copy) -- read metrics via PoolQ(), not the caller's original.no extension
PoolQ
(no comment in the source: the name reads as a sentence) pool qno extension
ValidateAgainst
Check every stage's facet is offered by a catalog (the deployment's competences, R8.2). Returns [] when all known, else the unknown facets -- so a pipeline is validated against what a cluster can run.no extension
Run
running ------------------------------------------------------------ Thread pInput through every stage in order; each stage's output feeds the next. Returns the final output. Records a per-stage trace. A stage that RAISES is CONTAINED: the failure is traced, the facet slot is released (no leak), the pipeline HALTS and returns NULL, and Why()/ Failed() explain -- one bad stage never crashes the whole pipeline.no extension
Failed
(no comment in the source: the name reads as a sentence) failedno extension
Why
(no comment in the source: the name reads as a sentence) whyno extension
RunBatch
Run many inputs through the WHOLE pipeline; returns a result list (same order). The trace reflects the LAST input.no extension
Trace
(no comment in the source: the name reads as a sentence) traceno extension
StageDurations
Per-stage costs from the last Run: [ [ stageName, durMs ], ... ]. The slowest stage is the pipeline's bottleneck candidate.no extension
TotalMs
Total cost of the last Run (sum of its stage durations, ms).no extension
LastOutput
(no comment in the source: the name reads as a sentence) last outputno extension
Narrate
(no comment in the source: the name reads as a sentence) narrateno extension