-
Notifications
You must be signed in to change notification settings - Fork 264
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
Introducing meta players #126
Conversation
Yeah, I agree: I don't think these count as cheaters. They're just taking very detailed notes throughout the tournament. |
They also boost the walltime of the tournament... creating more optimization challenges! :) |
Have you seen #125 ? I seem to be having problems with the parallelised version of the tournament now... |
(That's not directly relevant to this PR but just pinging you in case you have the same problem. Heading out the door now but will take a look at this shortly.) |
This is looking nice. How much longer is the run time? Also, could you tweak the contribution guidelines in the docs for the change from |
The whole thing now runs in about 100s on my machine. |
Introducing meta players
Introducing meta players
This abstracts the core of MetaHunter into an abstract MetaPlayer and adds some more involved metaplayers. Depending on the interpretation, these meta players could be regarded as cheaters, since they load other strategies at runtime. They do not, however, modify strategies or run separate tournaments, just record the running scores these strategies would have had in the current game. In princple, the same could be written explicitely without importing the strategies (alhtough it would be much longer). Anyway, these players are not particularly good (I though MetaWinner would do somewhat better, though).