Home › Code › quantile_loss

quantile_loss

Syntologyentry name in harvested code

Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

quantile_loss appears in the code Syntology harvested for 15 papers, as 11 distinct code bodies found in 15 places (a place is one code body under one paper). Of the 15 papers, 12 with a sample that ran: 9 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument. 3 of the code bodies carry a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named quantile_loss do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 11 distinct code bodies named quantile_loss: 8 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 1 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

1ran · honoured contract
1ran · violated contract
1ran · our draft was wrong
1ran; the contract check could not run
4ran
3unverified
3fingerprinted

Licence is a property of each copy, so it is counted per place: 6 of the 15 places are pointer only (Syntology does not serve that copy's text); at 2 of those this paper's copy is under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text (hover the licence cell for why). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

15 papers shown of 15, newest first; 15 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive, and the graph's for 4 papers added by Syntology; 1 papers have no page here and are shown by their id only (arXiv: for an arXiv id; an id from another venue, such as ACL Anthology or AAAI, is named as that venue's id, never as an arXiv id). Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's 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.

PaperDateFileStatus SyntologyLicence
Self-Adaptive Scale Handling for Forecasting Time Series with Scale Heterogeneity added by Syntology 18 Jun 2026 Meteor-Stars/ASTSF/layers/Deepar_utils.py 6d4626bb0fc92bff unverified no licence file found · pointer only
CITRAS-FM: Tiny Time Series Foundation Model for Covariate-Informed Zero-Shot Forecasting added by Syntology 2026-06 (from id) hitachi-ais/citras-fm/citras_fm/utils/tools.py 51b9c7b2fb6abf39 ran · our draft was wrong licence not identified · pointer only
SurvivalPFN: Amortizing Survival Prediction via In-Context Bayesian Inference added by Syntology 2026-05 (from id) TeaPearce/Censored_Quantile_Regression_NN/01_code/models.py dd1c2e866b214fbf ran; the contract check could not run (RAISES) MIT (permissive)
From Samples to Scenarios: A New Paradigm for Probabilistic Forecasting added by Syntology 2025-09 (from id) Fifthky/TimePrism/tsExperiments/models/project_models/TimePrism/personnalized_evaluator.py 88ed0f0f4a676936 ran fingerprinted Apache-2.0 (permissive)
Toward Conditional Distribution Calibration in Survival Prediction 27 Oct 2024 shi-ang/makesurvivalcalibratedagain/model/loss.py eaa9dce19df6fc3d ran MIT (permissive)
Conformalized Survival Distributions: A Generic Post-Process to Increase Calibration 12 May 2024 shi-ang/CSD/model/loss.py eaa9dce19df6fc3d ran MIT (permissive)
The Rise of Diffusion Models in Time-Series Forecasting 5 Jan 2024 ai4healthuol/sssd/src/imputers/CSDI.py ff7efc68e98e1d55 ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only
BayOTIDE: Bayesian Online Multivariate Time series Imputation with functional decomposition 28 Aug 2023 xuangu-fang/bayotide/model_BayOTIDE.py ff7efc68e98e1d55 ran · honoured contract fingerprinted no licence file found · pointer only
IDQL: Implicit Q-Learning as an Actor-Critic Method with Diffusion Policies 20 Apr 2023 philippe-eecs/idql/jaxrl5/agents/ddpm_iql/ddpm_iql_learner.py bcaf26b4b210fed0 ran · violated contract no licence file found · pointer only
Censored Quantile Regression Neural Networks for Distribution-Free Survival Analysis 26 May 2022 teapearce/censored_quantile_regression_nn/01_code/models.py dd1c2e866b214fbf ran; the contract check could not run (RAISES) MIT (permissive)
Conformal Prediction Intervals with Temporal Dependence 25 May 2022 zlin7/cptd/models/losses.py f77066f61753a058 ran fingerprinted MIT (permissive)
CSDI: Conditional Score-based Diffusion Models for Probabilistic Time Series Imputation 7 Jul 2021 ermongroup/CSDI/utils.py ff7efc68e98e1d55 ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only
Probabilistic Forecasting with Temporal Convolutional Neural Network 11 Jun 2019 vpozdnyakov/deeptcn/deeptcn/quantile_deeptcn.py 6462bf5b424fbb52 unverified MIT (permissive)
Anomaly Detection using One-Class Neural Networks 18 Feb 2018 danielenricocahall/One-Class-NeuralNetwork/loss.py 896764f70a139e5c ran MIT (permissive)
OpenReview id openreview_0xJt4PqPJv shi-ang/SALaD/model/loss.py 51a6f12ab6a231e2 unverified MIT (permissive)

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the 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 under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. 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 cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

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