Papers › Modelling Behavioural Diversity for Learning in Open-Ended Games

Modelling Behavioural Diversity for Learning in Open-Ended Games

14 Mar 2021arXiv:2103.07927archive 2025-07-28

Nicolas Perez Nieves, Yaodong Yang, Oliver Slumbers, David Henry Mguni, Ying Wen, Jun Wang

Promoting behavioural diversity is critical for solving games with non-transitive dynamics where strategic cycles exist, and there is no consistent winner (e.g., Rock-Paper-Scissors). Yet, there is a lack of rigorous treatment for defining diversity and constructing diversity-aware learning dynamics. In this work, we offer a geometric interpretation of behavioural diversity in games and introduce a novel diversity metric based on determinantal point processes (DPP). By incorporating the diversity metric into best-response dynamics, we develop diverse fictitious play and diverse policy-space response oracle for solving normal-form games and open-ended games. We prove the uniqueness of the diverse best response and the convergence of our algorithms on two-player games. Importantly, we show that maximising the DPP-based diversity metric guarantees to enlarge the gamescape -- convex polytopes spanned by agents' mixtures of strategies. To validate our diversity-aware solvers, we test on tens of games that show strong non-transitivity. Results suggest that our methods achieve at least the same, and in most games, lower exploitability than PSRO solvers by finding effective and diverse strategies.

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

By repository: named in the paper: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 7 samples from 1 repository, 7 ran (1 with no instrument failure; 6 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.

diversepsro/diverse_psro mentioned in paperpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
oslumbers/diverse-psro mentioned in paperpytorchSyntology: not harvested report
sjtu-marl/bd_rd_psro mentioned on GitHubpytorchSyntology: 7 samples, 7 ran (6 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

8 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 7 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.

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

Licence: 8 of the 8 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

diversepsro/diverse_psro named in the paper 1 sample, 1 ran (1 instrument-failed) · 0 unverified
gradient_loss_update_rectified non_mixture_model.py ran · our draft was wrong no licence file found · pointer only · 8f8dde5e49ed3949 · report fixture: signature torch_pop:TorchPop/0/?, k:int/0/int, weights:list/1/float, train_iters:int/0/int, lr:float/0/float · returned tuple · level recorded 2026-09-22
sjtu-marl/bd_rd_psro community (archive-listed) 7 samples, 7 ran (6 instrument-failed) · 0 unverified
distance_solver non_mixture_model.py ran · honoured contract fingerprinted no licence file found · pointer only · 89a0c3309350975e · report fixture: signature A:ndarray/2/float, b:Tensor/2/float · returned Tensor · level recorded 2026-09-22
fictitious_play spinning_tops_dpp.py ran · our draft was wrong no licence file found · pointer only · bb0cee34530e3448 · report fixture: signature iters:int/0/int, payoffs:ndarray/2/float, verbose:bool/0/bool · returned tuple · level recorded 2026-09-22
fictitious_play analyze_gauss.py ran · our draft was wrong no licence file found · pointer only · 1209c10396c7231f · report fixture: signature iters:int/0/int, payoffs:ndarray/2/float, verbose:bool/0/bool · returned tuple · level recorded 2026-09-22
fp_for_non_symmetric_game analyze_gauss.py ran · our draft was wrong fingerprinted no licence file found · pointer only · ec874bbd57842813 · report fixture: signature emp_game_matrix:ndarray/2/float, iters:int/0/int · returned tuple · level recorded 2026-09-22
get_br_to_strat spinning_tops_dpp.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · c0c29a0be57cf876 · report fixture: signature strat:ndarray/2/float, payoffs:ndarray/2/float, verbose:bool/0/bool · returned ndarray · level recorded 2026-09-22
get_br_to_strat analyze_gauss.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · 9591eb5c446df450 · report fixture: signature strat:ndarray/1/float, payoffs:ndarray/2/float, verbose:bool/0/bool · returned ndarray · level recorded 2026-09-22
get_exploitability spinning_tops_dpp.py ran · our draft was wrong no licence file found · pointer only · d860f0ba9aa6810b · report fixture: signature pop:ndarray/2/float, payoffs:ndarray/2/float, iters:int/0/int · returned float64 · level recorded 2026-09-22

Tasks

DiversityPoint Processes

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