 |
.. (לתיקייה המכילה) | |
Can you add functionality X? | |
|
No. If you need a certain functionality you should implement it yourselves. Changes of the supplied code will be issued only for bug fixes. |
What can we import? | |
You can import and use the following code:
You may not assume any other code (particularly code from alpha_beta.py) exists in the environment where your code will be run. |
How should we arrange our code? | |
|
Your agent (implements GameAgent) should be in the file agent.py. All your other code can reside in files and classes named to your liking, obviously avoiding name clashes with code from game_agent.py, game.py and loa_game.py. All your code should assume flat hierarchy (all files reside in the same directory). |
What code should we submit? | |
|
You should submit all the files that your code uses, and none of the files that were provided to you for this assignment. Therefore, if you changed say LinesOfActionState and would like to use your version, you should store your code in a class and file of a different name than any file/class provided. |
What can we assume on the agent setup time? | |
| You can assume it will be in the range of [0.1 .. 20] seconds. |
How should we test memory usage? | |
|
You should test your player against a 0 memory player (such as the random player), and see that your memory usage in a game with reasonable parameters (e.g. the default parameters) doesn't exceed 1GB. This should be fairly easy to achieve unless you store huge amounts of data for e.g. transposition tables. You can test your player's memory usage through system tools such as the Windows's Task Manager or Linux's top command. Search for the python process of your player. If you want to test your player's memory usage from inside the process, you can try the psutil library available here: http://code.google.com/p/psutil/ Don't spend too much time on this issue. Unless you do something wrong you are most likely not going to be even close to 1GB memory usage in a normal game. |