Courses:Field Robot Summer Course:Technical report

Guidelines

• The purpose of the technical report is to document your personal contributions to the team project. It is recommended but not mandatory that you follow the template listed below. The template resembles the typical structure of a scientific paper which is a good idea to become familiar with.

• The formal maximum length of the report is 5 pages. Though this is not a strict limitation, you should aim for that length.

• The audience of your report ranges from students at your own level to engineers and scientists.

• It is a technical report meaning that you should provide technical documentation of the work you have performed rather than focus on the project and team collaboration etc. Like in all scientific and technical papers avoid writing "I" and "We" except in the conclusion and foreword.

• It is recommended that you write the report in English which is the language used in almost all scientific communities and journals, however Danish is accepted as well.

• The report must be submitted for approval at latest August 28 at 12.00 to kjen@kbm.sdu.dk. Only PDF format is accepted and you must use this topic: "FRSC2012 report Team (your team number) (your name)".

• Please remember to use pictures, diagrams and/or sketches to ease the understanding. It is fully acceptable to draw sketches, tables etc. by hand and then scan or photograph them.

• Please indicate clearly in your report and related material if you would like to allow others to build upon your work. One way of doing this could be to release the material as open source using e.g. the MIT license.

• If you have any diagrams, source code or similar related material please include this. In this case please submit a zip file with your report and the related material.

Content template

Front page

• "Field Robot Summer Course 2012"
• Team number (and name if applicable)
• Your full name
• Date of report submission

Introduction

• Background.
  • What is the project all about? Use a few paragraphs to give the outside reader at chance to understand the context.

• Aim of the project.
  • Basically the aim of your teams project is to build a robot for navigating in row crops, but please use a few lines to write it your way adding the information you think is necessary.

• Contributions to the project.
  • Please list your own contributions to the team project. If you did some of the work in close collaboration with another team member please note that.

• Related work
  • During your literature search what did you find?
  • Your own prior work if any?

Materials and methods

• This is the large section where you add all the technical documentation for your contributions to the team project.

Results and discussion

• In this section you add all results from evaluating and testing your contributions to the team project. Please analyze and discuss the listed results.

Conclusion

• In this section you conclude on your contributions to the team project.

References

Reference to literature that you have cited in the report. Most references probably origin from the Related work section.

Please read the Guide to scientific referencing.

Acknowledgements

Here you have the opportunity to thank people, companies etc. who have somehow contributed to your work or helped you along the way.