-
Notifications
You must be signed in to change notification settings - Fork 14
User Guide
Problem is a complex, end-to-end pipeline that leads from raw data to the final score. User starts working on a problem by opening the welcome notebook (for example, Right Whales Recognition). Minerva developers implemented the entire pipeline and divided it into logical pieces. These pieces are called tasks - User's main point of interest.
Task contains a single processing step, such as a ConvNet implementation or a post-processing function. It is presented in its own notebook (for example, this one), where User can find the description of the task, learning objectives, what is expected as a solution and some auxiliary information that should help in the implementation process. Note that User may work on tasks in any order.
Technically, User works on the task by implementing the solution function, stub of which is already in the notebook. When the solution is ready, User submits the task and the corresponding part of the pipeline is replaced by the User's implementation. Recall that the entire pipeline is pre-implemented by the Minerva team.
User submits the task by running a single command. The structure of this command is explained in detail in the welcome notebook.
Currently, feedback is provided in a binary way: if the final score is very close to the default pipeline implementation, User receives an appropriate praise, if it is not, User is asked to try again.
Problem consists of many tasks and User is encouraged to solve all of them. User can work on tasks in any order and eventually re-implement a complex data scientific pipeline.