QuantEcon / QuantEcon/QuantEcon.py
Suggestions on the organization of game theory subpackage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.4k
- Forks
- 2.3k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 3
Description
We can think the game theory as the game forms. There are two main forms: normal form and extensive form. We can define two class for two forms. Then we provide a transformation between two forms. Then we can define the players, actions, payoffs, information and equilibrium concepts. The calculation of equilibrium can be defined by function and then make it into the class so that we can use it as a function or a instance method. For example,
# games/normal.py
class NormalGame(object):
pass
# games/extensive.py
class ExtensiveGame(object):
pass
# games/player.py
class Player(object):
pass
# games/equilibrium.py
def pure_nash():
pass
def mixed_nash():
pass
# games/__init__.py
from ..normal import NormalGame
from ..extensive import ExtensiveGame
from ..equilibrium import pure_nash, mixed_nash
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed games/normal.py, games/extensive.py, games/player.py, games/equilibrium.py, and games/init.py layout. The issue does not identify existing entry points or tests; work is only complete once the subpackage organization and scope for forms, players, payoffs, and equilibrium functions are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100