Papers › A Generalized EigenGame with Extensions to Multiview Representation Learning

A Generalized EigenGame with Extensions to Multiview Representation Learning

21 Nov 2022arXiv:2211.11323archive 2025-07-28

James Chapman, Ana Lawry Aguila, Lennie Wells

Generalized Eigenvalue Problems (GEPs) encompass a range of interesting dimensionality reduction methods. Development of efficient stochastic approaches to these problems would allow them to scale to larger datasets. Canonical Correlation Analysis (CCA) is one example of a GEP for dimensionality reduction which has found extensive use in problems with two or more views of the data. Deep learning extensions of CCA require large mini-batch sizes, and therefore large memory consumption, in the stochastic setting to achieve good performance and this has limited its application in practice. Inspired by the Generalized Hebbian Algorithm, we develop an approach to solving stochastic GEPs in which all constraints are softly enforced by Lagrange multipliers. Then by considering the integral of this Lagrangian function, its pseudo-utility, and inspired by recent formulations of Principal Components Analysis and GEPs as games with differentiable utilities, we develop a game-theory inspired approach to solving GEPs. We show that our approaches share much of the theoretical grounding of the previous Hebbian and game theoretic approaches for the linear case but our method permits extension to general function approximators like neural networks for certain GEPs for dimensionality reduction including CCA which means our method can be used for deep multiview representation learning. We demonstrate the effectiveness of our method for solving GEPs in the stochastic setting using canonical multiview datasets and demonstrate state-of-the-art performance for optimizing Deep CCA.

PaperPDFCodeCode Syntology ran

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 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 9 samples from 1 repository, 9 ran (9 with no instrument failure; 0 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

jameschapman19/cca_zoo jaxSyntology: 9 samples, 9 ran (0 instrument-failed) · 0 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

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 0 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.

9ran

Licence: 0 of the 9 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 jameschapman19/cca_zoo. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

jameschapman19/cca_zoo community (archive-listed) 9 samples, 9 ran (0 instrument-failed) · 0 unverified
ey_cross_covariance cca_zoo/_utils/_ey.py ran MIT (permissive) · 3393b769827b0aa7 · report fixture: signature representations:list/1/ndarray · returned tuple · level recorded 2026-09-25
ey_loss cca_zoo/_utils/_ey.py ran MIT (permissive) · 1665525b2f463810 · report fixture: signature representations:list/1/ndarray · returned dict · level recorded 2026-09-25
gevp cca_zoo/_utils/_linalg.py ran MIT (permissive) · 2482d8594a6697e8 · report fixture: signature A:ndarray/2/float, B:ndarray/2/float, k:int/0/int · returned tuple · level recorded 2026-09-25
perview_parameter cca_zoo/_utils/_validation.py ran MIT (permissive) · a8305f3ef2d757e2 · report fixture: signature name:str/0/str, value:int/0/int, default:int/0/int, n_views:int/0/int · returned list · level recorded 2026-09-25
procrustes_rotation cca_zoo/model_selection/_significance.py ran fingerprinted MIT (permissive) · 6d626058314ed66b · report fixture: signature reference:ndarray/2/float, target:ndarray/2/float · returned ndarray · level recorded 2026-09-25
soft_threshold in 12 papers
census: 4 implementations from 5 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
cca_zoo/_utils/_linalg.py ran fingerprinted MIT (permissive) · 21818c213b2a1315 · report fixture: signature x:ndarray/2/float, threshold:float/0/float · returned ndarray · level recorded 2026-09-25
svd_whiten cca_zoo/_utils/_linalg.py ran fingerprinted MIT (permissive) · 530564192d143f96 · report fixture: signature X:ndarray/2/float, regularization:float/0/float · returned tuple · level recorded 2026-09-25
validate_views cca_zoo/_utils/_validation.py ran MIT (permissive) · 9d12d25978185086 · report fixture: signature views:list/1/ndarray, min_views:int/0/int, ensure_all_finite:bool/0/bool · returned list · level recorded 2026-09-25
weight_gram_mean cca_zoo/_utils/_ey.py ran MIT (permissive) · 910ca463740e6918 · report fixture: signature weights:list/1/ndarray · returned ndarray · level recorded 2026-09-25

Tasks

Dimensionality ReductionRepresentation Learning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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