SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2002.08376 · 2020

A differentiable programming method for quantum control

arXiv · PDF · Open in the Atlas

Code that ran

6 of 7 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 6 have no contract verdict; 0 failures of our instrument; 1 no recorded run), measured 2026-11-21; 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/2002.08376.json · badge: /api/ran/2002.08376.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
frankschae/A-differentiable-programming-method-for-quantum-control canonical (classifier label)
classifier basis: census
6 ran · 1 no recorded run
FunctionStatusWhere it lives
create_init_state Ran
ran on a synthesized input
frankschae/A-differentiable-programming-method-for-quantum-control/qubit/differentiable_programming/dpqc_qubit.py
code served (permissive licence) · get_code("d40985dfe642ad4c")
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 tuple, ndim 3, dtype family float; no output shape is stated. The image it ran in was not recorded. The code mentions cuda, and the harness aliases cuda to the CPU for every sample; whether this run needed that is not recorded. If your copy returns the same type and ndim 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)

ARGS = {
    "noise": True,
    "n_par": 2,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 3, dtype family float — a tuple output has no array shape of its own; none is stated
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
generate_drive Ran
ran on a synthesized input
frankschae/A-differentiable-programming-method-for-quantum-control/spin_chain/GHZ/spinchain.py
code served (permissive licence) · get_code("649627097088c531")
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 3, dtype family float, shape (2, 3, 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 torch

torch.manual_seed(0)

# Analyze the function:
# - drive_strengths: used in einsum as 'bi', so shape (batch, i)
# - drive: used in einsum as 'ijk', so shape (i, j, k)
# - output: 'bjk', so shape (batch, j, k)

# Create small tensors with distinct dimensions
batch_size = 2
i_dim = 4
j_dim = 3
k_dim = 5

drive_strengths = torch.randn(batch_size, i_dim)  # shape (2, 4)
drive = torch.randn(i_dim, j_dim, k_dim)  # shape (4, 3, 5)

ARGS = {
    'drive_strengths': drive_strengths,
    'drive': drive,
}
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 3, dtype family float, shape (2, 3, 5) — shape (2, 3, 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
kronecker Ran
ran on a synthesized input
frankschae/A-differentiable-programming-method-for-quantum-control/spin_chain/GHZ/spinchain.py
code served (permissive licence) · get_code("5ed591024be2e265")
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 (8, 15) 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 two small tensors for the Kronecker product
# A will be 2x3, B will be 4x5
# This gives us distinct dimensions to probe later
A = torch.randn(2, 3)
B = torch.randn(4, 5)

ARGS = {
    'A': A,
    'B': B
}
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 (8, 15) — shape (8, 15) 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
list_kronecker Ran
ran on a synthesized input
frankschae/A-differentiable-programming-method-for-quantum-control/spin_chain/GHZ/spinchain.py
code served (permissive licence) · get_code("d0a63eba0c241c50")
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 (48, 105) 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 small distinct-sized tensor operators for Kronecker product
# Each operator should be a 2D matrix
op1 = torch.randn(2, 3)  # 2x3 matrix
op2 = torch.randn(4, 5)  # 4x5 matrix
op3 = torch.randn(6, 7)  # 6x7 matrix

# Test with nsite=1 (should return oplist[0])
oplist_1 = [op1]

# Test with nsite=2 (should kronecker op1 and op2)
oplist_2 = [op1, op2]

# Test with nsite=3 (should kronecker all three)
oplist_3 = [op1, op2, op3]

ARGS = {
    'oplist': oplist_3,
    'nsite': 3
}
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 (48, 105) — shape (48, 105) 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
log_normal Ran
ran on a synthesized input
frankschae/A-differentiable-programming-method-for-quantum-control/qubit/reinforce/policy_gradient_qubit.py
code served (permissive licence) · get_code("2c5697ebeebf54cd")
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
import numpy as np
from torch.autograd import Variable
import math

torch.manual_seed(0)

# Create small tensors for the function parameters
x = torch.randn(2, 4)  # batch size 2, dim 4
mu = torch.randn(2, 4)
sigma_sq = torch.abs(torch.randn(2, 4)) + 0.1  # ensure positive values

ARGS = {
    "x": x,
    "mu": mu,
    "sigma_sq": sigma_sq
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
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, 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
select_action Ran
ran on a synthesized input
frankschae/A-differentiable-programming-method-for-quantum-control/qubit/reinforce/policy_gradient_qubit.py
code served (permissive licence) · get_code("e35734bfb6c1e4ee")
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 tuple. The image it ran in was not recorded. The code mentions cuda, and the harness aliases cuda to the CPU for every sample; whether this run needed that is 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 torch
import torch.nn as nn
from torch.autograd import Variable
import math
import numpy as np

torch.manual_seed(0)

class SimplePolicy(nn.Module):
    def __init__(self):
        super(SimplePolicy, self).__init__()
        self.fc1 = nn.Linear(5, 8)
        self.mu_head = nn.Linear(8, 4)
        self.sigma_head = nn.Linear(8, 4)
    
    def forward(self, state, action):
        x = torch.cat([state, action], dim=-1)
        hidden = torch.relu(self.fc1(x))
        mu = self.mu_head(hidden)
        sigma_sq = torch.nn.functional.softplus(self.sigma_head(hidden)) + 1e-6
        return mu, sigma_sq

policy = SimplePolicy()

last_state = torch.randn(2, 3)
last_action = torch.randn(2, 2)

ARGS = {
    'policy': policy,
    'last_state': last_state,
    'last_action': last_action
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple 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
create_init_state Not yet run
unverified (harvested, no recorded run)
frankschae/A-differentiable-programming-method-for-quantum-control/quantum_parametric_oscillator/cat/para.py
code served (permissive licence) · get_code("e501f56428eb7d40")
How it ran

no invocation recorded.

Also present in other papers' code

Of 7 samples lifted from this paper's linked repositories, 7 carry a function identity and 0 do not. Of the 7 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 7 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-21.

Repositories linked to this paper

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

Abstract

Optimal control is highly desirable in many current quantum systems, especially to realize tasks in quantum information processing. We introduce a method based on differentiable programming to leverage explicit knowledge of the differential equations governing the dynamics of the system. In particular, a control agent is represented as a neural network that maps the state of the system at a given time to a control pulse. The parameters of this agent are optimized via gradient information obtained by direct differentiation through both the neural network \emph{and} the differential equation of the system. This fully differentiable reinforcement learning approach ultimately yields time-dependent control parameters optimizing a desired figure of merit. We demonstrate the method's viability and robustness to noise in eigenstate preparation tasks for three systems: a~single qubit, a~chain of qubits, and a quantum parametric oscillator.

For agents

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

get_harvested_code_for_paper("2002.08376")
get_code_for_paper("2002.08376")
have("2002.08376")

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

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

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

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

Connect an agent — have() is free.