Aim of the project is to analyse or collect real neuroscientific data in order to prove or disprove some theory about inner workings of the brain, find new interesting patterns, which might lead to a new theory, come up with cool visualizations of the data, apply new method or algorithm, etc.
Previous Year Examples
Check examples of project reports from last years:
- Checkpoint 1: Mon 16.04.2018 - 23:59:59
- Checkpoint 2: Mon 07.05.2018 - 23:59:59
- Create an empty version of your final report. Fill in the Introduction and Background sections. If you want, you can also start filling in Methods and Results. Upload it under Practices (Project Checkpoint 2).
Wed 06.06.2018 at 10.15 , Place: Ulikooli 17 (Paabel building) - room 219
- Wed 20.06.2018 at 10.15, Place: Liivi 2 - room 122
- To present in 6th of June you need to have results already. Methods and expected results is not enough. If you have no results yet (due to lack of GPU time for example), you need to postpone the presentation to 20th of June.
- You will have 10 min for the presentation and a few minutes for questions. You should limit your presentation to 5 slides. No posters needed.
- If you want and your project allows you to, you can do a demo.
- REPORT DEADLINE: Wed 20.06.2018- 23:59:59
- Final Report should be ~15 pages (depending on the amount and size of images), this includes the references.
- Report format (advisory): It would be nice if you format your report like a scientific paper rather than a thesis. This means no titlepage, no table of contents, but with abstract, references, author contributions etc.
- People who presented in early June can keep on working on their project and add new results to the report until the 20th June presentation date.
The report, code (or link to repository) and presentation slides must be submitted in practices under Project - Final Submission.
One day late on any of the deadlines above costs 1 point.
The list of projects will grow significantly along the course. Each team can also suggest its own project.
Project difficulty EASY, MEDIUM, HARD do not mean that you cannot get the same number of points for an EASY project as you get for HARD. It means that for an EASY project we expect a lot more thorough study of the problem, because the tool are there to begin with and you do not need to invent them. So you are expected to make a really nice report, produce baselines to compare with etc. For a HARD problem it might be impossible to get decent results in this timeframe, therefore the final results are not as important as the systematic approach you have applied and the effort you put into it.
The project gives up to 40 points of your final grade:
- 20 for the content
- 10 for the appearance and structure of the report
- 10 for final presentation.
- However, the intermediate milestones are a wonderful way to lose points - they are demanded of you and if you fail to deliver or they are not thorough enough, you will be penalized.
- By default, all members of a group get the same amount of points. If you have complaints about a team member inform your supervisor immediately. Also, before starting, choose well who you work with (do not take freeloaders).
Topics can be chosen from >>>HERE<<<. However, feel free to suggest a project that motivate you.
Confirmed teams can be seen >>>Here under Projects sheet<<<
From >>HERE<< you can choose a topic during project fair.
It is highly recommended to set up a GitHub repository to store your code & text and manage the issue tracking.