Assignment (INFO1110)
Introduction
The assignment is an individual assessment. It contributes 30% of your final marks.
The due date for the assignment is on 9th May 2024, 11:59 pm (Sydney time).
This is an assignment, and staff are not permitted to give guidance on your code or how to solve a specific problem. That is the purpose of the assessment that you are required to perform. to achieve the grade.
You may ask clarification questions about the assignment description. This is often necessary to implement functionality that may need further understanding to complete. If you have a question to ask on Ed, please search before asking. With a cohort of almost 2000 students, chances are that someone has already asked a question you have planned to ask.
Do not wait too long before starting. This assignment needs time and sustained effort.
Remember that you should not be posting any assignment code publicly (including Ed), as this would constitute academic dishonesty.
Submissions
Late submissions are not accepted unless an approved special consideration or special arrangement in the form. of a Simple Extension or Extension of time has been granted. Please inform. staff if you have been granted this.
All submissions must be made via Ed, including any supporting documentation that is produced during the planning of the program design such as flowcharts, pseudocodes, and UML class diagrams.
You may submit as many times before the due date, there is 0 penalty for submitting multiple times. We will use the latest submission received before the due date for marking. Request to grade files and derive marks from a combination of different submissions will not be accepted.
It is your responsibility to check that your submission is complete and it meets the following rules:
The Python programs must be able to compile and run within the Ed environment provided. The Python version that is currently being used on Ed is Python 3.11.8.
Only the files given in the scaffold code will be started by the auto-marker. You are free to write additional python files, but you must implement all functions and classes provided in the scaffold. Ensure that you have submitted these files with the correct file name as given in the questions' scaffold:
board_displayer.py
emitter.py
input_parser.py
laser_circuit.py
mirror.py
photon.py
receiver.py
run.py
sorter.py
Your submission must also include a circuit_for_testing.py and test.py file which will be used for the manual grading process.
All files specified above must include your name, SID, and unikey in the following format (order matters!). A placeholder has been provided at the top of the file in the docstring. Providing incorrect details will cause your submission to fail all test cases.
Name: Xxx Yyy
SID: XXXXXXXXX
Unikey: xxxxXXXX
If you attempt to deceive the auto-grader, obfuscate your code, or do not answer the question by hard coding, 0 marks will be awarded for the question.
Marks
Marks are allocated by the automatic test cases passed for each section, as well as manual grading by your tutor.
Automatic Test Cases (20/30)
Your marks for this component will be based purely on the automatic test cases you pass. There are 3 types of automatic test cases, all contributing to your mark:
Public: The name of these test cases describes what it is testing, and additionally gives you feedback on what you got wrong e.g. incorrect output, incorrect return values from functions, etc. Students can easily see what they got right and wrong.
Hidden: The test case is only named Hidden testcase and does not provide detailed feedback. You will only be able to see if you passed it or not. The idea behind this is to encourage students to carefully read through the assignment description and ensure its reflected in their program.
Private: These tests will only be visible after the deadline. You will not know how many private test cases there are until the assignment is graded and returned.
There are several features for this assignment, with each one having their own marking proportion. As example, the first feature SET-MY-CIRCUIT weighs 25% of the automatic test cases. This means passing all public, hidden and private test cases for this feature gets you 5 out of the 20 marks.
Manual Grading (10/30)
Manual grading will assess the style, layout, and comments, correctness of test case implementation in test.py and your responses in the test_plan.md document. The test.py file will be executed during the marking process. Style. marking is only applied for reasonable attempts, those which have code beyond the initial scaffold and are passing at least some test cases.
The style. guide for this assessment can be found on the official Python website
https://peps.python.org/pep-0008/.
In addition to the official style. guide, you can also refer to these resources:
Code style. guide - Part 1
Code style. guide - Part 2
If there's an issue running the program, the tutor will not be responsible to debug your program, so please ensure it runs as expected before making it your final submission.