Jeff Schneider, Youngseog Chung, Willie Neiswanger, Ian Char
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-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/2011.09588.json · badge: /api/ran/2011.09588.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.
| Repository | Role | Ran |
|---|---|---|
| uncertainty-toolbox/uncertainty-toolbox | canonical (classifier label) classifier basis: classifier_2025 |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| get_q_idx | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
uncertainty-toolbox/uncertainty-toolbox/uncertainty_toolbox/recalibration.py code served (permissive licence) · get_code("168759e2be2462e5") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned int, ndim 0, dtype family int, 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.
|
| iso_recal | Ran ran; our contract draft was wrong, not the code |
uncertainty-toolbox/uncertainty-toolbox/uncertainty_toolbox/recalibration.py code served (permissive licence) · get_code("23838b8fd23163c7") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned IsotonicRegression. 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.
|
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-21.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Among the many ways of quantifying uncertainty in a regression setting, specifying the full quantile function is attractive, as quantiles are amenable to interpretation and evaluation. A model that predicts the true conditional quantiles for each input, at all quantile levels, presents a correct and efficient representation of the underlying uncertainty. To achieve this, many current quantile-based methods focus on optimizing the pinball loss. However, this loss restricts the scope of applicable regression models, limits the ability to target many desirable properties (e.g. calibration, sharpness, centered intervals), and may produce poor conditional quantiles. In this work, we develop new quantile methods that address these shortcomings. In particular, we propose methods that can apply to any class of regression model, select an explicit balance between calibration and sharpness, optimize for calibration of centered intervals, and produce more accurate conditional quantiles. We provide a thorough experimental evaluation of our methods, which includes a high dimensional uncertainty quantification task in nuclear fusion. We first lay out the notation, terminology, and class of models considered in this paper. Then we provide an overview of evaluation metrics in UQ and demonstrate how the pinball loss may be inadequate both as an evaluation metric and as an optimization objective. Bold upper case letters X, Y denote random variables, lower case letters x, y, denote their values, and calligraphic upper case letters X , Y denote sets of possible values. We use x ∈ X to denote the input feature vector and y ∈ Y to denote the corresponding target. Additionally, we consider the regression setting where Y ⊂ R and X ⊂ R n . We use F X , F Y|x , F Y to denote the true cumulative distribution of the subscript random variable. For any x ∈ X , we assume there exists a true conditional distribution F Y|x over Y, and we assume Q p (x) denotes the true p th quantile of this distribution, i.e. F Y|x (Q p (x)) = p. Any estimates of the true functions F, Q p will be denoted with a hat, F, Qp . We will specifically refer to any family of estimates for Q p , with p ∈ (0, 1), as a "quantile model", denoted Q : X × (0, 1) → Y. Unless otherwise noted, we will always consider the conditional problem of estimating quantities in the target space Y, conditioned on a value x ∈ X . While various metrics have been proposed to assess the quality of UQ, there has been a great deal of recent focus on the notions of calibration and sharpness [15,13,65,60,55,35,21,20]. We introduce calibration here, but for a more thorough treatment, see Zhao et al. [65]. Broadly speaking, calibration in the regression setting requires that the probability of observing the target random variable below a predicted p th quantile is equal to the expected probability p, for all p ∈ (0, 1). We refer to the former quantity as the observed probability and denote it p obs (p), for an expected probability p, which we 0 200 400 600 800 Train Epoch 10 1 6 × 10 2 2 × 10 1 3 × 10 1 Pinball Loss SQR Val Ep: 350 10 2 10 1 Calibration Loss Cali Val Ep: 410 (a) Test Loss Curves 0 200 400 600 800 Train Epoch 0.05 0.10 0.15 0.20 0.25 Calibration Error SQR Cali SQR Val Ep (350) Cali Val Ep (410) (b) Test Calibration
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2011.09588")
get_code_for_paper("2011.09588")
have("2011.09588")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2011.09588.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2011.09588)
Connect an agent — have() is free.