Skip to main content

Module strategy

Module strategy 

Source
Expand description

Running a [TrainingStrategy].

The strategy types are contracts — a strategy is a graph-level attribute, part of what a graph is — so they live in soma-core beside the graph. Running one is not: it shards inputs, calls workers in a round loop, aggregates gradients and redistributes states. That is execution, and execution lives here.

See the “soma-core holds contracts, not execution” entry in the design decisions.

Structs§

TransportContext
A StrategyContext over one Transport per worker.
WorkerIdentity
How a worker can be named by a RemoteTarget.

Traits§

GradientAggregator
Contract for gradient aggregation across workers.
StateAggregator
Contract for federated state aggregation.
StrategyContext
Context provided to strategy executors. Abstracts worker communication — the strategy doesn’t know about WS/HTTP.
StrategyExecutor
Contract for training strategy execution. Every TrainingStrategy variant implements this — including Local.