Skip to content

Expose enummixed's connected components as NashComponent/NashPolytope - #1136

Draft
tturocy wants to merge 1 commit into
masterfrom
dev_components
Draft

Expose enummixed's connected components as NashComponent/NashPolytope#1136
tturocy wants to merge 1 commit into
masterfrom
dev_components

Conversation

@tturocy

@tturocy tturocy commented Sep 10, 2026

Copy link
Copy Markdown
Member

This adds NashPolytope (one maximal clique, genuinely convex) and NashComponent (one or more NashPolytopes glued at a shared vertex, not itself necessarily convex) as view objects, with the grouping computed via a small union-find pass over the existing per-clique vertex-index arrays in EnumMixedStrategySolution. EnumMixedResult.cliques becomes .components, and enummixed_solve's cliques= parameter becomes components=.

This adds NashPolytope (one maximal clique, genuinely convex) and NashComponent
(one or more NashPolytopes glued at a shared vertex, not itself necessarily convex)
as view objects, with the grouping computed via a small union-find pass over the
existing per-clique vertex-index arrays in EnumMixedStrategySolution. EnumMixedResult.cliques
becomes .components, and enummixed_solve's cliques= parameter becomes components=.
@tturocy

tturocy commented Sep 10, 2026

Copy link
Copy Markdown
Member Author

@rahulsavani Here's a marker on this idea. To be discussed/considered:

  1. Whether a hit-test/containment operation should be added to the new polytope objects;
  2. How might we present this in the GUI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant