Coursework – Python – MDP Solver Pacman 5 How your work will be marked There will be six components of the mark for your work: (A) Functionality We will test your code by running your .py _le against...

Need help with the assignment, would like someone to create a "creative" solution as more marks are awarded to "Creative" ideas. Need code commented well so that when I go through it I can understand it.


Coursework – Python – MDP Solver Pacman 5 How your work will be marked There will be six components of the mark for your work: (A) Functionality We will test your code by running your .py _le against a clean copy of pacman-cw2. As discussed above, for full marks for functionality, your code is required to: (a) Be able to win four games out of ten in smallGrid This will be assessed running your code with the command: python pacman.py -n 10 -q -p MDPAgent -l smallGrid and checking to see if it wins at least four games. (b) Be able to win two games out of ten in mediumClassic This will be assessed by running your code with the command: python pacman.py -n 10 -q -p MDPAgent -l mediumClassic and checking to see if it wins at least two games. Since we will check it this way, you may want to reset any internal state in your agent using final() (see Section ??). Partial credit will be given for code that fails to meet these requirements. Since we have a lot of coursework to mark, we will limit how long your code has to demonstrate that it can win. We will terminate the run of the 10 smallGrid games after 2 minutes, and will terminate the run of the 10 mediumClassic games after 5 minutes. If your code has failed to win enough games within these times, we will mark it as if it lost. Note that we will use the -q command, which runs Pacman without the interface, to speed things up. Code not written in Python will not be marked. (b) Style There are no particular requirements on the way that your code is structured, but it should follow standard good practice in software development and will be marked accordingly. Remember that your code is only allowed to interact with the Pacman environment through version 5 of api.py. Code that does not follow this rule will lose marks. (c) Documentation All good code is well documented, and your work will be partly assessed by the comments you provide in your code. If we cannot understand from the comments what your code does, then you will lose marks. (d) Report The contents of the report are described above. Your work will be assessed against the criteria laid out there. The report must be submitted as a PDF document. (e) Results In addition to looking at your experimental results to assess the functionality of your code, we will be looking to check that you did some evaluation, that you analysed the data as required, and that you have drawn sensible conclusions from the experiments. Proper statistical analysis will be credited. (f) Creativity In order to give credit to students who come up with particularly beautiful, sophisticated and/or creative solutions, there will be some marks available to recognise solutions that go beyond the average. As with all instances of creativity, I can't specify what this would, other than to say that we (the markers) will know it when we see it. Impress us. And if you want to be sure that we don't miss your creative solutions, make sure your report tells us about them.