andr3/fyp-report
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 3 Wiki Activity

moved the images to the appendix
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Andre Henriques 2024-02-01 12:39:05 +00:00
parent 0202c06afe
commit f5080ddcc0
1 changed files with 23 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
report/report.tex
View File

@ -169,7 +169,7 @@
% There are also unsupervised learning methods that do not have a fixed number of classes. While this method would work as an expandable model method, it would not work for the purpose of this project. This project requires that the model has a specific set of labels which does not work with unsupervised learning which has unlabelled data. Some technics that are used for unsupervised learning might be useful in the process of creating expandable models. % There are also unsupervised learning methods that do not have a fixed number of classes. While this method would work as an expandable model method, it would not work for the purpose of this project. This project requires that the model has a specific set of labels which does not work with unsupervised learning which has unlabelled data. Some technics that are used for unsupervised learning might be useful in the process of creating expandable models.
\pagebreak \pagebreak
\section{Problem Analysis \& Design Choices} \section{Problem Analysis}
\subsection{Structure of the Service} \subsection{Structure of the Service}
The system needs to manage: The system needs to manage:
@ -183,7 +183,7 @@
\item{Running of models} \item{Running of models}
\end{itemize} \end{itemize}
The system is designed with a semi-monolithic approach. The management of the data, and generation of the models will be done in the monolith while the training/running of the models will be done in GPU dedicated nodes. The system is designed with a semi-monolithic approach \ref{fig:expandable_models_simple}. The management of the data, and generation of the models will be done in the monolith while the training/running of the models will be done in GPU dedicated nodes.
The overall workflow of a user who wants a model created would be: The overall workflow of a user who wants a model created would be:
\begin{itemize} \begin{itemize}
@ -192,11 +192,8 @@
\item{The user requests the classification or confirmation of an image} \item{The user requests the classification or confirmation of an image}
\end{itemize} \end{itemize}
% TODO add diagram!
\includegraphics[height=\textheight]{expandable_models_simple}
\subsection{Generation Models} \subsection{Generation Models}
The system requires the generation of models. Generating all models based on one single model would decrease the complexity of the system, but it would not guarantee success. The system requires the generation of models \ref{fig:expandable_models_generator}. Generating all models based on one single model would decrease the complexity of the system, but it would not guarantee success.
The system needs to generate successful models, to achieve this, the system will be performing two approaches: The system needs to generate successful models, to achieve this, the system will be performing two approaches:
\begin{itemize} \begin{itemize}
@ -212,13 +209,9 @@
Since the AutoML approach would be more computational intensive, it would be less desirable to run. Therefore, the approach would be for the database search to happen first, where known possibly good models would be first tested. If a good model is found, then the search stops and if no model is found, the system would resort to AutoML to find a suitable model. Since the AutoML approach would be more computational intensive, it would be less desirable to run. Therefore, the approach would be for the database search to happen first, where known possibly good models would be first tested. If a good model is found, then the search stops and if no model is found, the system would resort to AutoML to find a suitable model.
% TODO add diagram
\includegraphics[height=\textheight]{expandable_models_generator}
\pagebreak
\section{Design Choices}
@ -246,8 +239,24 @@
% The smaller models would all be all generated by the platform, this model's purpose would be actually classification. % The smaller models would all be all generated by the platform, this model's purpose would be actually classification.
% This approach would offer a lot of expandability, as it makes the addition of a new class as easy as creating a new small model. % This approach would offer a lot of expandability, as it makes the addition of a new class as easy as creating a new small model.
\appendix \pagebreak
\newpage \section{Appendix}
\begin{figure}
\begin{center}
\includegraphics[height=\textheight]{expandable_models_simple}
\end{center}
\caption{Contains an overall view of the entire system}\label{fig:expandable_models_simple}
\end{figure}
\begin{figure}
\begin{center}
\includegraphics[height=\textheight]{expandable_models_generator}
\end{center}
\caption{Contains an overall view of the model genration system}\label{fig:expandable_models_generator}
\end{figure}
\pagebreak \pagebreak
\section{References} \section{References}