SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1812.09976 · 2018

Quantum Chemistry in the Age of Quantum Computing

arXiv · PDF · Open in the Atlas

Code that ran

11 of 15 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 11 have no contract verdict; 0 failures of our instrument; 4 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/1812.09976.json · badge: /api/ran/1812.09976.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
CDL-Quantum/CohortProject_2020 community (classifier label)
classifier basis not recorded on the link
8 ran · 3 no recorded run
shukob/CohortProject_2020_2 community (classifier label)
classifier basis not recorded on the link
3 ran · 0 no recorded run
CDLQuantum2020-RBM-Team3/CohortProject_2020 community (classifier label)
classifier basis not recorded on the link
0 ran · 1 no recorded run
FunctionStatusWhere it lives
Vij Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_1_RBM_and_Tomography/Rydberg_energy_calculator.py
code served (permissive licence) · get_code("1a49a28ac561531e")
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 float, ndim 0, dtype family float, shape () 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

torch.manual_seed(0)

# The function Vij(R, i, j) computes 1.0 / (R * abs(i - j)) ** 6.0
# It takes:
# - R: a scalar or array (used in multiplication and exponentiation)
# - i: an integer or value that supports subtraction
# - j: an integer or value that supports subtraction

# Create simple scalar and integer arguments
R = 2.5  # A scalar float value
i = 3    # An integer index
j = 1    # An integer index

ARGS = {
    "R": R,
    "i": i,
    "j": j
}
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 float, ndim 0, dtype family float, shape () — shape () 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
convert_mol_data_to_xyz_format Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_2_VQE_Molecules/utility.py
code served (permissive licence) · get_code("bb141a3893674987")
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 str. 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 torch
import numpy as np

torch.manual_seed(0)

# mol_data is expected to be an iterable of atoms
# Each atom is a tuple/list where:
# - atom[0] is a string (element symbol)
# - atom[1] is an iterable of coordinates (floats)

mol_data = [
    ('C', [0.0, 0.0, 0.0]),
    ('H', [1.0898, 0.0, 0.0]),
    ('H', [-0.5449, 0.9437, 0.0]),
    ('H', [-0.5449, -0.4719, 0.8177]),
]

ARGS = {
    'mol_data': mol_data
}
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 str — a str output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a str 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
energy_from_freq Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_1_RBM_and_Tomography/H2_energy_calculator.py
code served (permissive licence) · get_code("26b42ad216a1d9d4")
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 float64, ndim 0, dtype family float; no output shape is stated. The image it ran in was 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)

# Create sample data: 2 samples, each is a 2D vector matching basis vectors
samples = torch.tensor([
    [0.0, 0.0],
    [1.0, 1.0],
], dtype=torch.float32)

# Create coefficient array with 8 elements (indices 0-7, using 1:-1 gives indices 1-6)
coeff = np.array([0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8])

