Major rework

.github/workflows/verify.yml

@@ -26,7 +26,14 @@ jobs:
           biber --validate-datamodel main
           pdflatex -halt-on-error main.tex
       - name: Verify PDF
-        run: >
-          docker run --rm -t -v "$(pwd):/data" 
-          ghcr.io/verapdf/cli@sha256:26a57c6711ae1d59f987f34ca411f87d8078e3ae75bb90671fcece957b75dcee
-          -f 1b main.pdf
+        run: |
+          if [ "$ACT" = "true" ]; then
+            echo "No docker in ACT"
+          else
+            docker run --rm -t -v "$(pwd):/data" ghcr.io/verapdf/cli:latest -f 1b main.pdf
+          fi
+      - name: Upload PDF
+        uses: actions/upload-artifact@v4
+        with:
+          name: pdf
+          path: main.pdf

Chapters/abstract.tex

@@ -1,8 +1,9 @@
-\begin{abstract}
+% Remove the following line and define them in main.tex
+\keywords{M.Sc. degree\spc master’s thesis instructions\spc structure of a master’s thesis\footnote{The keywords should be different from the ones used in the title. Remove this footnote from your thesis.}}
 
-This document provides general guidance for a degree student of Computer Science and Engineering in preparing his/her master's thesis. This guide defines the role of a thesis in the M.Sc. Degree, presents the actions to be taken in different phases of the thesis procedure and introduces the way that master’s thesis is written. The document has been formatted based on these guidelines to serve as an example how the thesis should look like.
-
-\keywords M.Sc. degree, master’s thesis instructions, structure of a master’s
-thesis\footnote{The keywords should be different from the ones used in the title. Remove this footnote from your thesis.}
-
-\end{abstract}
+\begin{thesisabstract}{english}
+  \abstractmetadata
+% Alternatively you can write the abstract here.
+% Paragraph breaks and special characters are allowed here, but the content
+% should essentially be the same as the abstract in your metadata
+\end{thesisabstract}

Chapters/appendices.tex

@@ -8,16 +8,17 @@
 \newpage
 \markboth{left}{\normalfont{Appendix 1. Example Abstract}}
 
-{\noindent \bf Jurmu M.\ (2007) Resource Management in Smart Spaces Using Context-Based Leases.} University of Oulu, Department of Electrical and Information Engineering. Master’s Thesis, 77 p.
+\noindent \textbf{Jurmu M.\ (2007) Resource Management in Smart Spaces Using Context-Based Leases.} University of Oulu, Department of Electrical and Information Engineering. Master’s Thesis, 77 p.
 
 \begin{center}
-{\textbf{\fontsize{16}{19pt}\selectfont ABSTRACT}\\}
+\textbf{\fontsize{16}{19pt}\selectfont ABSTRACT}\\
 \end{center}
 
-{\noindent \bf The convergence of wireless access networks in conjunction with the increased computing power of the handheld terminals is preparing the emergence of the ubiquitous computing paradigm. In the center of this paradigm are smart spaces, which are local environments saturated with various embedded computational resources. These spaces co-operate with mobile client devices in enabling advanced, service-oriented computation scenarios. This co-operation is typically enabled through the utilization of distributed and modular middleware frameworks. An emerging additional requirement however is the possibility to harness resources from the proximity environment to the mobile device in an on-demand fashion. This is a challenge especially to the resource management infrastructure of the smart spaces.
+{\bfseries \noindent The convergence of wireless access networks in conjunction with the increased computing power of the handheld terminals is preparing the emergence of the ubiquitous computing paradigm. In the center of this paradigm are smart spaces, which are local environments saturated with various embedded computational resources. These spaces co-operate with mobile client devices in enabling advanced, service-oriented computation scenarios. This co-operation is typically enabled through the utilization of distributed and modular middleware frameworks. An emerging additional requirement however is the possibility to harness resources from the proximity environment to the mobile device in an on-demand fashion. This is a challenge especially to the resource management infrastructure of the smart spaces.
 
 This thesis explores the concept of a smart space and presents a review of the current research and technologies. Subsequently, a lease-based design for resource management in smart spaces is presented. Leases in this work are negotiated agreements between the mobile clients and the resource management infrastructure, regarding the harnessed resources. Leasing is seen as a suitable solution for the management due to the transient nature of the resource usage. The inclusion of additional contextual features to the leases further facilitates the management.
 
-Requirements for the design are derived from the review and from an example usage scenario. The requirements include dynamic mapping and contracting of resources from the proximity environment, monitoring of the contract validity, access control towards the resources and dynamic maintenance of the smart space infrastructure. Presented design is analytically compared against existing solutions, and several points for future development are listed. According to the comparison, none of the existing solutions utilize contracts with contextual validity in resource management. Two publications of this work have been accepted into an international conference and a workshop on the focus area of pervasive computing.}
+Requirements for the design are derived from the review and from an example usage scenario. The requirements include dynamic mapping and contracting of resources from the proximity environment, monitoring of the contract validity, access control towards the resources and dynamic maintenance of the smart space infrastructure. Presented design is analytically compared against existing solutions, and several points for future development are listed. According to the comparison, none of the existing solutions utilize contracts with contextual validity in resource management. Two publications of this work have been accepted into an international conference and a workshop on the focus area of pervasive computing.
 
-{\bf \keywords Ubiquitous computing, mobile computing, task-based computing, context-awareness, QoS.}
+\noindent\textbf{Keywords: Ubiquitous computing, mobile computing, task-based computing, context-awareness, QoS.}
+}

