Aligned series
(T, C)(P, C)(F, C + H)Future values must truly be known. Guesses belong in scenario analysis, not in the observed-data contract.
It treats forecasting as masked completion on a two-dimensional grid: time runs across, related series run down, and known future signals stay visible while the model fills every target horizon in one pass.
Use a retail scenario to see why multivariate context matters. The chart is an explanatory simulation: it mirrors the mechanism described by Google, but it does not run the 330M-parameter model in your browser.
Historical context on the left; 28-day forecast horizon on the right.
Shapes are the cleanest way to see what each boundary owns. T is targets, C is context length, P/F are covariate channels, and H is the requested horizon.
(T, C)(P, C)(F, C + H)Future values must truly be known. Guesses belong in scenario analysis, not in the observed-data contract.
per variate32 stepstime ↔ seriessingle passTwenty transformer layers in the public checkpoint alternate the two relationship types.
(T, H)(T, H, 9)0.1 … 0.9Quantiles describe modeled uncertainty. Local calibration still needs to be verified with held-out data.
Every step below changes the data representation. Select a stage or advance the trace to see its responsibility and hand-off.
Inspect the architecture by responsibility. The tabs keep model behavior, tensor contract, and purpose tied together.
Strong model explanations keep architecture facts, benchmark claims, and practical judgment in separate boxes.
Patch size, lookahead tokens, alternating attention, masked-horizon decode, and nine quantiles.
GOOGLE RESEARCH BLOG ↗20 layers, model dimension 1280, 16 heads, tensor shapes, data summary, and model license.
MODEL CARD ↗The original paper explains patch tokenization, residual projection, causal attention, and zero-shot pretraining.
ORIGINAL TIMESFM PAPER ↗The launch credits TiRex’s CPM strategy for the single-pass masked-horizon approach.
TIREX / CPM PAPER ↗Trust the architecture enough to test it—not enough to skip the test.
Run a leak-free rolling-origin backtest against seasonal naive and strong task-specific baselines. Check point error, quantile calibration, latency, memory, and license fit. Reject deployment if any critical requirement fails.