Papers › Benchmarking Distribution Shift in Tabular Data with TableShift

Benchmarking Distribution Shift in Tabular Data with TableShift

10 Dec 2023NeurIPS 2023 11arXiv:2312.07577archive 2025-07-28

Josh Gardner, Zoran Popovic, Ludwig Schmidt

Robustness to distribution shift has become a growing concern for text and image models as they transition from research subjects to deployment in the real world. However, high-quality benchmarks for distribution shift in tabular machine learning tasks are still lacking despite the widespread real-world use of tabular data and differences in the models used for tabular data in comparison to text and images. As a consequence, the robustness of tabular models to distribution shift is poorly understood. To address this issue, we introduce TableShift, a distribution shift benchmark for tabular data. TableShift contains 15 binary classification tasks in total, each with an associated shift, and includes a diverse set of data sources, prediction targets, and distribution shifts. The benchmark covers domains including finance, education, public policy, healthcare, and civic participation, and is accessible using only a few lines of Python code via the TableShift API. We conduct a large-scale study comparing several state-of-the-art tabular data models alongside robust learning and domain generalization methods on the benchmark tasks. Our study demonstrates (1) a linear trend between in-distribution (ID) and out-of-distribution (OOD) accuracy; (2) domain robustness methods can reduce shift gaps but at the cost of reduced ID accuracy; (3) a strong relationship between shift gap (difference between ID and OOD performance) and shifts in the label distribution. The benchmark data, Python package, model implementations, and more information about TableShift are available at https://github.com/mlfoundations/tableshift and https://tableshift.org .

PaperPDFConference PDFCodeCode Syntology ran

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 12 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 2 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 11 ran (5 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

mlfoundations/tableshift officialmentioned in papermentioned on GitHubpytorchMITSyntology: 12 samples, 11 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

12 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 2 violated, 2 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. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

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

Licence: 0 of the 12 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 mlfoundations/tableshift. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

mlfoundations/tableshift official repository 12 samples, 11 ran (6 instrument-failed) · 1 unverified
all_subgroups_contain_all_label_values tableshift/core/metrics.py ran · our draft was wrong MIT (permissive) · 48a9a5abe2f8751c · report fixture: signature y_true:ndarray/1/int, sens:DataFrame/0/? · returned bool · level recorded 2026-09-24
basename_from_url tableshift/core/utils.py ran · our draft was wrong fingerprinted MIT (permissive) · 44769640be6da14f · report fixture: signature url:str/0/str · returned str · level recorded 2026-09-24
clip_torch_outputs tableshift/core/metrics.py ran fingerprinted MIT (permissive) · 3a5434c8ce981c2c · report fixture: signature t:Tensor/2/float, eps:float/0/float, clip_max:float/0/float, clip_min:float/0/float · returned Tensor · level recorded 2026-09-24
column_is_of_type tableshift/core/features.py ran · our draft was wrong MIT (permissive) · b5c24dcc5582f968 · report fixture: returned bool · level recorded 2026-09-24
concat_columns tableshift/core/splitter.py ran · our draft was wrong MIT (permissive) · febd5f9b4d01a6ca · report fixture: signature data:DataFrame/0/? · returned Series · level recorded 2026-09-24
extract_positive_class_predictions tableshift/core/metrics.py ran · violated contract fingerprinted MIT (permissive) · 502284e64831d19a · report fixture: signature y_pred:Tensor/2/float · returned Tensor · level recorded 2026-09-24
idx_where_in tableshift/core/splitter.py ran; the contract check could not run (RAISES) MIT (permissive) · d5300b8af5a99ec7 · report fixture: signature x:Series/1/float, vals:list/1/int · returned ndarray · level recorded 2026-09-24
idx_where_not_in tableshift/core/splitter.py ran; the contract check could not run (RAISES) MIT (permissive) · 5a1bc315e38a6053 · report fixture: signature x:Series/1/int, vals:list/1/int · returned ndarray · level recorded 2026-09-24
is_categorical in 5 papers tableshift/core/features.py ran · violated contract MIT (permissive) · c783977dad9f056e · report fixture: signature x:Series/1/category · returned bool · level recorded 2026-09-24
preprocess_physionet tableshift/datasets/physionet.py ran · honoured contract MIT (permissive) · 565af8f9ffde9bfe · report fixture: signature df:DataFrame/0/? · returned DataFrame · level recorded 2026-09-24
safe_cast tableshift/core/features.py ran MIT (permissive) · 6943c3f1ced7440d · report fixture: signature x:Series/1/float, dtype:callable/0/? · returned Series · level recorded 2026-09-24
download_file in 22 papers tableshift/core/utils.py unverified MIT (permissive) · bbdf216a1a512106 · report

Tasks

BenchmarkingBinary ClassificationDomain Generalization

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

SET

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