In most of the cases, the Master Project is a teamwork project of n students working on a subject. Individual projects can also be considered. Projects will naturally be expected to require an effort proportional to the number of team members (300 hours per student). Students may choose a project from a list of suggested projects (see below) or propose one of their own ideas.
- Form a team of 1-5 students.
- Choose the prioritized list of projects.
- The Master’s Project Coordinator, Laura Igual (
ligual@ub.edu) will assign you a project, by looking for a (maybe global) maximum of the function that represents your global preferences. - Discuss the research questions, goals, approach you intend to take, methodology, data needed and time plan with your project supervisor.
- Construct a logical outline for the project. Include analysis steps and expected outcomes.
- Define a clear role for all members of the group. This role will be considered in your personal student assessment.
- Fill in details of the project + role definition in a short document (max 2 pages).
- Hand in this document to your supervisors and start the project development!
The final project delivery must include:
- all code produced in a GitHub (or similar) software repository.
- a project report (see the Report Template directory).
- a high level description of the completed project (jupyter notebook and/or blog entry).
See these examples:
- https://github.com/axelbrando/Mixture-Density-Networks-for-distribution-and-uncertainty-estimation
- http://diposit.ub.edu/dspace/handle/2445/133281
The quality of the projects will be graded by using three sources of information:
- The delivered information at the end of the project. We will use a “Project Evaluation Rubric” to assign an individual mark to each member of the project.
- The public presentation of your project. Your presentation should be professional enough to give at a technical conference (e.g. organized approach, prepared slides, a short demo or video if appropriate).
- Peer-evaluation. Team members will assess other members of the team as well as themselves. Peer assessment provides data that will be used in assigning individual grades for team members.
- Feb. 3: First follow up meeting
- Feb. 4: Deadline for sending your project priorities. Please, fill in this form
- Feb. 7: Assignment of projects & supervisors to student groups.
- Feb. 14: Limit for delivering the project proposal short document to your advisor.
- Feb 14 - Jul. 1: Period of development of your project.
- Jun. 1: Limit for informing if you will present the TFM in July or September.
- Jul. 1 & Set. 2: Limit for final delivery of your project (via Campus Virtual task).
- Jul. TBD & Set. TBD: Presentations.
- Every student have to submit an individual report.
- Use the latex report template available in this repository.
- The report should contain 50 pages for a teamwork project and 30 pages for an individual project.
- The report should contain a link to the project Github repository.
- For team projects, the report should contain a final appendix where the contribution of each of the team members should be detailed. Each member will be evaluated based on this information.
- Delivery should be only digital by Campus Virtual.
- Here you can find the style guide Interuniversity Style Guide for Writing Institutional Texts in English which aims to facilitate interuniversity communication and improve the quality of the institutional English-language documents we produce for international readers.
- For the basic structure of your GitHub you can use Cookiecutter
- You can find Notebook examples here.
- For non-publicable projects: use private Bitbucket repositories.
- Presentations will be 20 minutes for individual projects, 30 minutes for projects of 2 students and 40 minutes for projects of 3 students, followed by 10 minuts of quetsions.