SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2605.09696 · 2026

Discovery of Nonlinear Dynamics with Automated Basis Function Generation

Charles Nicholson, Mohammad Basiri

arXiv · PDF · Open in the Atlas

Code that ran

2 of 2 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 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; 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/2605.09696.json · badge: /api/ran/2605.09696.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
mabasiri95/AutoSINDy canonical (classifier label)
classifier basis: census
2 ran · 0 no recorded run
FunctionStatusWhere it lives
calculate_complexity_metrics Ran
ran; our contract draft was wrong, not the code
mabasiri95/AutoSINDy/AutoSINDy.py
code served (permissive licence) · get_code("24579415d3f7aa42")
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 dict. 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 sympy
import numpy as np

class MockSINDyModel:
    """Mock SINDy model with coefficients and feature names"""
    def __init__(self):
        self._coefficients = np.array([[1.5, 2.0, -0.5], [0.0, 1.0, 0.3]])
        self._features = ['x0', 'x0*x1', 'x1']
    
    def coefficients(self):
        return self._coefficients
    
    def get_feature_names(self):
        return self._features


class MockPySRModel:
    """Mock PySR model with equations"""
    def __init__(self):
        self.equations_ = True
    
    def get_best(self):
        return {'sympy_format': 'x0**2 + 2*x0*x1 + x1'}


class MockEnsembleModel:
    """Mock ensemble model with multiple sub-models"""
    def __init__(self):
        self.models = [MockSINDyModel(), MockSINDyModel()]


def create_test_model():
    """Create a test model that will be passed to the function"""
    return MockSINDyModel()


ARGS = {
    'model': create_test_model()
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, sympy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type dict — a dict output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a dict output the recorded ndim 0 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
split_data Ran
ran; our contract draft was wrong, not the code
mabasiri95/AutoSINDy/AutoSINDy.py
code served (permissive licence) · get_code("db11c92c5d7da114")
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 tuple. 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 numpy as np

# Create sample trajectory data
n_samples = 100
n_states = 4

# Generate synthetic trajectory data
t = np.linspace(0, 10, n_samples)
X = np.sin(np.arange(n_samples).reshape(-1, 1) * 0.1) * np.ones((n_samples, n_states))
X_dot = np.cos(np.arange(n_samples).reshape(-1, 1) * 0.1) * np.ones((n_samples, n_states))

train_ratio = 0.8
strategy = 'end'

ARGS = {
    'X': X,
    'X_dot': X_dot,
    't': t,
    'train_ratio': train_ratio,
    'strategy': strategy,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple output has no array shape of its own; none is 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 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 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 2 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

Discovering governing equations from observational data remains a fundamental challenge in scientific modeling, particularly when the underlying mathematical structure is unknown. Traditional sparse identification methods like SINDy excel at discovering parsimonious models but require researchers to specify candidate basis functions a priori, a limitation that often leads to model failure when critical terms are omitted or when systems exhibit unconventional dynamics. Purely symbolic regression approaches offer unlimited flexibility but struggle with noise sensitivity and frequently produce overly complex, unstable equations. We present AutoSINDy, a hybrid Discovery-then-Solve framework that combines the exploratory power of symbolic regression with the robust sparsity-promoting capabilities of SINDy. Our method operates in three stages: (1) PySR-based symbolic regression discovers candidate functional forms from bootstrapped data chunks; (2) a curation pipeline decomposes, expands, and filters these expressions using collinearity analysis to construct a minimal yet comprehensive library; and (3) SINDy identifies sparse governing equations from this custom-tailored library. Extensive experiments across canonical nonlinear systems (oscillatory, chaotic, etc.) demonstrate that AutoSINDy consistently recovers groundtruth equations even under high observational noise, achieving a ground-truth recovery rate of 92.8% across all trials. Compared with standard SINDy using enriched libraries and standalone symbolic regression, AutoSINDy achieves higher predictive accuracy, superior generalization to unseen trajectories, and substantially lower symbolic complexity. These results show that Au-toSINDy successfully identifies correct governing terms without prior domain knowledge, effectively automating the feature-engineering bottleneck in system identification and offering a scalable pathway for discovering complex dynamics in biological and physical systems where the mathematical form is unknown.

For agents

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

get_harvested_code_for_paper("2605.09696")
get_code_for_paper("2605.09696")
have("2605.09696")

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

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

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

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

Connect an agent — have() is free.