Code | Points | Description |
---|---|---|
A1 | 2 | Submission is zip containing 1 python file |
A2 | 2 | Zip is named after uni, unzips to folder with uni-hw3 |
A3 | 3 | Python file has good name |
A4 | 3 | Python file has good style |
Style Points:
main
or runSingleGame
, etc) and make calls to functions that are reuesable in part 2Edge cases:
revealGoats
function runs iteratively, if the user picks the car, N-2 doors should be revealedCode | Points | Description |
---|---|---|
B11 | 2 | User prompted for number of doors |
B12 | 4 | Game state correct for 3 doors |
B13 | 4 | User pick works correctly for 3 doors |
B14 | 4 | Reveal goats works correctly for 3 doors, whether or not user picked car |
B15 | 4 | User switch works correctly for 3 doors |
B16 | 4 | Game state resolved correctly, whether or not user picked car |
B17 | 2 | Play again works |
B2 | 4 | Game works correctly for 2 doors (nothing revealed in reveal goats step) |
B3 | 2 | Game works correctly for 4 doors |
B4 | 10 | Good style |
Style Points:
main
or runSimulationGame
, etc) and make calls to functions that are reuesable from part 1Test cases:
Code | Points | Description |
---|---|---|
C1 | 2 | User prompted for number of simulations |
C2 | 10 | Code produces correct win/loss probability for 2 doors |
C3 | 15 | Code produces correct win/loss probability for 3 doors |
C4 | 15 | Code produces correct win/loss probability for 10 doors |
C5 | 8 | Good Style (No globals, comments, well named vars) |