Skip to content
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

Write a manage.py script #32

Closed
drvinceknight opened this issue Feb 22, 2015 · 11 comments
Closed

Write a manage.py script #32

drvinceknight opened this issue Feb 22, 2015 · 11 comments
Assignees

Comments

@drvinceknight
Copy link
Member

As the number of strategies grows: the mathces (or just the random repetitions) can be parallelised (possibly even making use of caching for non stochastic strategies...).

@drvinceknight
Copy link
Member Author

I'm going to incorporate this with a new manage.py script which will run everything:

  • options to run tests
  • options to run in parallel
  • etc?

@langner
Copy link
Member

langner commented Feb 23, 2015

At first glance, caching would be the first things to do to boost performance.

@langner
Copy link
Member

langner commented Feb 24, 2015

See #41 for caching for pairs of deterministic strategies.

@drvinceknight
Copy link
Member Author

Absolutely huge pull request! Amazing! Awesome @langner ! I'll leave this issue open as I still want to parallelise when I get a chance. That does need the overall better manage.py script which I'll get to.

@drvinceknight
Copy link
Member Author

(I am learning a lot of Python from your pull request @langner : very much appreciated).

@drvinceknight drvinceknight changed the title Parallelise running of tournament Write a manage.py script Feb 26, 2015
@drvinceknight drvinceknight self-assigned this Feb 26, 2015
@meatballs
Copy link
Member

Can this one be closed now?

@drvinceknight
Copy link
Member Author

I think I'd still like a manage.py script, which we don't have so that we could move the functionality of run_tournament and include options like:

manage.py test

actually that's the only extra thing I'd want in there that I can think off.. Perhaps not needed?

@meatballs
Copy link
Member

why not just add any additional functionality as methods in the TournamentManager class? Makes them much easier to test.

@drvinceknight
Copy link
Member Author

Does it make sense to have run tests in there? I think that's the only
extra thing really needed which I'm now not sure warrants it... Although I
guess could be nice...

On Mon, Mar 23, 2015 at 8:33 AM Owen Campbell notifications@github.com
wrote:

why not just add any additional functionality as methods in the
TournamentManager class? Makes them much easier to test.


Reply to this email directly or view it on GitHub
https://github.com/drvinceknight/Axelrod/issues/32#issuecomment-84884756
.

@meatballs
Copy link
Member

Probably doesn't make much sense. Anyone who knows enough to want to run the tests is going to be perfectly capable of typing the command to do so. Running tests from within TournamentManager would actually require more typing!

@drvinceknight
Copy link
Member Author

Yeah... Cool. Let's scrap this.

On Mon, Mar 23, 2015 at 10:47 AM Owen Campbell notifications@github.com
wrote:

Probably doesn't make much sense. Anyone who knows enough to want to run
the tests is going to be perfectly capable of typing the command to do so.
Running tests from within TournamentManager would actually require more
typing!


Reply to this email directly or view it on GitHub
https://github.com/drvinceknight/Axelrod/issues/32#issuecomment-84942451
.

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

No branches or pull requests

3 participants