SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2202.03613 · 2022

Conformal Prediction Under Feedback Covariate Shift for Biomolecular Design

arXiv · PDF · Open in the Atlas

Code that ran

6 of 6 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; 3 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/2202.03613.json · badge: /api/ran/2202.03613.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
clarafy/conformal-for-design canonical (classifier label)
classifier basis: classifier_2025
3 ran · 0 no recorded run
copy not recorded community
not in the paper's declared repositories
3 ran · 0 no recorded run
FunctionStatusWhere it lives
get_loglikelihood Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
this paper's copy was not recorded; identical code first harvested from drewprinster/conformal-mfcs
pointer only · get_code("689d55842b0f0288")
How it ran

The body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. 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.

get_randomized_staircase_confidence_set Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
clarafy/conformal-for-design/calibrate.py
code served (permissive licence) · get_code("00450cc1174cf26c")
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 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 scipy as sc

# Set random seed for reproducibility
np.random.seed(0)

# Create small example data
m = 5  # number of calibration samples
scores_m = np.array([0.1, 0.3, 0.2, 0.5, 0.4])  # (m,) calibration scores
weights_m1 = np.array([0.15, 0.15, 0.15, 0.15, 0.15, 0.25])  # (m+1,) weights: m calibration + 1 test
predtest = 0.5  # float, prediction on test input
alpha = 0.1  # miscoverage level

ARGS = {
    "scores_m": scores_m,
    "weights_m1": weights_m1,
    "predtest": predtest,
    "alpha": alpha
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, scipy — 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 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
get_randomized_staircase_coverage Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
clarafy/conformal-for-design/calibrate.py
code served (permissive licence) · get_code("43136b4f9006dabb")
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 2, 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 get_randomized_staircase_coverage
# The function expects:
# - C_n: length-n list of outputs of get_randomized_staircase_confidence_set (list of tuples)
#   Each tuple represents a confidence interval list (list of 2-tuples with [lower, upper])
# - y_n: (n,) numpy array of true labels

# Create a small example with n=3 samples
n = 3

# C_n: list of confidence sets, where each confidence set is a list of intervals
# Each interval is a tuple (lower_bound, upper_bound)
C_n = [
    [(0.1, 0.5), (0.7, 0.9)],  # confidence set 1: two intervals
    [(0.2, 0.6)],               # confidence set 2: one interval
    [(0.3, 0.4), (0.6, 0.8)],  # confidence set 3: two intervals
]

# y_n: true labels, should be covered by some of the confidence sets above
y_n = np.array([0.3, 0.5, 0.7])

ARGS = {
    "C_n": C_n,
    "y_n": y_n,
}
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 tuple, ndim 2, 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
get_split_coverage Ran
ran, honoured the contract we drafted
clarafy/conformal-for-design/calibrate.py
code served (permissive licence) · get_code("f4800923ac4af83a")
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, 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 numpy as np

# Set random seed for reproducibility
np.random.seed(0)

# Create a small (n, 2) array of lower and upper bounds for confidence intervals
# n = 5 samples
lu_nx2 = np.array([
    [1.0, 3.0],
    [2.5, 4.5],
    [0.5, 2.0],
    [3.0, 5.0],
    [1.5, 3.5]
])

# Create a small (n,) array of true labels that fall within/outside the intervals
y_n = np.array([2.0, 4.0, 1.5, 4.5, 2.5])

ARGS = {
    "lu_nx2": lu_nx2,
    "y_n": y_n
}
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 float64, 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
phinuc2paa Ran
ran, honoured the contract we drafted
this paper's copy was not recorded; identical code first harvested from drewprinster/conformal-mfcs
pointer only · get_code("7f93af35d5251c0f")
How it ran

The body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. 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.

pnuc2paa Ran
ran, honoured the contract we drafted
this paper's copy was not recorded; identical code first harvested from drewprinster/conformal-mfcs
pointer only · get_code("66e533efe1108c9a")
How it ran

The body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. 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.

Also present in other papers' code

Of 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 distinct functions with an identity, 3 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 3 later) and 3 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
get_loglikelihood 1 other paper
1 later
2405.06627 (2024-05)
Conformal Validity Guarantees Exist for Any Data Distribution (and How to Find Them)
phinuc2paa 1 other paper
1 later
2405.06627 (2024-05)
Conformal Validity Guarantees Exist for Any Data Distribution (and How to Find Them)
pnuc2paa 1 other paper
1 later
2405.06627 (2024-05)
Conformal Validity Guarantees Exist for Any Data Distribution (and How to Find Them)

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

Many applications of machine learning methods involve an iterative protocol in which data are collected, a model is trained, and then outputs of that model are used to choose what data to consider next. For example, one data-driven approach for designing proteins is to train a regression model to predict the fitness of protein sequences, then use it to propose new sequences believed to exhibit greater fitness than observed in the training data. Since validating designed sequences in the wet lab is typically costly, it is important to quantify the uncertainty in the model's predictions. This is challenging because of a characteristic type of distribution shift between the training and test data in the design setting -- one in which the training and test data are statistically dependent, as the latter is chosen based on the former. Consequently, the model's error on the test data -- that is, the designed sequences -- has an unknown and possibly complex relationship with its error on the training data. We introduce a method to quantify predictive uncertainty in such settings. We do so by constructing confidence sets for predictions that account for the dependence between the training and test data. The confidence sets we construct have finite-sample guarantees that hold for any prediction algorithm, even when a trained model chooses the test-time input distribution. As a motivating use case, we demonstrate with several real data sets how our method quantifies uncertainty for the predicted fitness of designed proteins, and can therefore be used to select design algorithms that achieve acceptable trade-offs between high predicted fitness and low predictive uncertainty.

For agents

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

get_harvested_code_for_paper("2202.03613")
get_code_for_paper("2202.03613")
have("2202.03613")

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

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

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

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

Connect an agent — have() is free.