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

Started working on results
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Andre Henriques 2024-04-24 19:50:53 +01:00
parent 46cc4e4a06
commit 5fa89aec1d
1 changed files with 38 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
report/report.tex
View File

@ -159,22 +159,13 @@
\subsection{Project Structure}
The report on the project shows the development and designs stages of the project. With each section addressing a part of the design and development process.
\begin{longtable}{rp{0.45\textwidth} rp{0.45\textwidth}}
\begin{longtable}{rp{0.35\textwidth} rp{0.45\textwidth}}
\hyperref[sec:introduction]{Introduction} & The introduction section will do a brief introduction of the project and its objectives. \\
\hyperref[sec:lit-tech-review]{Literature and Technical Review} & The Literature and Technical Review section will introduce some current existing projects that are similar to this one, and introduce some technologies that can be used to implement this project. \\
\hyperref[sec:sanr]{Service Analysis and Requirements} & This section will analyse the project requirements. The section will define design requirements that the service will need to implement to be able to achieve the goals that were set up. \
\hyperref[sec:sanr]{Service Analysis and Requirements} & This section will analyse the project requirements. The section will define design requirements that the service will need to implement to be able to achieve the goals that were set up. \\
\hyperref[sec:sdai]{Service Design and Implementation} & This section discusses transforming the requirements defined in the previous section and implementing them, to obtain a working application. \\
\hyperref[sec:lsec]{Legal, Societal, and Ethical Considerations} & This section will cover potential legal societal and ethical issues that might arise from the service and how they are mitigated.\\
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
% foo & bar \\ \hline
\caption{Project structure}
\label{tab:project-structure}
\end{longtable}
@ -693,6 +684,7 @@
For example, if the service gets acquired by a company that also wants to use the data provided to system for other reasons.
\pagebreak
@ -706,7 +698,42 @@
\section{Evaluating the Service}
This section will discuss how the service can be evaluated from a technical standpoint and its results.
With the goals of the project there are two kinds of tests that need to be accounted for.
User testing tests that relate to the experience of the user while using the project and tests that quantitive test the project.
Such as accuracy of the generated models, response time to queries.
\subsection{Testing the model}
To test the system a few datasets were selected.
The datasets were selected to represent different possible sizes of models, and sizes of output labels.
The ImageNet\cite{imagenet} was not selected as one of the datasets that will be tested, as it does not represent the target problem that this project is trying to tackle.
The tests will measure:
\begin{itemize}
\item Time to process and validate the entire dataset upon upload
\item Time to train the dataset
\item Time to classify the image once the dataset has been trained
\item Time to extend the model
\item Accuracy of the newly created model
\end{itemize}
The results will be placed in the results table.
\subsubsection{MNIST}
The MNIST\cite{mnist} dataset was selected due to its size. It's a small dataset that can be trained quickly and can be used to verify other internal systems of the service.
\subsection{Results}
\begin{longtable}{ | c | c | c | c | c | c |}
\hline
MNIST & 0ms & 0ms & 0ms & 0ms & $98\%$ \\ \hline
\caption{Evaluation Results}
\label{tab:eval-results}
\end{longtable}
\pagebreak