melch/mt-polygon-simplification
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix labels

Browse Source
This commit is contained in:
Alfred Melch 2019-08-24 23:04:21 +02:00
parent bf8894ebe1
commit 7bd0d81418
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
thesis/chapters/04.00-results.tex
View File

@ -13,8 +13,8 @@ Each section in this chapter describes a set of benchmarks run on the same syste
\begin{table}[htb]
\centering
\includegraphics[width=.75\linewidth]{./images/dimensions-1.png}
\label{tbl:dimensions-1}
\caption{Problem dimensions of Case 1}
\label{tbl:dimensions-1}
\end{table}
At first it will be observed how the algorithms perform under different browsers. The chart to use for this is the "Simplify.js vs Simplify.wasm" chart. For that a Windows system was chosen as it allows to run benchmarks under three of the four browsers in question. The dataset is the Simplify.js example which will be simplified with and without the high quality mode.
@ -53,8 +53,8 @@ Interestingly, in the Edge browser the two JavaScript algorithms perform more al
\begin{table}[!htb]
\centering
\includegraphics[width=.75\linewidth]{./images/dimensions-2.png}
\label{tbl:dimensions-2}
\caption{Problem dimensions of Case 2}
\label{tbl:dimensions-2}
\end{table}
@ -76,8 +76,8 @@ In the case of high quality disabled, the results show a very steep curve of the
\begin{table}[!htb]
\centering
\includegraphics[width=.75\linewidth]{./images/dimensions-3.png}
\label{tbl:dimensions-3}
\caption{Problem dimensions of Case 3}
\label{tbl:dimensions-3}
\end{table}
A 2018 MacBook Pro 15" will be used to test the safari browser. For comparison the benchmarks will also be held under Firefox on MacOS. This time the bavarian boundary will be simplified with both preprocessing enabled and disabled.
@ -101,8 +101,8 @@ When turning on high quality mode the JavaScript implementations still perform a
\begin{table}[!htb]
\centering
\includegraphics[width=.75\linewidth]{./images/dimensions-4.png}
\label{tbl:dimensions-4}
\caption{Problem dimensions of Case 4}
\label{tbl:dimensions-4}
\end{table}
In this case the system is a Lenovo Miix 510 convertible with Ubuntu 19.04 as the operating system. Again the bavarian outline is used for simplification with both quality settings. It will be observed if the Turf.js implementation is reasonable. The third kind of chart is in use here, which is similar to the Simplify.wasm insights. There are also stacked bar charts used to visualize the time spans of subtasks. The results will be compared to the graphs of the Simplify.js vs. Simplify.wasm chart. As the Turf.js method only makes sense when the original version is faster than the alternative, the benchmarks are performed in the Firefox browser.
@ -124,8 +124,8 @@ The next two figures show the case when high quality is disabled. In figure \ref
\begin{table}[!htb]
\centering
\includegraphics[width=.75\linewidth]{./images/dimensions-5.png}
\label{tbl:dimensions-5}
\caption{Problem dimensions of Case 5}
\label{tbl:dimensions-5}
\end{table}
At last the results from a mobile device are shown. The device is an iPad Air with iOS version 12.4. The Simplify.js example is being generalized using Safari and the Firefox browser. Again both quality settings are used for the benchmarks.

BIN
thesis/main.pdf
View File

Binary file not shown.