Assignment Reporting

 

Before each meeting

On the day before each meeting the progress tables (see link in Assignments) should be updated. Both in terms of worked hours and best results so far on test problems (when applicable).

You should also upload your slides (see template Links to an external site.) in TWO places:

  • In the "Canvas Assignment" page, as a pdf. This is for book-keeping to check that you met the deadline etc.
  • In the "Canvas Links to slides" page, as a link to your google slides document. This will be used for the presentations and for peer-review.
    • Make sure anyone with a link can view and comment

At each meeting

At least one of each group should attend and be ready to present the current status of the project using the slides uploaded. Focus on what is interesting to your peers, and why you think your method is good.

At final meeting of Assignment X

At the final meeting you should be ready to run your code on new problem sets.

Report at end of Assignment X

The result of the assignment should be reported in a document, in the form of a scientific paper. We use the same format and instructions as the AI course (DD2380), created by Prof. Patric Jensfelt. If resubmissions are needed, they should be submitted within 2 weeks of the feedback being received.

Note that the Related Work section needs to include at least 5 references to research papers (URLs and Wikipedia does not count)

Note also that the section Related Work you can take inspiration from methods used by your fellow students, and in Experimental Results you should use the outcome of the final test (for A1) to compare the performance of your approach the the performance of others. A table should be included showing the results.

Apply a top-down approach when writing, as explained in this video Links to an external site. .

Finally, avoid giving a chronological description of your work (i.e., first we did this, then we did that etc), instead present the most important findings first.

The feedback form is given below. Make sure you check all aspects listed. If you ignore this (getting "Not sufficient") you will get a warning for ignoring instructions.

feedback.png

What do to if you failed in solving the problem

As described at the beginning of the course, it is allowed to fail an assignment if you really believed in your solution approach, and you really worked hard to make it work. Then it can still be a learning experience.

If this happens, you will adapt your report as described below:

  • The page limit does not apply to you.
  • Include everything listed above in your report, including a description of your approach and how it performed.
  • Include an additional section called: Analysis of Failure
    • Include a subsection Technical Aspect of Failure: describing why it did not work as you expected
    • Include a subsection Management Aspect of Failure
      • Including the plot from your Progress-report Links to an external site., showing your planned input in time, actual input in time, actually progress and risk estimate (use your original data, no post processing).
      • Include a detailed analysis of the plan-progress-risk above. When did you realize that failure was a major risk? How did you adapt to the risk? What did you do to make sure you could make it in time?
    • Include a subsection Lessons Learnt: describing how you will avoid similar situations in the future

 

See details in respective assignment.