Modified 2018-05-06 by Andrea Censi
The objective of this report is to bring justice to your hard work during the semester and make so that future generations of Duckietown students may take full advantage of it. Some of the sections of this report are repetitions from the preliminary and intermediate design document (PDD, IDD respectively).
Modified 2018-06-25 by Andrea Censi
Let’s start from a teaser.
Add as a caption: see the operation manual to reproduce these results.
Modified 2018-02-17 by TianluWang
Now tell your story:
Define what is your mission here.
Modified 2018-02-17 by TianluWang
Now step back and tell us how you got to that mission.
What are we talking about? [Brief introduction / problem in general terms]
Why is it important? [Relevance]
Modified 2018-02-17 by TianluWang
Modified 2018-02-17 by TianluWang
Examples: - there wasn’t a previous implementation - the previous performance, evaluated according to some specific metrics, was not satisfactory - it was not robust / reliable - somebody told me to do so (/s)
Modified 2018-06-25 by Andrea Censi
Definition of link: - could be the reference to a paper / textbook (check here (unknown ref duckumentation/demo-template) how to add citations) - (bonus points) it is best if it is a link to Duckiebook chapter (in the dedicated “Preliminaries” section)
Modified 2018-02-17 by TianluWang
Up to now it was all fun and giggles. This is the most important part of your report: a crisp mathematical definition of the problem you tackled. You can use part of the preliminary design document to fill this section.
Make sure you include your: - final objective / goal - assumptions made (including contracts with “neighbors”) - quantitative performance metrics to judge the achievement of the goal
Modified 2018-02-17 by TianluWang
Describe here, in technical detail, what you have done. Make sure you include: - a theoretical description of the algorithm(s) you implemented - logical architecture (refer to IDD template for description) - software architecture (refer to IDD template for description) - details on the actual implementation where relevant (how does the implementation differ from the theory?) - any infrastructure you had to develop in order to implement your algorithm - If you have collected a number of logs, add link to where you stored them
Feel free to create subsections when useful to ease the flow
Modified 2018-02-07 by tanij
Be rigorous!
Modified 2018-02-07 by tanij
Is there something you think still needs to be done or could be improved? List it here, and be specific!
No questions found. You can ask a question on the website.