Skip to content

i) Data

Fabian C. Annaheim edited this page Mar 29, 2023 · 4 revisions

Like for many other modern appplications, the core of 3ES is a data-driven solution because the value this application will provide to its users comes from a computer vision model that is trained on large amounts of data. 3ES needs to recognize hand-written digits which is why the acquisition of such images is absolutely crucial for the success of the project. Luckily, this task is everything but new wherefore tons of these images can be downloaded for free. The larger challenge lies in the recognition of the score table as a whole as well as of the candidate number which is represented as a string of numbers separated with dots. How this data should be acquired and how much of it is needed is part of the second retrospective.

On the other hand the remaining parts of the application are not data-driven at all. Despite the web server has the task of receiving and processing incoming data, it is still a comparatively low volume which is why no special actions are needed to guarantee this service. The same is true for the frontend part which only deals with user interactions and is also determined by low data volume.

Clone this wiki locally