Papers › Data Distribution Valuation
Data Distribution Valuation
Xinyi Xu, Shuaiqi Wang, Chuan-Sheng Foo, Bryan Kian Hsiang Low, Giulia Fanti
Data valuation is a class of techniques for quantitatively assessing the value of data for applications like pricing in data marketplaces. Existing data valuation methods define a value for a discrete dataset. However, in many use cases, users are interested in not only the value of the dataset, but that of the distribution from which the dataset was sampled. For example, consider a buyer trying to evaluate whether to purchase data from different vendors. The buyer may observe (and compare) only a small preview sample from each vendor, to decide which vendor's data distribution is most useful to the buyer and purchase. The core question is how should we compare the values of data distributions from their samples? Under a Huber characterization of the data heterogeneity across vendors, we propose a maximum mean discrepancy (MMD)-based valuation method which enables theoretically principled and actionable policies for comparing data distributions from samples. We empirically demonstrate that our method is sample-efficient and effective in identifying valuable data distributions against several existing baselines, on multiple real-world datasets (e.g., network intrusion detection, credit card fraud detection) and downstream applications (classification, regression).
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="2410.04386")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2410.04386", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2410.04386")
Code
Syntology 13 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 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.
By repository: official repository: 13 samples from 1 repository, 12 ran (6 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 12 samples that ran has no recorded date.
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
13 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 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.
Licence: 0 of the 13 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 xinyiys/data_distribution_valuation. “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.
1682bb48a6f46300 · report
fixture: signature X:Tensor/2/float, Y:Tensor/2/float, sigma_list:list/1/int, biased:bool/0/bool, device:device/0/?, batch_size:int/0/int · returned Tensor · level recorded 2026-09-22 a0997c0acc0f3683 · report
fixture: signature D_Xs:list/1/Tensor, D_Ys:NoneType/0/?, V_X:Tensor/2/float, V_Y:Tensor/2/float, netD:callable/0/?, device:device/0/?, sample_size:NoneType/0/?, squared:bool/0/bool, batch_size:int/0/int, sigma_list:list/1/int · returned list · level recorded 2026-09-22 f783a3b23476dfc6 · report
fixture: signature model:callable/0/?, loader:list/1/tuple, device:device/0/? · returned Tensor · level recorded, date not recorded cbe4794453d07854 · report
fixture: signature correlation_df:DataFrame/0/?, name:str/0/str · returned DataFrame · level recorded 2026-09-24 0e0b1ef1ccf79eb6 · report
fixture: signature model:callable/0/?, train_loader:list/1/tuple, test_loader:list/1/tuple, epochs:int/0/int, device:device/0/? · returned SimpleRegressor · level recorded 2026-09-24 3f594ff441c3d230 · report
fixture: signature Pstar_X:list/1/ndarray, Pstar_Y:list/1/int, Q:list/1/ndarray, epsilon:float/0/float, size:int/0/int, labels:list/1/int · returned list · level recorded 2026-09-24 fdbaf4694487b065 · report
fixture: signature Pstar_X:list/1/Tensor, Pstar_Y:list/1/Tensor, Q_X:list/1/Tensor, Q_Y:list/1/Tensor, epsilon:float/0/float, size:int/0/int · returned tuple · level recorded 2026-09-24 bb890357a4a87c70 · report
fixture: signature f_of_X:Tensor/2/float, f_of_Y:Tensor/2/float · returned Tensor · level recorded 2026-09-24 261fa51f4424898d · report
fixture: signature filename:str/0/str · returned tuple · level recorded 2026-09-24 3c8a7d889a9a2cbb · report
fixture: signature X_train:Tensor/2/float, y_train:Tensor/1/int, degree:float/0/float, size:int/0/int, heterogeneity:str/0/str, vendor_index:NoneType/0/?, N:NoneType/0/?, interpolate:bool/0/bool · returned list · level recorded 2026-09-24 48a3b455cac473ed · report
fixture: signature X:Tensor/2/float, Y:Tensor/2/float, sigma_list:list/1/int, biased:bool/0/bool, device:device/0/? · returned Tensor · level recorded 2026-09-22 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 MMD-based valuation method (graph method: MMD-based valuation method). 3 bricks; individually on a fixture: 3 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; 3 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.
- get_MMD_values_uneven entry · level 1 · ran · our draft was wrong ·
a0997c0acc0f3683 - batched_rbf_mmd2 helper · level 1 · ran · our draft was wrong ·
1682bb48a6f46300 - rbf_mmd2 helper · level 1 · ran · our draft was wrong ·
48a3b455cac473ed
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="2410.04386") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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