andras/great-ai
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases 4 Packages Wiki Activity Actions

Finish first draft

Browse source
This commit is contained in:
Andras Schmelczer 2022-08-19 16:36:28 +02:00
parent 35d400a9ed
commit 08a40bfaaf
No known key found for this signature in database
GPG key ID: 0EA1BC97D0AB076E
14 changed files with 420 additions and 187 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/thesis/chapters/5_cases/main.tex
View file

@ -8,7 +8,7 @@ To achieve this, we have a service-based architecture \cite{kleppmann2017designi
I was among the first engineers on the team, which has grown considerably in the past two years. While architecting, designing, and integrating more and better models into our software solution, I experienced the same difficulties as were described in Chapter \ref{chapter:background}. The gap between prototypes and production-ready services is larger than it seems, and it is also larger than it should be. This has motivated me to investigate the state-of-the-art, and I have found that it is insufficient in many cases. Since the ScoutinScience platform is a typical example of applying AI in the industry, it will serve as the real-life case, problem context, and testbed for attempting to design a solution that can hopefully advance the state-of-the-art.
In this chapter, the process of designing \textit{GreatAI} is described, along with how it fits into real-life use-cases. First, a simple experiment is presented, which leads to the implementation of a software service. Subsequently, as the feature set of the library grows and matures, a more complex component is developed. Lastly, the final version of the design is presented and qualitatively evaluated to verify how well it satisfies the requirements described in Section \ref{section:requirements}.
This chapter describes the process of designing \textit{GreatAI} and how it fits into real-life use cases. First, a simple experiment is presented, which leads to the implementation of a software service. Subsequently, as the feature set of the library grows and matures, a more complex component is developed. Lastly, the final version of the design is presented and qualitatively evaluated to verify how well it satisfies the requirements described in Section \ref{section:requirements}.
\input{chapters/5_cases/naive-bayes}
\input{chapters/5_cases/scibert}