Chapters/experiments.tex

@@ -100,7 +100,7 @@ \section{References}
 
 The references are mostly cited in your own words, and direct quoting is used only if you want to emphasis the source. In this case you place the quote in hyphens, for example saying that the original phrasing of Moore’s law is  “The complexity for minimum component costs has increased at a rate of roughly a factor of two per year (see graph on next page). Certainly over the short term this rate can be expected to continue, if not to increase. Over the longer term, the rate of increase is a bit more uncertain, although there is no reason to believe it will not remain nearly constant for at least 10 years.”~\cite{moore}.  Correct referencing is  important as the archiving of electronic makes them easily accessible (either in library or in the Internet, depending on the publicity level selected by the thesis author).
 
-The list of references is written according to the instructions of the IEEE Transactions series~\cite{ieeetransactions}; using the running numbering. Referencing is easiest to do using \LaTeX\ for writing the thesis and following the model given in these instructions. You should add your own references to the file \textit{citations.bib}. Following the instructions automatically creates the list of references in the order in which they appear in the text. References in the text are then indicated with a reference number, e.g.,~\cite{lappalainen} or~\cite{lappalainen, acta, korpela}. References to books should include also page number, for example~\cite[p.15]{lappalainen} or~\cite[p.15-17]{lappalainen}.
+The list of references is written according to the instructions of the IEEE Transactions series~\cite{ieeetransactions}; using the running numbering. Referencing is easiest to do using \LaTeX\ for writing the thesis and following the model given in these instructions. You should add your own references to the file \textit{citations.bib}. Following the instructions automatically creates the list of references in the order in which they appear in the text. References in the text are then indicated with a reference number, e.g.,~\cite{lappalainen} or~\cite{lappalainen, acta, korpela}. References to books should include also page number, for example~\cite[p.\ 15]{lappalainen} or~\cite[pp.\ 15--17]{lappalainen}.
 
 References need to be presented so that it is clear what information is from a source and what is created by the author. Also the sources of equations, figures, and tables need to be given, when not created by the author her/himself. In addition, permissions need to be asked for tables and figures. Special attention needs to be paid to web sources, as web content can have a short life cycle. Hence, the date of downloading referenced web content should always be mentioned in the reference.
 

Chapters/implementation.tex

@@ -18,11 +18,6 @@ \section{Linguistic style}
 \section{Typography}
 
 In the text typography, you need to use the following guidelines and rules:
-\newlength{\mylen}
-\setbox1=\hbox{$\bullet$}\setbox2=\hbox{\tiny$\bullet$}
-\setlength{\mylen}{\dimexpr0.7\ht1-0.5\ht2}
-\renewcommand\labelitemi{\raisebox{\mylen}{\tiny$\bullet$}}
-\renewcommand\labelitemii{\raisebox{\mylen}{\tiny$\bullet$}}
 
 \begin{itemize}
     \setlength\itemsep{0pt}
@@ -80,7 +75,6 @@ \subsection{Figures and tables}
     tables).
 \end{itemize}
 
