Papers › Shifts 2.0: Extending The Dataset of Real Distributional Shifts
Shifts 2.0: Extending The Dataset of Real Distributional Shifts
Andrey Malinin, Andreas Athanasopoulos, Muhamed Barakovic, Meritxell Bach Cuadra, Mark J. F. Gales, Cristina Granziera, Mara Graziani, Nikolay Kartashev, Konstantinos Kyriakopoulos, Po-Jui Lu, Nataliia Molchanova, Antonis Nikitakis, Vatsal Raina, Francesco La Rosa, Eli Sivena, Vasileios Tsarsitalidis, Efi Tsompopoulou, Elena Volf
Distributional shift, or the mismatch between training and deployment data, is a significant obstacle to the usage of machine learning in high-stakes industrial applications, such as autonomous driving and medicine. This creates a need to be able to assess how robustly ML models generalize as well as the quality of their uncertainty estimates. Standard ML baseline datasets do not allow these properties to be assessed, as the training, validation and test data are often identically distributed. Recently, a range of dedicated benchmarks have appeared, featuring both distributionally matched and shifted data. Among these benchmarks, the Shifts dataset stands out in terms of the diversity of tasks as well as the data modalities it features. While most of the benchmarks are heavily dominated by 2D image classification tasks, Shifts contains tabular weather forecasting, machine translation, and vehicle motion prediction tasks. This enables the robustness properties of models to be assessed on a diverse set of industrial-scale tasks and either universal or directly applicable task-specific conclusions to be reached. In this paper, we extend the Shifts Dataset with two datasets sourced from industrial, high-risk applications of high societal importance. Specifically, we consider the tasks of segmentation of white matter Multiple Sclerosis lesions in 3D magnetic resonance brain images and the estimation of power consumption in marine cargo vessels. Both tasks feature ubiquitous distributional shifts and a strict safety requirement due to the high cost of errors. These new datasets will allow researchers to further explore robust generalization and uncertainty estimation in new situations. In this work, we provide a description of the dataset and baseline results for both tasks.
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):
get_harvested_code_for_paper(arxiv_id="2206.15407")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2206.15407", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2206.15407")
Code
Syntology 19 code samples harvested from 1 repository linked to this paper: 18 ran (of which 0 constructed an object rather than computing a result; 18 with no instrument failure: 0 honoured, 0 violated, 18 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: official repository: 19 samples from 1 repository, 18 ran (18 with no instrument failure; 0 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
19 samples harvested: 18 ran (of which 0 constructed an object rather than computing a result; 18 with no instrument failure: 0 honoured, 0 violated, 18 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures 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.
Licence: 0 of the 19 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 shifts-project/shifts. “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.
32f31d880069ea9d · report
fixture: signature errors:ndarray/1/float, uncertainty:ndarray/1/float · returned tuple · level recorded 2026-09-25 2787e52d21a2bf7e · report
fixture: signature errors:ndarray/1/float, uncertainty:ndarray/1/float, group_by_uncertainty:bool/0/bool · returned ndarray · level recorded 2026-09-25 a99c182ce1216b6f · report
fixture: signature dataset_key_to_arrs:dict/0/? · returned dict · level recorded 2026-09-25 fc31ff56fab222ef · report
fixture: signature ground_truth:ndarray/3/float, predictions:ndarray/3/float · returned float32 · level recorded 2026-09-25 a7902a9714cafd0b · report
fixture: signature ground_truth:ndarray/3/int, predictions:ndarray/3/int · returned float32 · level recorded 2026-09-25 d992fc481289f284 · report
fixture: signature probs:ndarray/3/float, epsilon:float/0/float · returned dict · level recorded 2026-09-25 e4c7c0e0df8531fc · report
fixture: signature probs:ndarray/5/float, epsilon:float/0/float · returned ndarray · level recorded 2026-09-25 8c257ee78c6af4b0 · report
fixture: signature probs:ndarray/3/float, epsilon:float/0/float · returned ndarray · level recorded 2026-09-25 ac5749939a4c2e43 · report
fixture: signature probs:ndarray/3/float, epsilon:float/0/float · returned ndarray · level recorded 2026-09-25 b36ada5e86b4525d · report
fixture: signature model_preds:list/1/ndarray, model_conf_scores:list/1/ndarray, d:int/0/int · returned tuple · level recorded 2026-09-25 0c9ae6c1b138f23e · report
fixture: signature metric_name:str/0/str · returned str · level recorded 2026-09-25 83495554aedb7d95 · report
fixture: signature arr_len:int/0/int · returned int · level recorded 2026-09-25 1f5326db4a7bbe88 · report
fixture: signature metadata_cache_dir:str/0/str, chosen_dataset_keys:tuple/1/str · returned defaultdict · level recorded 2026-09-25 9f7420e10d09842f · report
fixture: signature metadata_cache_path:str/0/str · returned DataFrame · level recorded 2026-09-25 8c63b918b61bb33d · report
fixture: signature ground_truth:ndarray/1/float, predictions:ndarray/1/float, uncertainties:ndarray/1/float, parallel_backend:callable/0/? · returned float · level recorded 2026-09-25 d2ee41704e0bf321 · report
fixture: signature labels:ndarray/1/int, probs:ndarray/2/float, measure:ndarray/1/float, rev:bool/0/bool · returned tuple · level recorded 2026-09-25 2d472c7f8fa5769d · report
fixture: signature probs:ndarray/5/float, alpha:float/0/float · returned ndarray · level recorded 2026-09-25 936046ea2d77b177 · report
fixture: signature probs:ndarray/5/float, alpha:float/0/float · returned ndarray · level recorded 2026-09-25 65521763be938fc5 · report
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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