SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1906.07906 · 2019

Discovery of Physics from Data: Universal Laws and Discrepancies

arXiv · PDF · Open in the Atlas

Code that ran

10 of 13 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 10 have no contract verdict; 0 failures of our instrument; 3 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/1906.07906.json · badge: /api/ran/1906.07906.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
briandesilva/discovery-of-physics-from-data community (classifier label)
classifier basis not recorded on the link
10 ran · 3 no recorded run
FunctionStatusWhere it lives
append_re_dependent_drag Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/library.py
code served (permissive licence) · get_code("99364b9f102ebcdb")
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 torch
import numpy as np

# First, we need to define the reynolds_number function that's called in append_re_dependent_drag
def reynolds_number(v, diameter, k_viscosity):
    """Calculate Reynolds number given velocity, diameter, and viscosity coefficient."""
    # This is a simple stand-in implementation
    return v * diameter / k_viscosity

# Create a small library dict to serve as the input
library = {}

# Define the parameters
diameter = 0.01  # Small diameter value in meters
k_viscosity = 2 / 3  # Default viscosity coefficient

ARGS = {
    'library': library,
    'diameter': diameter,
    'k_viscosity': k_viscosity
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — 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
differentiate Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/differentiation.py
code served (permissive licence) · get_code("21c98ad537e99057")
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 ndarray, ndim 2, dtype family float, shape (3, 10) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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 data for differentiation
# X can be 1D or 2D array
# Using 2D array: 3 variables (rows) x 10 time points (columns)
X = np.array([
    [1.0, 1.5, 2.1, 2.8, 3.5, 4.2, 4.9, 5.6, 6.3, 7.0],
    [0.5, 1.0, 1.6, 2.3, 3.1, 3.9, 4.8, 5.7, 6.7, 7.8],
    [2.0, 2.2, 2.5, 2.9, 3.4, 4.0, 4.7, 5.5, 6.4, 7.4]
], dtype=np.float64)

# Time parameter - can be scalar or array
t_scalar = 0.1  # uniform time step
t_array = np.linspace(0, 0.9, 10)  # non-uniform time points

ARGS = {
    'X': X,
    't': t_scalar,
    'diff_method': 'forward difference',
    'smoother': 'savgol',
    'window_length': 5
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, scipy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 2, dtype family float, shape (3, 10) — shape (3, 10) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
forward_difference Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/differentiation.py
code served (permissive licence) · get_code("f8ef8adf92381a9a")
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 ndarray, ndim 1, dtype family float, shape (5,) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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

# Case 1: 1D array with scalar t
X_1d = np.array([1.0, 2.0, 3.0, 4.0, 5.0])
t_scalar = 1

# Case 2: 1D array with array t
X_1d_arr_t = np.array([1.0, 2.0, 3.0, 4.0, 5.0])
t_array = np.array([0.0, 0.5, 1.2, 1.8, 2.5])

# Case 3: 2D array with scalar t
X_2d = np.array([
    [1.0, 2.0, 3.0, 4.0],
    [2.0, 3.0, 4.0, 5.0]
])
t_scalar_2d = 1.0

# Case 4: 2D array with array t
X_2d_arr_t = np.array([
    [1.0, 2.0, 3.0, 4.0],
    [2.0, 3.0, 4.0, 5.0]
])
t_array_2d = np.array([0.0, 0.5, 1.2, 1.8])

# Use case 1 as the primary test case
ARGS = {
    "X": X_1d,
    "t": t_scalar
}
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 ndarray, ndim 1, dtype family float, shape (5,) — shape (5,) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
get_library Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/library.py
code served (permissive licence) · get_code("eb129eac7eab60f4")
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 numpy as np

ARGS = {
    'lib_type': 'polynomial',
    'order': 3
}
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 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
get_library_index Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/library.py
code served (permissive licence) · get_code("3d2fc04eec6bec97")
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 int, ndim 0, dtype family int, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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 torch
import torch.nn as nn

torch.manual_seed(0)

# The function iterates over library.keys() and compares names with label
# So library needs to be a dict-like object with keys() method
# label needs to be a string to compare with the keys

library = {
    "function_a": lambda x: x,
    "function_b": lambda x: x * 2,
    "function_c": lambda x: x + 1,
}

label = "function_b"

ARGS = {
    "library": library,
    "label": label,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type int, ndim 0, dtype family int, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
group_sparse_penalty Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/sindy_ball.py
code served (permissive licence) · get_code("27b3c79246383909")
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 ndarray, ndim 1, dtype family float, shape (3,) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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

# The function takes a list/sequence of arrays (Xi) that get stacked into a 2D array
# where rows represent groups. Let's create a small example.

# Create a list of 1D arrays that will be stacked as columns
# After stacking on axis=1, we'll have shape (num_groups, len(Xi))
Xi = [
    np.array([1.0, 2.0, 3.0]),
    np.array([4.0, 5.0, 0.5]),
    np.array([0.1, 0.2, 0.3])
]

ARGS = {
    'Xi': Xi,
    'method': '2-norm',
    'quantile': None
}
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 ndarray, ndim 1, dtype family float, shape (3,) — shape (3,) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
need_to_clip Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/utils.py
code served (permissive licence) · get_code("6ff96ad883b8f470")
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 int64, ndim 0, dtype family int, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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

ARGS = {
    "t": np.array([0.0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 5.0])
}
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 int64, ndim 0, dtype family int, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
normalize_columns Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/utils.py
code served (permissive licence) · get_code("042df78bb2bdf5bb")
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 a small matrix with distinct dimensions (4 rows, 3 columns)
# This allows us to test column normalization clearly
X = np.array([
    [3.0, 4.0, 0.0],
    [4.0, 0.0, 5.0],
    [0.0, 3.0, 12.0],
    [1.0, 2.0, 1.0]
], dtype=np.float64)

ARGS = {
    "X": X
}
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
smooth_data Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/differentiation.py
code served (permissive licence) · get_code("e16b70f570f33b0e")
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 ndarray, ndim 2, dtype family float, shape (4, 35) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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
from scipy import signal

np.random.seed(0)

# Create test data - 2D array with shape (4, 35)
# This ensures window_length=35 doesn't exceed the last dimension
X = np.random.randn(4, 35).astype(np.float64)

ARGS = {
    'X': X,
    'smoother': 'savgol',
    'window_length': 35
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, scipy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 2, dtype family float, shape (4, 35) — shape (4, 35) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
synthetic_ball_drop Ran
ran on a synthesized input
briandesilva/discovery-of-physics-from-data/code/helpers/utils.py
code served (permissive licence) · get_code("6e0fb112ae66619c")
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, ndim 2, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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
from scipy.integrate import odeint

np.random.seed(0)

ARGS = {
    "accel": -9.81,
    "drag": 0.5,
    "h0": 47.33,
    "timesteps": 49,
    "dt": 1 / 15,
    "noise": 0.1,
    "v2": None,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, scipy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 2, dtype family float — a tuple output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
predict_with_model Not yet run
unverified (harvested, no recorded run)
briandesilva/discovery-of-physics-from-data/code/helpers/tests.py
code served (permissive licence) · get_code("3248c29466176f26")
How it ran

no invocation recorded.

subtract_known_model Not yet run
unverified (harvested, no recorded run)
briandesilva/discovery-of-physics-from-data/code/helpers/tests.py
code served (permissive licence) · get_code("de7056d8f4eea632")
How it ran

no invocation recorded.

test_group_sparsity Not yet run
unverified (harvested, no recorded run)
briandesilva/discovery-of-physics-from-data/code/helpers/tests.py
code served (permissive licence) · get_code("8dc070fa13d771e1")
How it ran

no invocation recorded.

Also present in other papers' code

Of 13 samples lifted from this paper's linked repositories, 13 carry a function identity and 0 do not. Of the 13 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 13 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

Machine learning (ML) and artificial intelligence (AI) algorithms are now being used to automate the discovery of physics principles and governing equations from measurement data alone. However, positing a universal physical law from data is challenging without simultaneously proposing an accompanying discrepancy model to account for the inevitable mismatch between theory and measurements. By revisiting the classic problem of modeling falling objects of different size and mass, we highlight a number of nuanced issues that must be addressed by modern data-driven methods for automated physics discovery. Specifically, we show that measurement noise and complex secondary physical mechanisms, like unsteady fluid drag forces, can obscure the underlying law of gravitation, leading to an erroneous model. We use the sparse identification of nonlinear dynamics (SINDy) method to identify governing equations for real-world measurement data and simulated trajectories. Incorporating into SINDy the assumption that each falling object is governed by a similar physical law is shown to improve the robustness of the learned models, but discrepancies between the predictions and observations persist due to subtleties in drag dynamics. This work highlights the fact that the naive application of ML/AI will generally be insufficient to infer universal physical laws without further modification.

For agents

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

get_harvested_code_for_paper("1906.07906")
get_code_for_paper("1906.07906")
have("1906.07906")

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

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

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

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

Connect an agent — have() is free.