Axelrod
Axelrod copied to clipboard
A research tool for the Iterated Prisoner's Dilemma
Now that we're Python 3.5+ exclusive, it's time for [type hints](https://docs.python.org/3/library/typing.html)! Note to contributors: please run mypy on any newly annotated files. After installing with `pip install mypy`, please run:...
Each of the of the original strategies from [Axelrod's second tournament](http://axelrod.readthedocs.io/en/stable/reference/overview_of_strategies.html#axelrod-s-second-tournament) needs to be reverse engineered and an issue created for each which describes its operation. - [x] [GRASR](https://github.com/Axelrod-Python/TourExec/blob/v0.3.0/src/strategies/grasr.f) -...
EDIT: This issue is no longer about the strategy described below. It now corresponds to an implementation of a Fortran strategy. ~~This strategy is one of the strategies from Axelrod's...
Function stack based strategies from "Ashlock, Daniel. "Training function stacks to play the iterated prisoner's dilemma." Computational Intelligence and Games, 2006 IEEE Symposium on. IEEE, 2006."
This is one of the strategies from [Axelrod's Second Tournament](http://axelrod.readthedocs.io/en/stable/reference/overview_of_strategies.html#axelrod-s-second-tournament) for which we have the [orginal Fortran code](https://github.com/Axelrod-Python/TourExec/blob/v0.3.0/src/strategies/k91r.f). A description of this strategy is given in Axelrod, R. (1980). More...
- [x] Replace the inline tables with csv_tables - [x] Replace the :code: directives with :class: directives - [ ] Remove the text descriptions of each strategy (ensuring that the...
Binary decision strategies defined in "Varying Decision Inputs in Prisoner’s Dilemma", Barlow and Ashlock 2015
It would be nice to be able to define and execute an external configuration file for running a tournament (not in python), something like: ``` [strategies] Random, 0.4 TitForTat ......
@marcharper found a bug in mypy but this has now been patched: https://github.com/python/mypy/pull/2786 This bug currently stops us from type checking the whole library (as some modules don't play nice)...
Currently we manually update various components post release, such as running new tournaments in the tournament repository. It would be great if we had a script that we could run...