-\captionsetup[table]{justification=raggedright,singlelinecheck=off}
 \begin{table}[!ht]
 % Add some padding to the table cells:
 \def\arraystretch{1.1}%

Chapters/tiivistelma.tex

@@ -1,11 +1,8 @@
-\begin{tiivistelma}
-
-Näissä ohjeissa opastetaan valmistumisvaiheessa olevaa opiskelijaa diplomityön tekemisessä. Ohjeissa selvitetään työn asema diplomi-insinööritutkinnossa, kerrotaan toimenpiteet, joihin työn tekijän on ryhdyttävä työn eri vaiheissa, sekä määritellään yksityiskohtaisesti diplomityön kirjallinen rakenne. Ohje on muotoiltu noudattaen näitä kirjoitusohjeita ja toimii siten esimerkkinä, miltä diplomityön tulisi näyttää.
-
-\avainsanat diplomi-insinöörin tutkinto, opinnäytetyön ohjeet, diplomityön
-rakenne\footnote{Käytä avainsanoina eri sanoja kuin lopputyön otsikossa. Poista tämä alaviite lopputyöstäsi.}
-
-%\avainsanat diplomi-insinöörin tutkinto, opinnäytetyön ohjeet, diplomityön
-%rakenne.}
-
-\end{tiivistelma}
+% Määrittele avainsanat main.tex:ssä ja poista seuraava rivi
+\avainsanat{diplomi-insinöörin tutkinto\spc diplomityön ohjeet\spc diplomityön rakenne\footnote{Käytä avainsanoina eri sanoja kuin lopputyön otsikossa. Poista tämä alaviite lopputyöstäsi.}}
+\begin{thesisabstract}{finnish}
+\tiivistelmametadata
+% Voit myös laittaa tähän version tiivistelmästä, joka sisältää kappalejakoja
+% ja erikoismerkkejä. Sisällön tulisi kuitenkin olla muutoin identtinen
+% metadatassa olevan version kanssa.
+\end{thesisabstract}

Gallery/protocolheader.tex

@@ -0,0 +1,17 @@
+% Load the bitfield package in your main.tex
+% \usepackage{bytefield}
+
+% Define a command to represent a protocol header table using bitfield
+% Example usage: TCP header representation
+\begin{figure}[ht]
+  \centering
+  \begin{bytefield}[bitwidth=\textwidth/32, bitheight=\widthof{~Data offset~}]{32} % Added horizontal spacing
+    \bitbox{16}{Source Port} & \bitbox{16}{Destination Port} \\
+    \bitbox{32}{Sequence Number} \\
+    \bitbox{32}{Acknowledgment Number} \\
+    \bitbox{4}{\rotatebox{90}{\scriptsize Data Offset}} & \bitbox{3}{\rotatebox{90}{\scriptsize Reserved}} & \bitbox{9}{Flags} & \bitbox{16}{Window Size} \\
+    \bitbox{16}{Checksum} & \bitbox{16}{Urgent Pointer} \\
+  \end{bytefield}
+  \caption{TCP Header}
+  \label{tcp-header}
+\end{figure}

citations.bib

@@ -180,11 +180,17 @@ @Book{heikkinen:2011
     address = "University of Oulu, Department of Computer Science and Engineering"
 }
 
-@misc{toivonen:2004,
-    author = "Toivonen, T. and Heikkilä, J. and Silvén ,O.",
-    title = "{Oulun yliopisto, assignee. Method and device for coding successive images}",
-    year = "2004",
-    note = "European patent 1438861"
+@patent{toivonen:2004,
+	title = {Method and device for coding successive images},
+	url = {https://patents.google.com/patent/EP1438861A1/en?oq=1438861},
+	holder = {Individual},
+	type = {patenteu},
+	number = {1438861A1},
+	author = {Toivonen, Tuukka and Heikkilä, Janne and Silvén, Olli},
+	urldate = {2025-06-09},
+	date = {2004-07-21},
+	langid = {english},
+	keywords = {block, coded, theoretic, theoretic transform, transform},
 }
 
 @book{asuntoliitto_asumistaso_1969,
@@ -195,3 +201,5 @@ @book{asuntoliitto_asumistaso_1969
 	author = {{Suomen Asuntoliitto} and {Asuntoreformiyhdistys} and {Suomen asuntomessut}},
 	year = {1969},
 }
+
+