Information on Final Project
The goal of the final project is to do some concrete Python implementation and documenting it in a short report. The project can be done in groups with 1-3 students. There are three deliverables for the final project that should be handed in:
- Python code. Either plain Python 3 code in one or more .py files, or Python 3 code embedded into a Jupyter file.
- A report - maximum 4 pages. The front page must contain the information listed below (the front page does not count towards the page count).
- Visualization of data. E.g. matplotlib output. The plots should be included in an appendix to the report, that does not count towards the page count, or alternatively embedded in a Jupyter file.
Project report
The project report must contain the below front page (not counted in the 4 pages). Make sure you read and understand the note on plagiarism. The report can be written in Danish and English.
project-front-page.pdf | project-front-page.docx | project-front-page.tex
Project descriptions
You can choose any of the projects listed in the menu as your final project.
Evaluation of project
The project deliverables will be scored according to the below rubric.
| Deliverable | Not present 0% |
Many major shortcomings 25% |
Some major weaknesses 50% |
Minor weaknesses 75% |
Solid 100% |
|---|---|---|---|---|---|
| Code 50% |
No code, or code where no part computes the required | Some elementary parts of the code work, but significant parts do not work | Most essential parts of the code work, but the code does not completely solve the problem addressed | Overall good code, but space for improvement, e.g. missing documentation, code could be made clearer | Complete code, well structured, good use of modules, clear variable names, good documentation, PEP8 compliant |
| Visualization 25% |
No visualization | Very few or very unclear visualizations | Some visualizations illustrating basic idea | Overall good visualization but some details could have been more clear | Clear visualizations documenting the problem being solved and supporting the conclusions drawn |
| Report 25% |
No report | Very unpolished report, missing structure, no clear conclusions, major misunderstandings | The basic ideas are described but details are missing | Overall good report but for some aspects the level of detail/precision could be higher | Solid report, containing reflection upon the implementation done, discussion of the Python modules used, the design choices made, discussion of the structure of the code, what were the hardest parts, what is missing, and discussion of testing and visualization |