|
***General instructions for the participants in Datathon 2017***
|
|
***General instructions for the participants in Datathon 2017***
|
|
|
|
|
|
**The task**
|
|
**The task**
|
|
|
|
|
|
During the event your task would be to develop a data based solution to a chosen case study.
|
|
During the event your task would be to develop a data based solution to a chosen case study.
|
|
To start working fork the project, containing the desired case study. , work, upload final results back
|
|
|
|
|
|
To start working fork the project, containing the desired case study. Every project contains general information for every team, specific case description and data sets. After you fork the project you start developing your solution. There are some technical opportunities provided (read further down). Before the deadline you should upload your final results back to your fork of the project.
|
|
|
|
|
|
Expected outputs are:
|
|
Expected outputs are:
|
|
* description data processing required to solve the case;
|
|
* description data processing required to solve the case;
|
|
* description of algorithms, workflows, etc.;
|
|
* description of algorithms, workflows, etc.;
|
|
* working models, rulesets, etc.;
|
|
* working models, rulesets, etc.;
|
|
* source codes, used libraries;
|
|
* source codes, used libraries;
|
|
|
|
|
|
After you have developed your solutions you will have the opportunity to make a short presentation about it.
|
|
After you have developed your solutions you will have the opportunity to make a short presentation about it.
|
|
|
|
|
|
During your work you should document it in a publicly available white paper (or report) with a provided template.
|
|
During your work you should document it in a publicly available white paper (or report) with a provided template.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Time frames**
|
|
**Time frames**
|
|
|
|
|
|
Day 1: Friday
|
|
Day 1: Friday
|
|
|
|
|
|
16:30 - 17:00 Registration
|
|
16:30 - 17:00 Registration
|
|
|
|
|
|
17:00 - Opening
|
|
17:00 - Opening
|
|
|
|
|
|
17:10 - 20:45 - Cases Presentations
|
|
17:10 - 20:45 - Cases Presentations
|
|
|
|
|
|
20:50 - 21:30 - Team forming
|
|
20:50 - 21:30 - Team forming
|
|
|
|
|
|
21:30 - work starts
|
|
21:30 - work starts
|
|
|
|
|
|
|
|
|
|
Day 2: Saturday
|
|
Day 2: Saturday
|
|
|
|
|
|
11:59 Deadline for team registration (team name, team members and chosen case study)
|
|
11:59 Deadline for team registration (team name, team members and chosen case study)
|
|
|
|
|
|
00:00 - 23:59 Work
|
|
00:00 - 23:59 Work
|
|
|
|
|
|
|
|
|
|
Day 3: Sunday
|
|
Day 3: Sunday
|
|
|
|
|
|
00:00 - 15:00 Work
|
|
00:00 - 15:00 Work
|
|
|
|
|
|
15:00 Deadline for uploading final solutions and white paper
|
|
15:00 Deadline for uploading final solutions and white paper
|
|
|
|
|
|
15:00 - 16:00 Break
|
|
15:00 - 16:00 Break
|
|
|
|
|
|
16:00 – 17:30 Team presentations and Q&A
|
|
16:00 – 17:30 Team presentations and Q&A
|
|
|
|
|
|
19:00 – 20:00 Voting and awards, networking
|
|
19:00 – 20:00 Voting and awards, networking
|
|
|
|
|
|
|
|
|
|
the paper
|
|
the paper
|
|
|
|
|
|
tehnical - jupyter notebook, gitlab
|
|
tehnical - jupyter notebook, gitlab
|
... | | ... | |