|
| 1 | +\documentclass{article} |
| 2 | +\usepackage{wrapfig} |
| 3 | +\usepackage{graphicx} |
| 4 | +\usepackage{color} |
| 5 | +\usepackage{enumitem,lipsum} |
| 6 | +\usepackage[labelformat=empty]{caption} |
| 7 | + |
| 8 | +\linespread{1.05} |
| 9 | +\title{The Superhero Machine Learning Api} |
| 10 | +\date{} |
| 11 | +\begin{document} |
| 12 | + \maketitle |
| 13 | + % \thispagestyle{empty} |
| 14 | + Here at e-conomic we really love superheros. In fact we love superheros |
| 15 | + so much that we have decided to start a new department which will focus |
| 16 | + solely on inventing new superhero characters. Our team of dedicated |
| 17 | + inventors will think out new awesome characters and for each new creation |
| 18 | + the inventor will devise a character description containing information |
| 19 | + such as abilities, partnerships, team affiliations, etc. |
| 20 | + |
| 21 | + The two legendary US publishers, Marvel Comics and DC Comics, have shown |
| 22 | + great interest in our new department, and they would like to make offers |
| 23 | + on each new character. |
| 24 | + |
| 25 | + \begin{figure}[h] |
| 26 | + \minipage{0.5\textwidth} |
| 27 | + \centering |
| 28 | + \includegraphics[width=0.7\textwidth]{marvel} |
| 29 | + \caption*{\scriptsize{Superheros published by Marvel Comics}} |
| 30 | + \endminipage\hfill |
| 31 | + \minipage{0.5\textwidth} |
| 32 | + \centering |
| 33 | + \includegraphics[width=0.8\textwidth]{dc} |
| 34 | + \caption*{\scriptsize{Superheros published by DC Comics}} |
| 35 | + \endminipage |
| 36 | + \end{figure} |
| 37 | + |
| 38 | + Due to market circumstances, when a new character is offered to a |
| 39 | + publisher, all other publishers lose interest in buying that character, |
| 40 | + because they are afraid that the company who got the offer first, may |
| 41 | + steal the idea and bring onto the market a similar superhero, before the |
| 42 | + investment can be legally secured. |
| 43 | + |
| 44 | + That is why we need your help! We mined Wikipedia for Marvel- and |
| 45 | + DC-superhero articles, and now we hand you the dataset\footnote{In the |
| 46 | + handout you will find \texttt{data.zip}}. |
| 47 | + |
| 48 | + Your task is to build a RESTful API that (\textit{i}) manages the |
| 49 | + articles, (\textit{ii}) and offers a prediction endpoint, that uses |
| 50 | + machine learning to classify a text as being either closer to the Marvel |
| 51 | + or the DC universe. |
| 52 | + |
| 53 | + \clearpage |
| 54 | + The API should use some kind of database for persistence and offer the |
| 55 | + following endpoints. |
| 56 | + \vspace{0.5cm} |
| 57 | + \begin{description}[labelindent=0.5cm, leftmargin=1cm] |
| 58 | + \item[\texttt{/article/(\$id)}] \hfill \\ |
| 59 | + Article resource endpoint(s). The api should as minimum be able |
| 60 | + to read a resource, creates a resource, updates a resource, |
| 61 | + delete a resource and list resource URI's. The training data from |
| 62 | + \texttt{data.zip} should be posted to this endpoint. |
| 63 | + \item[\texttt{/train}] \hfill \\ |
| 64 | + Train or re-train your machine learning model based on the |
| 65 | + articles in the database. |
| 66 | + \item[\texttt{/predict}] \hfill \\ |
| 67 | + Receive a text as input and return classification results. |
| 68 | + \end{description} |
| 69 | + \vspace{0.5cm} |
| 70 | + \noindent You will present the solution to a team of e-conomic developers |
| 71 | + and they might have questions and suggestions about the code and machine |
| 72 | + learning techniques. Keep in mind that we do not expect your code to be |
| 73 | + production ready. What we're looking for is how you approach the problem, |
| 74 | + preferably creating some nice and clean code along the way. We will |
| 75 | + appreciate if your solution is working and comes with a build guide, so |
| 76 | + that we can run and test it. |
| 77 | + |
| 78 | + When presenting the solution you are welcome to bring your own laptop if |
| 79 | + that suits you better. In case you have questions, please do not hesitate |
| 80 | + to ask. |
| 81 | + \\\\ |
| 82 | + Happy coding :) |
| 83 | +\end{document} |
0 commit comments