The technical report for your group should be between 10 and 12 pages long. It is intended to provide information on the design and implementation of your robot which will be useful to someone assessing your work and judging the quality of your robot. Your report must state which of the pre-existing solutions you started with, and go on to explain the motivation and nature of the changes you made to that solution. All the choices that you have made during the design and implementation should be explained and justified. Each of the components of your robot (hardware, vision, strategy, etc.) should be described.
The hardware and software architecture should be presented (diagrams will be useful here). You should include sufficient background material (for example about software libraries etc) for the reader to appreciate what is your own work and how you have used available resources. Only the final version of anything needs to be thoroughly documented: you should discuss abandoned or superseded components or approaches only sufficiently to explain why you moved on.
Within the report you should also describe how you managed integration of different components, within your group and within your team. Similarly your approach to testing should be described.
Since the technical report will be completed after the final day, you should include a section in which you take stock of how well your robot performed on the day, and explain what lessons you have learned, what you would do differently if you were starting again.
You are encouraged to include diagrams and tables in your report in order to make things clear, rather than just use textual descriptions. Reports may contain appendices beyond the strict page limits but markers are not required to read these appendices and in any case you advised to use them sparingly. Large illustrations and references will not count towards the page limits.
The deadline for the technical report is 4pm on Wednesday 19th April. These two documents should be submitted electronically by one group member using the submit command:
submit sdp 9 [filename]
where [filename] is the name of your technical report file; the filename must be group-[g]-technical.pdf, where [g] is the group number.
Both reports should be submitted by a group member nominated for this purpose, and notified to the group mentor at the time of submission.
The technical reports will contribute 20% of the marks for the course, and will be marked out of 20.
The marking will be based on the following elements:
Return to the course webpage.
Informatics Forum, 10 Crichton Street, Edinburgh, EH8 9AB, Scotland, UK
Tel: +44 131 651 5661, Fax: +44 131 651 1426, E-mail: firstname.lastname@example.org
Please contact our webadmin with any comments or corrections. Logging and Cookies
Unless explicitly stated otherwise, all material is copyright © The University of Edinburgh