Papers › Competitive Gradient Descent

Competitive Gradient Descent

28 May 2019NeurIPS 2019 12arXiv:1905.12103archive 2025-07-28

Florian Schäfer, Anima Anandkumar

We introduce a new algorithm for the numerical computation of Nash equilibria of competitive two-player games. Our method is a natural generalization of gradient descent to the two-player setting where the update is given by the Nash equilibrium of a regularized bilinear local approximation of the underlying game. It avoids oscillatory and divergent behaviors seen in alternating gradient descent. Using numerical experiments and rigorous analysis, we provide a detailed comparison to methods based on \emph{optimism} and \emph{consensus} and show that our method avoids making any unnecessary changes to the gradient dynamics while achieving exponential (local) convergence for (locally) convex-concave zero sum games. Convergence and stability properties of our method are robust to strong interactions between the players, without adapting the stepsize, which is not the case with previous methods. In our numerical experiments on non-convex-concave problems, existing methods are prone to divergence and instability due to their sensitivity to interactions among the players, whereas we never observe divergence of our algorithm. The ability to choose larger stepsizes furthermore allows our algorithm to achieve faster convergence, as measured by the number of model evaluations.

PaperPDFConference PDFCodeCode Syntology ran

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

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1905.12103")

Code

Syntology Ran 3 of 5 code samples harvested from 3 repositories linked to this paper; 2 have no recorded run. Of those that ran: 3 ran · our draft was wrong.

By repository: community (archive-listed): 5 samples from 3 repositories, 3 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

f-t-s/CGD officialmentioned in papermentioned on GitHubpytorchMIT report
18jeffreyma/cgd_scratch_work mentioned on GitHubpytorch report
18jeffreyma/multi_cmd mentioned on GitHubpytorch report
devzhk/Implicit-Competitive-Regularization mentioned on GitHubpytorchApache-2.0 report
devzhk/cgds-package mentioned on GitHubpytorch report
gehring/fax mentioned on GitHubjax report
wagenaartje/torch-cgd mentioned on GitHubpytorchMIT 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

5 samples harvested; 3 ran; 0 honoured the contract we drafted; 2 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

3ran · our draft was wrong
2unverified

Licence: 1 of the 5 samples is 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 3 repositories linked to this paper, official or community; each sample names its own and says which. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

CG devzhk/cgds-package/src/CGDs/cg_torch.py community (archive-listed) ran · our draft was wrong MIT (permissive) · 135ab19db3580e2d · report
make_mixed_hessian gehring/fax/fax/competitive/cga.py community (archive-listed) ran · our draft was wrong MIT (permissive) · c00f52f3b0258f87 · report
make_mixed_jvp gehring/fax/fax/competitive/cga.py community (archive-listed) ran · our draft was wrong MIT (permissive) · 142c34c0c504b5a5 · report
cg_fixed_point_solve gehring/fax/fax/competitive/cga.py community (archive-listed) unverified MIT (permissive) · af4ef0837095e7f3 · report
player_payoffs 18jeffreyma/multi_cmd/notebooks/how_to_use_optim.py community (archive-listed) unverified no licence file found · pointer only · 75d97d1a4dc46d3f · report

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