SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2109.03188 · 2021

Optimizing Quantum Variational Circuits with Deep Reinforcement Learning

arXiv · PDF · Open in the Atlas

Code that ran

2 of 2 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; 2 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/2109.03188.json · badge: /api/ran/2109.03188.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
lockwo/rl_qvc_opt canonical (classifier label)
classifier basis: classifier_2025
2 ran · 0 no recorded run
FunctionStatusWhere it lives
cnn_encoding Ran
ran; our contract draft was wrong, not the code
lockwo/rl_qvc_opt/deploy/augment.py
code served (permissive licence) · get_code("fd3fb029da3f68f7")
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) and returned ndarray, ndim 3, dtype family float, shape (5, 3, 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 numpy as np

# Analyze the function to understand parameter requirements:
# - max_q: int, used as dimension in np.zeros and modulo operation
# - max_d: int, used as dimension in np.zeros
# - num_q: int, used in modulo operation (i % num_q)
# - struct: indexable, length matches weights, values used as indices into state[:,:,:]
# - weights: indexable, length determines loop iterations, values are floats
# - error: scalar, assigned to state[:, :, 4]
# - input_type: scalar, assigned to state[:, :, 3]

# Create small but distinct dimensions
max_q = 3
max_d = 4
num_q = 2

# weights and struct must have same length
# Let's create 6 weights (3 qubits * 2 depths)
weights = np.array([0.1, 0.2, 0.3, 0.4, 0.5, 0.6], dtype=np.float32)

# struct contains indices into the 5th dimension (0-4)
# Using values 0, 1, 2 to index into state[:, :, struct[i]]
struct = np.array([0, 1, 2, 0, 1, 2], dtype=np.int32)

# error and input_type are scalars
error = 0.05
input_type = 1.0

ARGS = {
    "max_q": max_q,
    "max_d": max_d,
    "num_q": num_q,
    "struct": struct,
    "weights": weights,
    "error": error,
    "input_type": input_type,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 3, dtype family float, shape (5, 3, 4) — shape (5, 3, 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
mlp_encoding Ran
ran; our contract draft was wrong, not the code
lockwo/rl_qvc_opt/deploy/augment.py
code served (permissive licence) · get_code("54c6ee92844d1e4a")
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) and returned ndarray, ndim 1, dtype family float, shape (40,) 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

# Analyze the function to understand parameter requirements:
# - size: int, used as first dimension of state array
# - num_q: int, used in modulo operation (i % num_q)
# - num_d: int, stored in state but not used in computation
# - struct: array-like, indexed by i, length must be >= size
# - weights: array-like, indexed by i, length must be >= size
# - error: numeric, stored in state
# - input_type: numeric, stored in state

size = 5
num_q = 3
num_d = 7
struct = np.array([10, 20, 30, 40, 50])
weights = np.array([1.5, 2.5, 3.5, 4.5, 5.5])
error = 0.1
input_type = 2

ARGS = {
    "size": size,
    "num_q": num_q,
    "num_d": num_d,
    "struct": struct,
    "weights": weights,
    "error": error,
    "input_type": input_type
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 1, dtype family float, shape (40,) — shape (40,) 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 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 2 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.

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

Quantum Machine Learning (QML) is considered to be one of the most promising applications of near term quantum devices. However, the optimization of quantum machine learning models presents numerous challenges arising from the imperfections of hardware and the fundamental obstacles in navigating an exponentially scaling Hilbert space. In this work, we evaluate the potential of contemporary methods in deep reinforcement learning to augment gradient based optimization routines in quantum variational circuits. We find that reinforcement learning augmented optimizers consistently outperform gradient descent in noisy environments. All code and pretrained weights are available to replicate the results or deploy the models at: https://github.com/lockwo/rl_qvc_opt.

For agents

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

get_harvested_code_for_paper("2109.03188")
get_code_for_paper("2109.03188")
have("2109.03188")

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

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

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

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

Connect an agent — have() is free.