live wire
AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLMAI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
analysisAI

ASTEP gives language models a vocabulary for steering time-series forecasts

A joint RPI–IBM project published by Red Hat Research argues that controllable forecasting matters more than marginal leaderboard gains.

Time-series patches on one side, steerable token forecast on the other.
Side by side: what changed
By The News Desk· Aug 22, 2026

Time-series foundation models are running into a familiar maturity problem: benchmark scores keep moving, but it is increasingly difficult to tell whether the architecture, the training data or the recipe deserves the credit. A joint project from Rensselaer Polytechnic Institute and IBM Research, described in Red Hat Research Quarterly, proposes a more useful target: make forecasts steerable by language.

What changed

The project developed two related models. PatchTST-FM uses a conventional encoder-only Transformer with patch tokenization, missing-value normalization and a quantile output head. With public data, contiguous masking and a long context window, the team says this deliberately ordinary backbone matched or exceeded specialized time-series models on GIFT-Eval and TIME. The result is less a victory lap than a warning: leaderboard gains attributed to novel architectures may instead come from data and training differences.

ASTEP, short for Abstract Semantic Tokenizer-Predictor, tackles a different limitation. Conventional time-series models expose continuous numerical patches, which give a person or another model no clean way to express a high-level expectation. ASTEP converts a series into discrete tokens describing recurring temporal shapes at several scales. Coarse tokens can represent a gradual rise or plateau; finer tokens fill in shorter fluctuations.

That hierarchy matters. The team reports that multi-scale tokenization outperformed a single-scale version and that ASTEP's larger variant led its zero-shot GIFT-Eval comparison. More importantly, a user or language model can specify the coarse pattern and leave ASTEP to generate a probabilistic forecast consistent with it. The article says this intervention helps most at long horizons, where unconstrained forecasts diverge.

Who should care

The immediate audience is teams building forecasting agents for planning, monitoring and control. The broader project, called the Time-Series Data Agent, couples a language model to a forecasting model so a request such as “expect a slow rise, then a plateau” can become part of the forecast rather than an instruction applied after the fact.

The work also matters to model evaluators. PatchTST-FM is an argument for controlling data and training variables before crediting architectural novelty. ASTEP is an argument for measuring capabilities beyond zero-shot accuracy, including whether a model can accept structured human or machine guidance.

What to try

Practitioners should treat ASTEP as a research architecture, not a product announcement. The useful test is architectural: compare a standard forecasting baseline under a documented training recipe, then ask whether intervention improves decisions at the horizons that matter. If a forecasting agent cannot translate contextual reasoning into a constraint on the forecast, a higher leaderboard score may not solve the operational problem.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.