MTRN4110 Phase B Marking Script

This is the marking script for Phase B.

Usage

Please note, this installation process is OS-independent, meaning it should work for Windows, OSX and Linux.

1. Download Python from the Python website (yellow button that says “Download Python X"). Doing this will also install an application called IDLE.
2. Go to GitHub and download this repository. Do this by clicking the green button labelled “Code”, then “Download ZIP”. Extract the download to wherever you want.
3. Open IDLE, then go to “File -> Open”. Navigate to the extracted ZIP file and open “main.py”.
4. Once the file is opened, you can run it with “Run -> Run Module”. The script runs our solution with "Map.txt" and compares the answer to what is given in “answer.txt”. Furthermore, “PathPlanFound.txt” should contain your path plan (see Section 3.4).
5. To make the script check your solution, copy and paste the output from Webots into “answer.txt”. Make sure the controller name (e.g. [z1234567_MTRN4110_PhaseB]) prefix is omitted in each line. You can do this with find and replace (replace with an empty value) on your text editor of choice (e.g. Notepad++, VS Code).

Using Git to keep up-to-date

I predict that more issues will be found over the next week. To avoid having to re-download this repository every time a bug is fixed, you can use Git.

1. Download Git and GitHub Desktop.
2. On this repository, go to "Code", then "Open in GitHub Desktop".
3. Follow the instructions on GitHub Desktop to set up the folder for you.
4. Now, you can update the copy of your script on your computer by clicking "Fetch Origin" and "Pull Origin".

Known Bugs

Bug	Status
Final path wasn't added to the get_paths function, taking off marks for a correct answer.	Fixed
Student's PathPlanFound.txt was in a different location to the automarker's repo, giving an error.	Fixed
Linux is not supported - the ./sln is outdated.	Fixed
Current solution file does not support paths of steps > 40.	Fixed

Contribution

If you have found a bug, please message me on Teams. Come back for status updates on known bugs (see above). If you're familiar with GitHub, make a PR - it's a lot easier for me as well!