Docs / jax4j-core / com.nablatensor.jax4j.engine
interface
AadExecutable
A tape that has been compiled by some AadEngine and can be replayed.
Recording and compilation happen once; after that a replay costs one dispatch to whatever backend produced this handle, no matter how many scenarios it covers. Inputs are arguments rather than baked-in constants, so setInput re-values a shifted parameters with no re-record and no re-compile.
An engine implements the five core methods — engineName(), tape(), setInput, replay and close(). The segmentation methods (replaySafe, calibrate, measuredPathsPerSecond, maxChunkSeconds) and compileSeconds have working defaults that split a large replay into budgeted dispatches; AbstractAadExecutable is an optional base that provides the same with its own bookkeeping plus tape flattening.
Methods
Identifier of the engine that produced this handle, e.g. cuda.
One dispatch covering paths scenarios starting at pathOffset.
Wall-clock compilation time, paid once. Zero for engines that interpret.
Replays totalPaths as a series of dispatches, each sized from a measured rate to stay within maxChunkSeconds().
Measures throughput with dispatches that start small and grow.
Per-dispatch wall-clock budget used to size chunks.