SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2601.03802 · 2026

Quantum vs. Classical Machine Learning: A Benchmark Study for Financial Prediction

Muhammad Shafique, Muhammad Kashif, Nouhaila Innan, Rehan Ahmad

arXiv · PDF · Open in the Atlas

Code that ran

3 of 3 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; 0 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; 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/2601.03802.json · badge: /api/ran/2601.03802.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
mit-han-lab/torchquantum canonical (classifier label)
classifier basis: census
3 ran · 0 no recorded run
FunctionStatusWhere it lives
apply_readout_error_func Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
mit-han-lab/torchquantum/torchquantum/noise_model/noise_models.py
code served (permissive licence) · get_code("431ecd880701ee17")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) 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)

# Construct x: measurement outcomes tensor of shape (batch_size, num_qubits)
# Using batch_size=2, num_qubits=4
x = torch.tensor([[-1.0, -1.0, 1.0, 1.0],
                   [1.0, -1.0, -1.0, 1.0]], dtype=torch.float32)

# Construct c2p_mapping: mapping from qubit indices (0, 1, 2, 3) to physical wire indices
c2p_mapping = {
    0: 0,
    1: 1,
    2: 2,
    3: 3
}

# Construct measure_info: measurement information dictionary with probabilities
# Structure: {(physical_wire,): {"probabilities": [[p_0_to_0, p_0_to_1], [p_1_to_0, p_1_to_1]]}}
# p_i_to_j is the probability of measuring j when the true value is i
measure_info = {
    (0,): {"probabilities": [[0.95, 0.05], [0.03, 0.97]]},
    (1,): {"probabilities": [[0.96, 0.04], [0.02, 0.98]]},
    (2,): {"probabilities": [[0.94, 0.06], [0.04, 0.96]]},
    (3,): {"probabilities": [[0.97, 0.03], [0.01, 0.99]]}
}

ARGS = {
    "x": x,
    "c2p_mapping": c2p_mapping,
    "measure_info": measure_info
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
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
get_combs Ran
ran; our contract draft was wrong, not the code
mit-han-lab/torchquantum/torchquantum/algorithm/quantumnas/super_layers.py
code served (permissive licence) · get_code("720a4ed306e8c638")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list. The image it ran in was not recorded. If your copy returns the same type 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 itertools
from typing import List, Iterable

# Test case 1: n=None (all combinations)
inset_1 = [1, 2, 3]
ARGS = {
    "inset": inset_1,
    "n": None
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
none outside the standard library — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type list — a list output has no array shape of its own; none is stated
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
parse_hamiltonian_file Ran
ran; our contract draft was wrong, not the code
mit-han-lab/torchquantum/torchquantum/algorithm/hamiltonian.py
code served (permissive licence) · get_code("2243b947de66156d")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned dict. The image it ran in was not recorded. If your copy returns the same type 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 tempfile
import os

# Create a temporary Hamiltonian file
temp_dir = tempfile.mkdtemp()
hamiltonian_file = os.path.join(temp_dir, "hamiltonian.txt")

# Write a valid Hamiltonian file content
hamiltonian_content = """h2 bk 2
-1.052373245772859 I0 I1
0.39793742484318045 I0 Z1
-0.39793742484318045 Z0 I1
-0.01128010425623538 Z0 Z1
0.18093119978423156 X0 X1"""

with open(hamiltonian_file, 'w') as f:
    f.write(hamiltonian_content)

ARGS = {
    'filename': hamiltonian_file
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
none outside the standard library — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type dict — a dict output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a dict output the recorded ndim 0 and dtype family float describe that coercion, not the output, and are not stated
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 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 2 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 0 the same month, 0 later) and 1 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
apply_readout_error_func 1 other paper
1 dated earlier
2107.10845 (2021-07)
QuantumNAS: Noise-Adaptive Search for Robust Quantum Circuits
parse_hamiltonian_file 1 other paper
1 dated earlier
2107.10845 (2021-07)
QuantumNAS: Noise-Adaptive Search for Robust Quantum Circuits

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

In this paper, we present a reproducible benchmarking framework that systematically compares QML models with architecture-matched classical counterparts across three financial tasks: (i) directional return prediction on U.S. and Turkish equities, (ii) live-trading simulation with Quantum LSTMs versus classical LSTMs on the S&P 500, and (iii) realized volatility forecasting using Quantum Support Vector Regression. By standardizing data splits, features, and evaluation metrics, our study provides a fair assessment of when current-generation QML models can match or exceed classical methods. Our results reveal that quantum approaches show performance gains when data structure and circuit design are well aligned. In directional classification, hybrid quantum neural networks surpass the parameter-matched ANN by +3.8 AUC and +3.4 accuracy points on AAPL stock and by +4.9 AUC and +3.6 accuracy points on Turkish stock KCHOL. In live trading, the QLSTM achieves higher riskadjusted returns in two of four S&P 500 regimes. For volatility forecasting, an angle-encoded QSVR attains the lowest QLIKE on KCHOL and remains within ∼0.02-0.04 QLIKE of the best classical kernels on S&P 500 and AAPL. Our benchmarking framework clearly identifies the scenarios where current QML architectures offer tangible improvements and where established classical methods continue to dominate.

For agents

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

get_harvested_code_for_paper("2601.03802")
get_code_for_paper("2601.03802")
have("2601.03802")

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

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

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

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

Connect an agent — have() is free.