Papers › Relaxed Quantile Regression: Prediction Intervals for Asymmetric Noise

Relaxed Quantile Regression: Prediction Intervals for Asymmetric Noise

5 Jun 2024arXiv:2406.03258archive 2025-07-28

Thomas Pouplin, Alan Jeffares, Nabeel Seedat, Mihaela van der Schaar

Constructing valid prediction intervals rather than point estimates is a well-established approach for uncertainty quantification in the regression setting. Models equipped with this capacity output an interval of values in which the ground truth target will fall with some prespecified probability. This is an essential requirement in many real-world applications where simple point predictions' inability to convey the magnitude and frequency of errors renders them insufficient for high-stakes decisions. Quantile regression is a leading approach for obtaining such intervals via the empirical estimation of quantiles in the (non-parametric) distribution of outputs. This method is simple, computationally inexpensive, interpretable, assumption-free, and effective. However, it does require that the specific quantiles being learned are chosen a priori. This results in (a) intervals that are arbitrarily symmetric around the median which is sub-optimal for realistic skewed distributions, or (b) learning an excessive number of intervals. In this work, we propose Relaxed Quantile Regression (RQR), a direct alternative to quantile regression based interval construction that removes this arbitrary constraint whilst maintaining its strengths. We demonstrate that this added flexibility results in intervals with an improvement in desirable qualities (e.g. mean width) whilst retaining the essential coverage guarantees of quantile regression.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 7 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 6 ran (0 with no instrument failure; 6 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tpouplin/rqr officialmentioned in papermentioned on GitHubpytorchSyntology: 7 samples, 6 ran (6 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

5ran · our draft was wrong
1ran; the contract check could not run
1unverified

Licence: 0 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from tpouplin/rqr. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

tpouplin/rqr official repository 7 samples, 6 ran (6 instrument-failed) · 1 unverified
GaussianKernelMatrix src/RQR-O/losses.py ran · our draft was wrong fingerprinted BSD-3-Clause (permissive) · 69d96d5ce93bdd5b · report fixture: signature x:Tensor/2/float, sigma:int/0/int · returned Tensor · level recorded 2026-09-22
HSIC in 5 papers src/RQR-O/losses.py ran · our draft was wrong BSD-3-Clause (permissive) · 179e3979e3baf728 · report fixture: signature x:Tensor/2/float, y:Tensor/2/float, s_x:float/0/float, s_y:float/0/float · returned Tensor · level recorded 2026-09-22
compute_coverages_and_avg_interval_len src/RQR-O/losses.py ran · our draft was wrong BSD-3-Clause (permissive) · 29cab5d016e44af2 · report fixture: signature y:Tensor/1/float, y_lower:Tensor/1/float, y_upper:Tensor/1/float · returned tuple · level recorded 2026-09-22
independence_penalty src/RQR-O/losses.py ran; the contract check could not run (RAISES) fingerprinted BSD-3-Clause (permissive) · 7075e9f3dc11708e · report fixture: signature y:Tensor/2/float, pred_l:Tensor/2/float, pred_u:Tensor/2/float, pearsons_corr_multiplier:int/0/int, hsic_multiplier:int/0/int, y_multiplier:int/0/int · returned int · level recorded 2026-09-22
pairwise_distances in 34 papers
census: 14 implementations from 13 papers, 7 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind float, dtype float32
src/RQR-O/losses.py ran · our draft was wrong fingerprinted BSD-3-Clause (permissive) · 92723afcb622bb4d · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
pearsons_corr2d src/RQR-O/losses.py ran · our draft was wrong fingerprinted BSD-3-Clause (permissive) · 477227d65660abff · report fixture: signature x:Tensor/2/float, y:Tensor/2/float · returned Tensor · level recorded 2026-09-22
RQR_loss src/RQR-O/losses.py unverified BSD-3-Clause (permissive) · 5d256576da960ca0 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Relaxed Quantile Regression (graph method: Relaxed Quantile Regression). 7 bricks; individually on a fixture: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. RQR_loss entry · level 0 · unverified · 5d256576da960ca0
  2. independence_penalty loss · level 1 · ran; the contract check could not run (RAISES) · 7075e9f3dc11708e
  3. HSIC helper · level 1 · ran · our draft was wrong · 179e3979e3baf728
  4. compute_coverages_and_avg_interval_len helper · level 1 · ran · our draft was wrong · 29cab5d016e44af2
  5. pearsons_corr2d helper · level 1 · ran · our draft was wrong · 477227d65660abff
  6. GaussianKernelMatrix helper · level 1 · ran · our draft was wrong · 69d96d5ce93bdd5b
  7. pairwise_distances helper · level 1 · ran · our draft was wrong · 92723afcb622bb4d

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2406.03258") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

PredictionPrediction IntervalsUncertainty Quantificationquantile regressionregression

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections