-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tournament script / config file #421
Comments
YAML is good for that sort of thing and there's a python library to deal with it: http://pyyaml.org/wiki/PyYAML |
This is an awesome idea and also completely agree with @meatballs that we should use yml (have done similar for other projects). |
Great, YAML works for me. |
I'm going to look at this one next. I think this is the way that the API will need to receive definitions of tournaments to be run. |
@erik-sn @meatballs What's the current state of this re: the API? |
@marcharper sorry for the delayed response - the API can sort of do this right now, I just need to do some documentation. Essentially you would POST to I added "sort of" because this does require an HTTP client - using requests in a python script, curl, postman, a browser UI, etc. I will try to work on documenting each of the endpoints soon, I have been distracted by some other stuff I have going on. |
It would be nice to be able to define and execute an external configuration file for running a tournament (not in python), something like:
Then we could do something like
This way we could allow people to use the library without understanding python and also have reusable tournament specifications (for the goal of reproducibility). It would also separate the internal APIs of axelrod from the actual specification of tournaments, and perhaps e.g. ease mapping a webapp to axelrod.
Any thoughts?
The text was updated successfully, but these errors were encountered: