Reporting

The team report, preferably typeset in LaTeX, should contain the following

• Title, team ID, team members, student numbers and date
• Abstract (10 lines, specific approach and results)
• Introduction (including problem statement)
• Architecture (all software components and interfaces)
• Implementation (how you did it, and who did what)
• Experimental results (list capabilities of your demonstrator)
• Conclusion (evaluate design, team results, individual performance, learning experience)
• Appendices (all component interfaces, component code for those components you wish to feature)

Specific items that must be included are a functional block diagram of the overall system architecture, the size of the Rust code, the control speed of the system (control frequency, the latencies of the various blocks within the control loop), and the individual contributions of each team member (no specification = no contribution). The report should be complete but should also be as minimal as possible. In any case, the report must not exceed 10 pages (A4, 11 point), including figures and appendices. Reports that exceed this limit are NOT taken into consideration (i.e., desk-rejected).