SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2302.08166 · 2023

Learning Neural Operators on Riemannian Manifolds

arXiv · PDF · Open in the Atlas

Code that ran

2 of 4 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; 1 honoured the contract we drafted, 0 violated it and 1 has no contract verdict; 0 failures of our instrument; 2 no recorded run), measured 2026-11-21; 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/2302.08166.json · badge: /api/ran/2302.08166.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
gengxiangc/norm canonical (classifier label)
classifier basis not recorded on the link
2 ran · 2 no recorded run
FunctionStatusWhere it lives
beltrami_coefficient Ran
ran on a synthesized input
gengxiangc/norm/Case1_DarcyFlow/lapy/Conformal.py
code served (permissive licence) · get_code("18f193c6246a6b8e")
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 (2,) 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

class SimpleMesh:
    """Stand-in class for mesh object with vertices and triangles."""
    def __init__(self, v, t):
        self.v = v  # vertices: (nv, 3)
        self.t = t  # triangles: (nf, 3)

# Create a small planar mesh
# 4 vertices on z=0 plane
vertices = np.array([
    [0.0, 0.0, 0.0],
    [1.0, 0.0, 0.0],
    [1.0, 1.0, 0.0],
    [0.0, 1.0, 0.0],
], dtype=np.float64)

# 2 triangles
triangles = np.array([
    [0, 1, 2],
    [0, 2, 3],
], dtype=np.int32)

tria = SimpleMesh(vertices, triangles)

# Mapping from 2D parameter space to 3D space
# nv=4 vertices, each mapped to (x, y, z)
mapping = np.array([
    [0.0, 0.0, 0.1],
    [1.0, 0.0, 0.2],
    [1.0, 1.0, 0.15],
    [0.0, 1.0, 0.25],
], dtype=np.float64)

ARGS = {
    "tria": tria,
    "mapping": mapping,
}
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 1, dtype family float, shape (2,) — shape (2,) 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
count_params Ran
ran, honoured the contract we drafted
gengxiangc/norm/Case1_DarcyFlow/utils.py
pointer only (licence: MIT); the stored copy get_code serves, from skhetrapal/chaotic-pde-fno, is pointer only (licence: NONE) · get_code("ff22c81e9f140b90")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from skhetrapal/chaotic-pde-fno, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

mobius_area_correction_spherical Not yet run
unverified (harvested, no recorded run)
gengxiangc/norm/Case1_DarcyFlow/lapy/Conformal.py
code served (permissive licence) · get_code("2afed879b5bae7de")
How it ran

no invocation recorded.

spherical_conformal_map Not yet run
unverified (harvested, no recorded run)
gengxiangc/norm/Case1_DarcyFlow/lapy/Conformal.py
code served (permissive licence) · get_code("697f996ea073bd9e")
How it ran

no invocation recorded.

Also present in other papers' code

Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 1 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 1 later) and 3 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.

FunctionAlso present inEarliest-datedOthers named
count_params 5 other papers
1 dated earlier, 4 later
2207.05209 (2022-07)
Fourier Neural Operator with Learned Deformations for PDEs on General Geometries
2312.05583 (2023-12)
Better Neural PDE Solvers Through Data-Free Mesh Movers
2312.06980 (2023-12)
SPFNO: Spectral operator learning for PDEs with Dirichlet and Neumann boundary conditions
and 2 more not named here

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-21.

Repositories linked to this paper

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

Abstract

In Artificial Intelligence (AI) and computational science, learning the mappings between functions (called operators) defined on complex computational domains is a common theoretical challenge. Recently, Neural Operator emerged as a promising framework with a discretisation-independent model structure to break the fixed-dimension limitation of classical deep learning models. However, existing operator learning methods mainly focus on regular computational domains, and many components of these methods rely on Euclidean structural data. In real-life applications, many operator learning problems are related to complex computational domains such as complex surfaces and solids, which are non-Euclidean and widely referred to as Riemannian manifolds. Here, we report a new concept, Neural Operator on Riemannian Manifolds (NORM), which generalises Neural Operator from being limited to Euclidean spaces to being applicable to Riemannian manifolds, and can learn the mapping between functions defined on any real-life complex geometries, while preserving the discretisation-independent model structure. NORM shifts the function-to-function mapping to finite-dimensional mapping in the Laplacian eigenfunctions' subspace of geometry, and holds universal approximation property in learning operators on Riemannian manifolds even with only one fundamental block. The theoretical and experimental analysis prove that NORM is a significant step forward in operator learning and has the potential to solve complex problems in many fields of applications sharing the same nature and theoretical principle.

For agents

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

get_harvested_code_for_paper("2302.08166")
get_code_for_paper("2302.08166")
have("2302.08166")

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

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

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

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

Connect an agent — have() is free.