SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2201.08528 · 2022

To SMOTE, or not to SMOTE?

arXiv · PDF · Open in the Atlas

Code that ran

1 of 1 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 1 has no contract verdict; 0 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2201.08528.json · badge: /api/ran/2201.08528.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
aws/to-smote-or-not canonical (classifier label)
classifier basis not recorded on the link
1 ran · 0 no recorded run
FunctionStatusWhere it lives
filter_optimal_hps Ran
ran on a synthesized input
aws/to-smote-or-not/src/analyze.py
code served (permissive licence) · get_code("dc6c826176481f0f")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned DataFrame. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import pandas as pd
import numpy as np

# Create a sample dataframe with the expected structure
np.random.seed(0)

# Define parameters
num_rows = 120
datasets = ['dataset_A', 'dataset_B', 'dataset_C']
seeds = [1, 2]
learners = ['learner_X', 'learner_Y']
oversamplers = ['oversampler_1', 'oversampler_2']
param_sets = ['param_set_1', 'param_set_2', 'param_set_3']

# Create base dataframe
data = {
    'dataset': np.random.choice(datasets, num_rows),
    'seed': np.random.choice(seeds, num_rows),
    'learner': np.random.choice(learners, num_rows),
    'oversampler': np.random.choice(oversamplers, num_rows),
    'param_set': np.random.choice(param_sets, num_rows),
    'accuracy': np.random.uniform(0.7, 0.99, num_rows),
    'f1_score': np.random.uniform(0.65, 0.98, num_rows),
    'precision': np.random.uniform(0.68, 0.97, num_rows),
    'recall': np.random.uniform(0.72, 0.96, num_rows),
}

df = pd.DataFrame(data)

# Ensure we have complete combinations for the assertion to pass
# We need exactly 3 datasets × 2 seeds = 6 combinations per (learner, oversampler)
expanded_rows = []
for dataset in datasets:
    for seed in seeds:
        for learner in learners:
            for oversampler in oversamplers:
                for param_set in param_sets:
                    expanded_rows.append({
                        'dataset': dataset,
                        'seed': seed,
                        'learner': learner,
                        'oversampler': oversampler,
                        'param_set': param_set,
                        'accuracy': np.random.uniform(0.7, 0.99),
                        'f1_score': np.random.uniform(0.65, 0.98),
                        'precision': np.random.uniform(0.68, 0.97),
                        'recall': np.random.uniform(0.72, 0.96),
                    })

df = pd.DataFrame(expanded_rows)

opt_metric = 'accuracy'
output_metrics = ['accuracy', 'f1_score', 'precision', 'recall']

ARGS = {
    'df': df,
    'opt_metric': opt_metric,
    'output_metrics': output_metrics,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, pandas — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type DataFrame — a DataFrame output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a DataFrame output the recorded ndim 2 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 1 samples lifted from this paper's linked repositories, 1 carry a function identity and 0 do not. Of the 1 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 1 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Balancing the data before training a classifier is a popular technique to address the challenges of imbalanced binary classification in tabular data. Balancing is commonly achieved by duplication of minority samples or by generation of synthetic minority samples. While it is well known that balancing affects each classifier differently, most prior empirical studies did not include strong state-of-the-art (SOTA) classifiers as baselines. In this work, we are interested in understanding whether balancing is beneficial, particularly in the context of SOTA classifiers. Thus, we conduct extensive experiments considering three SOTA classifiers along the weaker learners used in previous investigations. Additionally, we carefully discern proper metrics, consistent and non-consistent algorithms and hyper-parameter selection methods and show that these have a significant impact on prediction quality and on the effectiveness of balancing. Our results support the known utility of balancing for weak classifiers. However, we find that balancing does not improve prediction performance for the strong ones. We further identify several other scenarios for which balancing is effective and observe that prior studies demonstrated the utility of balancing by focusing on these settings.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2201.08528")
get_code_for_paper("2201.08528")
have("2201.08528")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2201.08528.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2201.08528.svg)](https://syntology.ai/paper/2201.08528)

Connect an agent — have() is free.