Methods › General › Pruning › Dataset Pruning

Dataset Pruning

25 papers tagged archive 2025-07-28

Introduced by Shuo Yang et al. in Dataset Pruning: Reducing Training Data by Examining Generalization Influence

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

Dataset pruning is an approach to reduce a large dataset to obtain a small dataset by removing less significant sample.

PaperSource

In Syntology name not resolved (unknown_name). Other entries in Syntology's graph carry this name; the lookup's note below says what that means for this name.

From the lookup's note on this name: Nothing resolved to this name, but 2 entries in Syntology's graph carry it; the most cited is the paper “Dataset Pruning: Reducing Training Data by Examining Generalization Influence” (arXiv:2205.09329, 186 citations). The lookup reads this as a miss of its own name matching, not a gap in coverage: the graph holds the name under a spelling the lookup did not reach. For arXiv:2205.09329: its page on this site · ask the lookup about it.

Near matches the lookup lists, each a different name: Training-Free Dataset Pruning (TFDP); dataset; IG-Pruning; SFT dataset; ToM dataset; SFT dataset; KMA dataset; MCQ dataset.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

Papers archive 2025-07-28

archive papers tagged: 25 · with a code link: 12 · where Syntology ran a sample: 6 (5 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (6 of 25 tagged: 5 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 25 of 25, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

20 shown of 32 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Diversity2
Federated Learning2
Image Classification2
Natural Language Understanding2
image-classification2
8k1
All1
Classification1
Computational Efficiency1
Dataset Condensation1
Dataset Distillation1
Density Estimation1
Fairness1
GPU1
Graph Embedding1
Image Captioning1
Image Classification with Label Noise1
Image Super-Resolution1
Inductive Bias1
Informativeness1

Usage over time archive 2025-07-28

Papers per year tagged with Dataset Pruning: 2022 to 2025, peak 13 13 0 2022: 2 papers 2022 2023: 6 papers 2023 2024: 13 papers 2024 2025: 4 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (25 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Pruning

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