Project Report : Grail Simulation

Project Report : Grail Simulation

Name:

Student Number:

Date:

Overview

Describe your program's purpose and implemented features.

User Guide

Instructions on how to use your simulation setup, required packages, code usage (and parameter sweep code usage, if applicable)

Traceability Matrix

Table giving overview of features, and the implementation and testing of your code. Example below.

Feature - numbered for easy referencing

Code reference reference to files/classes/methods or snippets of code only, do not put the whole program in the report OR Not Implemented

Test reference test code or describe how you tested your feature, N/A if not implemented

Status P = passed tests, S = skipped, F = failed, or N/A

Date Completed date or Ongoing or N/A if not implemented

Feature Code Reference Test Reference Status Date Completed

1.0 Creatures (example) 1.1 Newts Class Newt in creatures.py testNewt.py 4/2/24

1.1.1 Newts are plotted as blue circles plot_me() method in Newt class testNewt.py plotting test section P 4/2/24

1.1.2 Newts move towards water step_change() method in Newt class, #1.1.2 ref in code testNewt.py movement test section P 4/2/24

1.2 Witches (Example) Class Witch in creatures.py testWitch.py 4/2/24

1.2.1 Plotted as black circles plot_me() method in Witch class PASSED - plotting test section P 4/2/24

1.2.2 Move with Moore neighbourhood, and can teleport anywhere step_change() method in Witch class, lines 5-8 for 10% chance of teleporting PASSED - movement test section P 4/2/24

1.3 Knights (Example) Not Implemented N/A N/A N/A

2.0 Behaviours (Example) 2.1 Witches turn Knights into Newts interactions() function in grail_sim.py, #2.1 code ref test_interactions.py, #2.1 code ref Ongoing

2.2 Newted Peasants get better step_change() method in Newt class, #2.2 ref in code - recover after 5 timesteps testNewt.py #2.2 code ref P 5/2/24

Discussion

Discussion of implemented features (referring to the Traceability Matrix), explaining how they work and how you implemented them. A UML Class Diagram should be included for objects and their relationships.

Showcase

Discussion and demonstration of code output, including three different scenarios different settings, numbers of items, strategies etc.

In this Introduction, describe how you have chosen to set up and compare the simulations for the showcase. Include commands, input files anything needed to reproduce your results.

Scenario 1

Show and discuss the scenarios outputs/results.

Scenario 2

Show and discuss the scenarios outputs/results.

Scenario 3

Show and discuss the scenarios outputs/results.

Conclusion

Reflection on your assignment with respect to the specification

Future Work

Further investigations and/or extensions that could follow.

References

Use Chicago 17th Author-Date, refs in alphabetical order

COMP1005. Fundamentals of Programming: Lecture 5. Accessed May 4th, 2024 via Blackboard

[then cite as (COMP1005, 2024) or COMP1005 (2024)]

COMP1005a. Fundamentals of Programming: Practical 5, Activity 6. Accessed May 4th, 2024 via Blackboard

[if multiple with same author/year]

Curtin University. Chicago 17th Author-Date. Accessed February 4th, 2024. https://uniskills.library.curtin.edu.au/referencing/chicago17/introduction/