Grading

Each team executes the same assignment and is therefore involved in a competition to achieve the best result. The course grade is directly dependent on the project result in terms of absolute demonstrator and report quality as well as relative team ranking. Next to team grading, each team member is individually graded depending on the member’s involvement and contribution to the team result. Consequently, a team member grade can differ from the team grade.

As this course is about embedded systems, it is mandatory for each team member to have written some embedded code that runs on the drone.

A better result earns more credits. A result is positively influenced by a good design and good documentation (which presents the design and experimental results). A good design will achieve good stability, use good programming techniques, have bug-free software, demonstrates a modular approach where each module is tested before system-level integration, and therefore adhere to the “first-time-right” principle (with respect to connecting to the real drone).

On the debit side, to avoid lack of progress a design may sometimes require excessive assistance from the Teaching Assistants (consultancy minutes), which will cost credits

This is a group project. In case group collaboration is insufficient, caused by one or multiple members, the work of the members in question will not be evaluated at all. You cannot pass this course without sufficient teamwork.

For more information about how grades are calculated see the Deliverables page.

Note: The final demonstration lab sessions in Week 3.9 are on Monday 7th April, Tuesday 8th April, Wednesday 9th April and Thursday 10th April. The demonstrations take place in the same room as the labs. The deadline for handing in the report and code is Sunday 13th April.