SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2307.07191 · 2023

Bridging AI and Energy Forecasting: An Autonomous Workflow with Customized Toolkit

arXiv · PDF · Open in the Atlas

Code that ran

4 of 4 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 3 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2307.07191.json · badge: /api/ran/2307.07191.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
leo-vk/proenfo canonical (classifier label)
classifier basis: plan_row
4 ran · 0 no recorded run
FunctionStatusWhere it lives
seasonality_model Ran
ran; our contract draft was wrong, not the code
leo-vk/proenfo/models/NBEATSX.py
code served (permissive licence) · get_code("a80543442281cf38")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned Tensor, ndim 2, dtype family float, shape (2, 6) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import numpy as np
import torch

torch.manual_seed(0)

# thetas: a 2D tensor where the second dimension is p (number of seasonality components)
# t: time values (1D array or list)
# device: torch device

# Looking at the function:
# - thetas.size()[-1] gets the last dimension of thetas
# - thetas.shape[1] gets the second dimension
# - p <= thetas.shape[1] must be true
# - thetas.mm(S) means thetas is 2D and we do matrix multiplication
# - S will have shape (p, len(t))
# - So thetas should be (batch_size, p)

batch_size = 2
p = 4  # number of seasonality components
time_steps = 6

thetas = torch.randn(batch_size, p)
t = np.linspace(0, 1, time_steps)
device = torch.device('cpu')

ARGS = {
    'thetas': thetas,
    't': t,
    'device': device
}
Setup block drafted by
a language model, Claude Sonnet 4.5, prompt python_fixture_v1
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 6) — shape (2, 6) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
squeeze_last_dim Ran
ran, honoured the contract we drafted
leo-vk/proenfo/models/NBEATSX.py
code served (permissive licence) · get_code("6b82ed8d296402a1")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch

torch.manual_seed(0)

# Create a 3D tensor with last dimension = 1 to test the squeeze functionality
tensor = torch.randn(2, 4, 1)

ARGS = {
    "tensor": tensor
}
Setup block drafted by
a language model, Claude Sonnet 4.5, prompt python_fixture_v1
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
transition Ran
ran; our contract draft was wrong, not the code
leo-vk/proenfo/models/FiLM.py
pointer only (licence: BSD-3-Clause); the stored copy get_code serves, from ARBrachet/PRO-DYN, is pointer only (licence: NONE) · get_code("c8733a0c39550140")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (BSD-3-Clause), but get_code serves the stored copy, first harvested from ARBrachet/PRO-DYN, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

trend_model Ran
ran; our contract draft was wrong, not the code
leo-vk/proenfo/models/NBEATSX.py
code served (permissive licence) · get_code("48c2e955f3036f30")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned Tensor, ndim 2, dtype family float, shape (2, 5) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import numpy as np
import torch

torch.manual_seed(0)

# thetas: a 2D tensor where the last dimension is p (number of polynomial terms)
# We'll use p=3 (less than or equal to 4)
# Let's say we have 2 series, so shape is (2, 3)
thetas = torch.randn(2, 3)

# t: a scalar or 1D array representing time points
# Let's use a 1D numpy array with 5 time points
t = np.array([0.0, 1.0, 2.0, 3.0, 4.0])

# device: a torch device
device = torch.device('cpu')

ARGS = {
    'thetas': thetas,
    't': t,
    'device': device
}
Setup block drafted by
a language model, Claude Sonnet 4.5, prompt python_fixture_v1
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 5) — shape (2, 5) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 4 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 0 the same month, 1 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
transition 3 other papers
3 later · 1 only as an assembly brick
2502.08942 (2025-02)
Language in the Flow of Time: Time-Series-Paired Texts Weaved into a Unified Temporal Narrative
2507.15774 (2025-07)
Time Series Forecasting Through the Lens of Dynamics
2601.01677 (2026-01)
Trustworthy Data-Driven Wildfire Risk Prediction and Understanding in Western Canada
seasonality_model 1 other paper
1 dated earlier
1905.10437 (2019-05)
N-BEATS: Neural basis expansion analysis for interpretable time series forecasting
squeeze_last_dim 1 other paper
1 dated earlier
1905.10437 (2019-05)
N-BEATS: Neural basis expansion analysis for interpretable time series forecasting
trend_model 1 other paper
1 dated earlier
1905.10437 (2019-05)
N-BEATS: Neural basis expansion analysis for interpretable time series forecasting

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Energy forecasting is crucial for the power grid, but fundamentally different from general time series analysis: it highly relies on covariates like meteorological factors, and its goals must align with actual power grid operations, such as risk assessment and system reliability. In order to bridge the huge gap between advanced machine learning forecasting models and actual power grid demand, this paper proposes an autonomous forecasting workflow based on LLMs. As a virtual analyst, the agent replaces tedious manual adjustments by autonomously analyzing data features, dynamically orchestrating optimal forecasting pipelines, and generating actionable analysis reports for decision-makers. The carefully arranged pipeline directly addresses the demand of the power grid through probabilistic forecasting for uncertainty quantification. Furthermore, the framework acts as an automated testbed, enabling seamless A/B testing of specific algorithmic plugins across various architectures to evaluate their empirical effectiveness. As the foundation of the algorithm, the underlying toolkit integrates 31 advanced temporal architectures and 6 customized exogenous modules, resulting in 146 highly configurable variants. In addition, to provide experience references for the agents, we established a large-scale benchmark on 21 energy datasets and released new high-quality renewable energy datasets with meteorological factors.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2307.07191")
get_code_for_paper("2307.07191")
have("2307.07191")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2307.07191.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2307.07191.svg)](https://syntology.ai/paper/2307.07191)

Connect an agent — have() is free.