Papers › Learning equivariant tensor functions with applications to sparse vector recovery

Learning equivariant tensor functions with applications to sparse vector recovery

3 Jun 2024arXiv:2406.01552archive 2025-07-28

Wilson G. Gregory, Josué Tonelli-Cueto, Nicholas F. Marshall, Andrew S. Lee, Soledad Villar

This work characterizes equivariant polynomial functions from tuples of tensor inputs to tensor outputs. Loosely motivated by physics, we focus on equivariant functions with respect to the diagonal action of the orthogonal group on tensors. We show how to extend this characterization to other linear algebraic groups, including the Lorentz and symplectic groups. Our goal behind these characterizations is to define equivariant machine learning models. In particular, we focus on the sparse vector estimation problem. This problem has been broadly studied in the theoretical computer science literature, and explicit spectral methods, derived by techniques from sum-of-squares, can be shown to recover sparse vectors under certain assumptions. Our numerical results show that the proposed equivariant machine learning models can learn spectral methods that outperform the best theoretically known spectral methods in some regimes. The experiments also suggest that learned spectral methods can solve the problem in settings that have not yet been theoretically analyzed. This is an example of a promising direction in which theory can inform machine learning models and machine learning models could inform theory.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 8 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 3 honoured, 1 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 8 ran (5 with no instrument failure; 3 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 3 of the 8 samples that ran have no recorded date.

wilsongregory/tensorpolynomials officialmentioned in papermentioned on GitHubjaxSyntology: 11 samples, 8 ran (3 instrument-failed) · 3 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 8 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 3 honoured, 1 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
1ran; the contract check could not run
1ran
3unverified

Licence: 0 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from wilsongregory/tensorpolynomials. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

wilsongregory/tensorpolynomials official repository 11 samples, 8 ran (3 instrument-failed) · 3 unverified
GeneralLinear src/tensorpolynomials/ml.py ran · metamorphic tier: deterministic MIT (permissive) · a2b25394881d78d2 · report fixture: returned GeneralLinear · level recorded 2026-09-22
get_patterns src/tensorpolynomials/ml.py ran · honoured contract fingerprinted MIT (permissive) · 2dc0602051429b2b · report fixture: signature k:int/0/int, n:int/0/int · returned list · level recorded 2026-09-22
get_symmetric_patterns src/tensorpolynomials/ml.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · c4521f9abe35a923 · report fixture: signature patterns:list/1/tuple, symmetric_axes:tuple/1/tuple · returned tuple · level recorded 2026-09-22
map_and_loss scripts/sos_spectral.py ran · our draft was wrong MIT (permissive) · 2dad7d3e9ac96f86 · report fixture: signature model:callable/0/?, x:ArrayImpl/3/float, y:ArrayImpl/2/float, aux_data:dict/0/? · returned tuple · level recorded, date not recorded
partitions src/tensorpolynomials/ml.py ran · our draft was wrong MIT (permissive) · abe32879e73b871a · report fixture: signature n:int/0/int, k:int/0/int, min_elem:int/0/int · returned generator · level recorded 2026-09-22
reorder_pattern src/tensorpolynomials/ml.py ran · violated contract fingerprinted MIT (permissive) · c07cf93b55480f2d · report fixture: signature pattern:ndarray/1/int · returned ndarray · level recorded 2026-09-22
sos_method src/tensorpolynomials/models.py ran · honoured contract fingerprinted MIT (permissive) · c64048d649037766 · report fixture: signature S:ArrayImpl/2/float · returned ArrayImpl · level recorded, date not recorded
sos_methodII src/tensorpolynomials/models.py ran · honoured contract fingerprinted MIT (permissive) · b14d386d5c18e44c · report fixture: signature S:ArrayImpl/2/float · returned ArrayImpl · level recorded, date not recorded
PermEquivariantLayer src/tensorpolynomials/ml.py unverified MIT (permissive) · 9573c20df0f9b5e0 · report
PermInvariantTensor src/tensorpolynomials/ml.py unverified MIT (permissive) · 1bad12d82c05605f · report
tensor_from_pattern src/tensorpolynomials/ml.py unverified MIT (permissive) · 5acafa1378b5dea8 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for equivariant machine learning architectures on tensors (graph method: equivariant machine learning architectures on tensors). 8 bricks; individually on a fixture: 5 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 1 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. PermEquivariantLayer entry · level 0 · unverified · 9573c20df0f9b5e0
  2. GeneralLinear model · level 1 · ran · a2b25394881d78d2
  3. PermInvariantTensor helper · level 0 · unverified · 1bad12d82c05605f
  4. get_patterns helper · level 1 · ran · honoured contract · 2dc0602051429b2b
  5. get_symmetric_patterns helper · level 1 · ran; the contract check could not run (RAISES) · c4521f9abe35a923
  6. tensor_from_pattern helper · level 0 · unverified · 5acafa1378b5dea8
  7. partitions helper · level 1 · ran · our draft was wrong · abe32879e73b871a
  8. reorder_pattern helper · level 1 · ran · violated contract · c07cf93b55480f2d

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2406.01552") returns these assemblies with each brick's role and wiring (how to connect).

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Focus

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