The students are required to complete a developemental project. During the course it will be offered the possibility to present the project (in this case no oral exam will be required). The students are required to produce a final report in the form of a scientifc paper written in latex.

EXAM MODALITIES

The exam consists in a development project. The project will be presented by the candidate during the second part of the course*. The project will be delivered along with a report formatted as a scientific paper. SEE THE FOLLOWING RULES.

(*) Non-attending students or candidates that failed to schedule and discuss their project presentation within the required deadlines will have to pass an oral exam in substitution of the presentation.

IMPORTANT RULES FOR PROJECT SUBMISSION

1) ALL PROJECTS MUST BE SUBMITTED AT LEAST 3 WEEKS BEFORE THE EXAM REGISTRATION DEADLINE.

2) You will have to submit the project proposal by filling a google form at midterm (november) and wou will be given access to a google drive folder.

3) All the projects MUST be submitted FIRSTLY uploading on the google drive folder (shared with you by the teacher using your institutional account) including:

a) the complete ZIPPED folder with your (runnable) code, and the ZIPPED dataset folder if not publicly aviable
b) the complete report in form of a scientific paper in pdf (including the latex source folder ZIPPED)

Therefore I expect to find only 3 (or 4) files: report.pdf, latex.zip, code.zip (and dataset.zip if not easily dowloadable or modified).

4) AFTER point 3) you MUST UPLOAD ALSO on the google classroom the pdf of the report by filling the REPORT SUBMISSION FORM.

A projects is as delivered ONLY after all the codes, scripts, datasets, latex source code and project pdf has been submitted and notified to me by you with an email.

5) The paper MUST be 7 pages minimum, written in latex with THIS (link) template and respecting the following rules:

a) Use the 2 columns template (sample-2col.tex);
b) Use the bibtex bibliography style (sample-ceur.bib);
c) Reference all the table and figures into the text and place them as close as possible to it;
d) Do not change the template*, the font size, or force any spacing
*in some system however you will have to drop the use of "minted" package, you can do that.
e) IMPORTANT THINGS TO DO:
- don't forget the abstract that resumes your work
- before the introduction add a \Section{HIGHLIGHTS} containing 5 SMALL BULLET PONTS with the highlight of YOUR work, novelty and achievement
- do a proper introduction (i expect it to be more than one page)
- do a proper literature research for the second \Section{Related Works}
- describe your implementation carefully and with all the possible details (add tables, images, graphs)
- write a \Section{Results} also with some numerical metrics (accuracy, precision, error, percentage error...)
- make COMPARISONS with existing works (add tables, images, graphs)
- elaborate on the results and discuss their implications in your \Section{Conclusion}
- avoid unnecessary pictures, avoid unnecessary waste of space, but don't worry if your report is longer than 7 pages, that's ok

6) All the projects MUST have some differences with respect to literature, therefore they must have "something" novel to report;

7) All the projects will be accurately analyzed by a team of experts and compared with the existing literature. Plagiarism will result in exam failure

8) A mere implementation of "existing" code or the simple replica of work done by other will result in a "compilative project" with scoring 18/30.

9) DO NOT SHARE YOUR CODE ON PUBLIC REPOSITORIES BEFORE THE END OF THE EXAM otherwise I will be forced to declare your project NULL (exam failed)

NOTE: students that have not submitted their proposal or did not present their projects during lectures will have to pass the oral exam (considered for the final score).

AFTER SUBMISSION

You will receive an email with my corrections within 3 weeks from the submission, along with the corrections you will be informed

• IF your projects is sufficient / non sufficient to pass the exam (in the latter case the corrections are intended as mandatory)

• WHAT improvement I expect if you want a better grade

If you accept to make the corrections then your project will be evaluated again within 2 weeks from the submission of the new version. If the correction are not mandatory you can accept the current grade proposal and it will be registered as it is.

NOTE: excellent papers/projects will be considered for publication.

FINAL SCORE - GRADING TABLE