ARGS = {
    "samples": samples,
    "coeff": coeff,
}
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 float64, ndim 0, dtype family float — no output shape is stated: observe_signature.py recorded float ndim 0, which disagrees with the fixture run
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
find_sample_frequency Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_1_RBM_and_Tomography/H2_energy_calculator.py
code served (permissive licence) · get_code("429a8beaaa71cdac")
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 ndarray, ndim 1, dtype family float, shape (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

torch.manual_seed(0)

# The function expects 'samples' to be an iterable of torch tensors
# that can be compared element-wise with 2D tensors from the basis
# Each sample should be comparable to basis vectors of shape [2]

samples = [
    torch.tensor([0.0, 0.0]),
    torch.tensor([0.0, 1.0]),
    torch.tensor([1.0, 0.0]),
    torch.tensor([1.0, 1.0]),
    torch.tensor([0.0, 0.0]),
]

ARGS = {
    "samples": samples
}
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 ndarray, ndim 1, dtype family float, shape (4,) — shape (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
lorentzian Ran
ran on a synthesized input
shukob/CohortProject_2020_2/Project_3_Franck_Condon_Factors/lorentzian_smoothing.py
code served (permissive licence) · get_code("004e5a44fdd859e0")
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 1, dtype family float, shape (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

torch.manual_seed(0)

# Lorentzian function parameters:
# x: input values (tensor or array)
# x0: center of the peak (scalar)
# a: amplitude (scalar)
# gam: gamma/width parameter (scalar)

x = torch.tensor([1.0, 2.0, 3.0, 4.0], dtype=torch.float32)
x0 = torch.tensor(2.5, dtype=torch.float32)
a = torch.tensor(1.0, dtype=torch.float32)
gam = torch.tensor(0.5, dtype=torch.float32)

ARGS = {
    "x": x,
    "x0": x0,
    "a": a,
    "gam": gam
}
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 1, dtype family float, shape (4,) — shape (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
lorentzian_smoothing Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_3_Franck_Condon_Factors/common/utils.py
code served (permissive licence) · get_code("4e60852f5dab2cf3")
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 ndarray, ndim 2, dtype family float, shape (2, 1000) 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

# Create a small example of stick data
# sticks should be a 2D numpy array with shape [2, n_sticks]
# First row: energies, second row: intensities

energies = np.array([1.0, 2.5, 4.2, 5.8])
intensities = np.array([0.5, 1.2, 0.8, 0.3])
sticks = np.vstack([energies, intensities])

ARGS = {
    "sticks": sticks,
    "gamma": 100.0,
    "points": 1000,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
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 2, dtype family float, shape (2, 1000) — shape (2, 1000) 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
modes_from_counts Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_3_Franck_Condon_Factors/sampleX.py
code served (permissive licence) · get_code("7b07a474ce874828")
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, ndim 1, dtype family int; no output shape is stated. The image it ran in was 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 torch
import numpy as np

# Analyze the function: modes_from_counts takes a list of counts
# and converts it to a list of modes where photons/clicks were observed.
# The function iterates through enumerate(s) and accesses each element as c,
# converts it to int, and uses the index i.

# Create a simple list of counts
s = [0, 1, 0, 1, 2, 0]

ARGS = {
    "s": s
}
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 list, ndim 1, dtype family int — a list 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
multi_lorentz Ran
ran on a synthesized input
shukob/CohortProject_2020_2/Project_3_Franck_Condon_Factors/lorentzian_smoothing.py
code served (permissive licence) · get_code("a39c46d3b81d28fe")
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 ndarray, ndim 1, dtype family float, shape (100,) 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

torch.manual_seed(0)

# Construct arguments for multi_lorentz(x, params)
# x: input array/tensor for the lorentzian function
# params: list of parameters where each triplet (x0, a, gam) defines a lorentzian peak

# Create input x as a numpy array or tensor
x = np.linspace(-10, 10, 100)

# Create params as a list of lorentzian parameters
# Each lorentzian needs 3 parameters: x0 (center), a (amplitude), gam (gamma/width)
# Let's create 2 lorentzian peaks
params = [
    2.0,   # x0 for first lorentzian
    1.5,   # a (amplitude) for first lorentzian
    0.5,   # gam (gamma) for first lorentzian
    -3.0,  # x0 for second lorentzian
    2.0,   # a (amplitude) for second lorentzian
    0.8,   # gam (gamma) for second lorentzian
]

ARGS = {
    "x": x,
    "params": params,
}
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 ndarray, ndim 1, dtype family float, shape (100,) — shape (100,) 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
one Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_1_RBM_and_Tomography/H2_energy_calculator.py
code served (permissive licence) · get_code("dd1125764088c43a")
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 0, dtype family float, shape () 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)

freq = torch.randn(2, 4)

ARGS = {
    "freq": freq
}
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 0, dtype family float, shape () — shape () 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
postselect Ran
ran on a synthesized input
CDL-Quantum/CohortProject_2020/Project_3_Franck_Condon_Factors/sampleX.py
code served (permissive licence) · get_code("1ffdebe21b400db4")
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, ndim 2, dtype family int; no output shape is stated. The image it ran in was 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.

ARGS = {
    "samples": [[1, 1, 1, 1, 1], [1, 1, 0, 1, 1], [0, 0, 0, 0, 0], [1, 0, 0, 0, 1]],
    "min_count": 2,
    "max_count": 4
}
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, ndim 2, dtype family int — a list 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
res_multi_lorentz Ran
ran on a synthesized input
shukob/CohortProject_2020_2/Project_3_Franck_Condon_Factors/lorentzian_smoothing.py
code served (permissive licence) · get_code("78d9a530a3654620")
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, ndim 1, dtype family float; no output shape is stated. The image it ran in was 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

# Construct arguments for res_multi_lorentz(params, xData, yData)

# params: list/array of parameters for multi_lorentz
# The function expects params to be iterable with elements that can be unpacked
# as (x0, a, gam) triplets for each Lorentzian peak
# Let's create params for 2 Lorentzian peaks: [x0_1, a_1, gam_1, x0_2, a_2, gam_2]
params = [1.0, 2.0, 0.5, 3.0, 1.5, 0.3]

# xData: iterable of x values (list or array)
# The function zips xData with yData, so they must be the same length
xData = np.array([0.5, 1.0, 1.5, 2.0, 2.5, 3.0])

# yData: iterable of y values (list or array)
# Same length as xData
yData = np.array([1.2, 2.1, 1.8, 1.5, 1.3, 2.0])

ARGS = {
    'params': params,
    'xData': xData,
    'yData': yData
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type list, ndim 1, dtype family float — a list 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
energy Not yet run
unverified (harvested, no recorded run)
CDL-Quantum/CohortProject_2020/Project_1_RBM_and_Tomography/Rydberg_energy_calculator.py
code served (permissive licence) · get_code("3044b46a01b62f57")
How it ran

no invocation recorded.

load_dataset Not yet run
unverified (harvested, no recorded run)
CDLQuantum2020-RBM-Team3/CohortProject_2020/Project_1_RBM_and_Tomography/helper.py
code served (permissive licence) · get_code("d37813dd891dfab9")
How it ran

no invocation recorded.

object_einsum Not yet run
unverified (harvested, no recorded run)
CDL-Quantum/CohortProject_2020/Project_4_Ising_Annealer/object_einsum.py
code served (permissive licence) · get_code("57bc8e6cbeded5c5")
How it ran

no invocation recorded.

read_idx Not yet run
unverified (harvested, no recorded run)
CDL-Quantum/CohortProject_2020/Project_1_RBM_and_Tomography/MNIST/Load_MNIST.py
code served (permissive licence) · get_code("7bd7b2ec574c073a")
How it ran

no invocation recorded.

Also present in other papers' code

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

Practical challenges in simulating quantum systems on classical computers have been widely recognized in the quantum physics and quantum chemistry communities over the past century. Although many approximation methods have been introduced, the complexity of quantum mechanics remains hard to appease. The advent of quantum computation brings new pathways to navigate this challenging complexity landscape. By manipulating quantum states of matter and taking advantage of their unique features such as superposition and entanglement, quantum computers promise to efficiently deliver accurate results for many important problems in quantum chemistry such as the electronic structure of molecules. In the past two decades significant advances have been made in developing algorithms and physical hardware for quantum computing, heralding a revolution in simulation of quantum systems. This article is an overview of the algorithms and results that are relevant for quantum chemistry. The intended audience is both quantum chemists who seek to learn more about quantum computing, and quantum computing researchers who would like to explore applications in quantum chemistry.

For agents

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

get_harvested_code_for_paper("1812.09976")
get_code_for_paper("1812.09976")
have("1812.09976")

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

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

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

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

Connect an agent — have() is free.