Commit before SF changes

This commit is contained in:
jfmcarreira committed 2018-09-03 02:03:59 +01:00
1 parent 594357af56
commit 8fb90680d2
10 files changed
+270 -280

No files matched your search

@@ -6,7 +6,7 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% CHAPTER
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\chapter{Error robustness of HEVC - Evaluation and improvements}
\chapter{Error robustness of HEVC - Evaluation and improvements \VERSION{1}}
\label{Chapter:HEVCErrorResilience}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -103,7 +103,8 @@ In the first set of experiments the impact of the maximum \ac{cu} size in the de
Table~\ref{Table3:Quality_BlockSize} shows the average \ac{psnr} obtained for the three test conditions and for four different packet loss ratios. Results for the error-free scenario shows a consistent quality increase as the maximum \ac{cu} size increases, up to a maximum of 1.41 dB for the Tennis sequence when comparing the maximum \ac{cu} size of $64\times64$ with $16\times16$.
This confirms the principle used by the \ac{hevc} standard, that allowing larger coding units lead to higher coding efficiency, achieving a maximum of 1.41~dB for the Tennis sequence which has the higher \ac{ti} parameter (see Table~\ref{TableTestSequences}). Moreover, it is also noticeable that sequences with higher amount of inter-coded blocks take less advantage of the larger \acs{cu}, by the results of the BQSquare sequence (i.e., highest ratio of inter-coded blocks and lowest quality gain in the error-free case).
Overall, comparing the results for the error-free and data loss cases it is noticeable that similar quality gains are obtained, which are achieved due to the superior coding efficiency of larger \acs{cu}. In most of the cases the quality gains slightly decrease for increasing \acs{plr}.
Therefore, one may conclude that the error robustness of \ac{hevc} streams is not affected by limiting the maximum \ac{cu} size. \todo{Complete discussion of partition unit size}
Therefore, one may conclude that the error robustness of \ac{hevc} streams is not affected by limiting the maximum \ac{cu} size.
%\todo{Complete discussion of partition unit size}
%Results for the case of data loss indicate that using larger coding units leads to higher video quality.
@@ -171,7 +172,7 @@ Figure~\ref{Figure3:QualityvsIntra} shows the average decoded video quality (\ac
Results in the figure indicate that as the distance between intra frames increases, the decoded video quality significantly decreases.
The quality decreasing is especially noticeable for intra periods higher than 32 frames, indicating that temporal distances greater than approximately one second are not suitable for video streaming under error-prone conditions.
When a high temporal distance between intra frames is used, the quality decreasing is more noticeable in the People On Street and BQSquare sequences, which have higher spatial complexity (see values for \ac{si}), leading to a reduction of 13 dB and 14 dB, respectively. As spatial complexity increases the encoder rely more on temporal predictions making the bitstream more prone to error propagation.
\todo{Complete discussion of intra refreshing}
%\todo{Complete discussion of intra refreshing}
One should also note from the results of Figure~\ref{Figure3:QualityvsIntra} that using a small distance between intra frames is not always more efficient.
Since intra frames require higher amount of bits, the overall coding efficiency is reduced, resulting in an overall quality that decreases even in data loss conditions.
@@ -182,8 +183,7 @@ For the remaining sequences it can be concluded that using sixteen frames (not h
The partitioning of the \acs{ctu} into different slices increase the flexibility of video streams to be partitioned into different packets, thus adapting them to the video transmission system.
By partitioning the coded video frame into different slices spatial refresh points are introduced, limiting the error propagation across different \acs{ctu}.
In this sub-section the amount of bits per slice is evaluated, in order to evaluate the influence of different schemes on the error robustness of \ac{hevc} streams. The quality obtained different mode is compared in order to find the most efficient that suits for video transmission under data loss conditions.
%As a reference for comparison a single slice per frame is also evaluated.
In this sub-section the amount of bytes per slice is evaluated, in order to evaluate the influence of different schemes on the error robustness of \ac{hevc} streams. The quality obtained different mode is compared in order to find the most efficient that suits for video transmission under data loss conditions.
\begin{figure}[!t]
\centering
@@ -194,15 +194,18 @@ In this sub-section the amount of bits per slice is evaluated, in order to evalu
\label{Figure3:SlicePartitioning}
\end{figure}
Figure~\ref{Figure3:SlicePartitioning} shows the average \ac{psnr} for three difference slice partitioning modes and different \acs{plr}.
The first mode uses a single slice per frame, corresponding to the case where slice partitioning is disabled.
The two remaining are characterised by a different amount of bits per slice, namely 1200 and 2400 bytes per slice, respectively. In these two cases each frame has a variable number of slices.
\todo{Complete discussion of slice partitioning}
Figure~\ref{Figure3:SlicePartitioning} shows the average \ac{psnr} for four difference slice partitioning modes and different \acs{plr}.
The first three modes are characterised by a different amount of bytes per slice (B/S), namely 1200, 2400 and 4800 bytes, respectively. In these cases each frame has a variable number of slices.
The last mode uses a single slice per frame (referred to as \textit{SS}), corresponding to the case where slice partitioning is disabled.
Results in the figure reveals a clear impact of the slice partitioning mode on the error robustness of the \ac{hevc}, as the quality degradation for increasing \ac{plr} significantly changes for each mode.
Comparing the cases with fixed amount of bytes per slice, it is clearly noticeable that when higher amount of bytes are used the quality degradation increases. This is true for the results of most of the test sequences shown in Figure~\ref{Figure3:SlicePartitioning}.
Although the use of smaller slices increases the overhead used for slice headers, the superior error robustness of achieved with 1200 B/S is able to overcome the inherent degradation on coding efficiency.
This is due to the lack of refresh points within a frame, resulting in errors that affects larger regions of the frame which are propagated to the subsequent inter predicted frames.
Results reveals a clear impact of the slice partitioning on the error robustness of the \ac{hevc}, as the quality degradation as the \ac{plr} increases varies for each scheme.
Firstly it is clearly notice the disadvantage of using a single slice per frame as it leads to the lower quality when comparing the test cases studied. This is due to the lack of refresh points within a frame, resulting in loss events that affects the whole frame which will propagate to the subsequent inter predicted frames.
Secondly, comparing slices of different sizes, i.e., comparing the use of 1200 and 2400 bytes per slice, reveals that using small slices leads to higher quality which is able to overcome the inherent degradation on coding efficiency due to higher amount of slice headers.
The results for of \textit{SS} (slice partitioning disabled) also reveals that this approach also leads to lower error robustness when comparing with those cases where the frames are divided into multiple slices. Although higher coding efficiency is achieved in this mode the lower error robustness leads to an overall poor performance under frame or slice loss conditions.
Results for Kendo sequence does not follow the main trend. This can be explained by the low bitrate required to compress the video signal, which is the lowest comparing with the other test sequences (see \ref{TableTestSequences}). Therefore, most of the inter-coded frames are able to transmitted using a single slice even with 1200 bytes per slice, resulting in a similar partitioning for all tested modes, and thus similar error robustness. In this case, the higher coding efficiency achieved by the \textit{SS} case consequently leads to higher quality in case of errors.
%\todo{Complete discussion of slice partitioning}
\subsection{Motion vector coding impact on error propagation}
@@ -212,47 +215,44 @@ Therefore, in this sub-section the impact of using spatial and temporal \ac{mv}
\subsubsection{Spatial \ac{mv} candidates}
\begin{figure}[!t]
\centering
\renewcommand{\FIGSIZE}{0.75\textwidth}
\input{031_ErrorResilienceEvaluation/QualityEvaluation/PSNRvsMergeCand.tex}
\caption{Average quality using different number of \ac{mv} candidates.}
\label{Figure3:AvgPSNRMergeCandidates}
\end{figure}
The first set of experiments aimed to investigate the impact of the amount of spatial \ac{mv} candidates in the video quality.
As mentioned before, \ac{hevc} allows up to five candidates to be used, which can be provided solely by spatial neighbours. In order to check the impact of the \ac{mv} candidates, different coding configurations were used, each one characterised by different amounts of spatial \ac{mv} candidates, i.e., 1, 3 and 5 \acs{mv}.
\begin{figure}[!t]
\centering
\renewcommand{\FIGSIZE}{0.75\textwidth}
\input{031_ErrorResilienceEvaluation/QualityEvaluation/PSNRvsMergeCand.tex}
\caption{Average quality using different number of \ac{mv} candidates.}
\label{Figure3:AvgPSNRMergeCandidates}
\end{figure}
Figure~\ref{Figure3:AvgPSNRMergeCandidates} shows the average quality results for the Basketball Drill and People On Street sequences under different packet loss conditions.
The results show that, besides the number of \ac{mv} candidates, similar quality decreasing is achieved as the \ac{plr} increases. Therefore, one may conclude that varying the number of available \ac{mv} candidate does not affect the error resilience of the \ac{hevc}.
\begin{table}[!t]
\newcommand{\somespaces}{}
\newcommand{\colwidth}{1.8cm}
\centering
\caption{Relation between the number of available \ac{mv} candidates and its usage} \label{Table3:MergeIdxRatio}
\footnotesize
\TABLESVSPACE
\begin{tabular}{x{3.3cm}|x{\colwidth}|x{\colwidth}|x{\colwidth}|x{\colwidth}|x{\colwidth}}
\toprule
\multirow{2}{*}{\vbox{\centering \textbf{Max. number of candidates}}} & \multicolumn{5}{c}{\textbf{Candidate selected (ratio)}} \\
\cline{2-6}
& 1 & 2 & 3 & 4 & 5 \\
\hline
3 \acs{mv} & $66.17\%$ & 22.79$\%$ & 11.04$\%$ & - & - \\
\hline
5 \acs{mv} & 64.54$\%$ & 22.24$\%$ & 7.38$\%$ & 3.37$\%$ & 2.47$\%$ \\
\bottomrule
\end{tabular}
\end{table}
The occurrence rate for each spatial \ac{mv} candidate was analysed in order to check whether they are uniformly used.
Table~\ref{Table3:MergeIdxRatio} shows the usage percentage of each \ac{mv} candidate when three and five candidates are available, for the slice partitioning mode of 1200 bytes/slice. The results indicate that most predictions use the first candidate and minor differences occur by adding 2 or more \acs{mv}.
Since the mostly used \ac{mv} candidates are the initial ones, changing the number of available candidates does not significantly affects the error resilience.
Moreover, the slice partitioning mode used only 1200 bytes per slice, which introduces refresh points in each frame, reducing the spatial error propagation due to mismatched \ac{mv} predictions.
\begin{table}[tb]
\newcommand{\somespaces}{}
\newcommand{\colwidth}{1.8cm}
\centering
\caption{Relation between the number of available \ac{mv} candidates and its usage} \label{Table3:MergeIdxRatio}
\footnotesize
\TABLESVSPACE
\begin{tabular}{x{3.3cm}|x{\colwidth}|x{\colwidth}|x{\colwidth}|x{\colwidth}|x{\colwidth}}
\toprule
\multirow{2}{*}{\vbox{\centering \textbf{Max. number of candidates}}} & \multicolumn{5}{c}{\textbf{Candidate selected (ratio)}} \\
\cline{2-6}
& 1 & 2 & 3 & 4 & 5 \\
\hline
3 \acs{mv} & $66.17\%$ & 22.79$\%$ & 11.04$\%$ & - & - \\
\hline
5 \acs{mv} & 64.54$\%$ & 22.24$\%$ & 7.38$\%$ & 3.37$\%$ & 2.47$\%$ \\
\bottomrule
\end{tabular}
\end{table}
\subsubsection{Temporal \ac{mv} candidates}
@@ -292,7 +292,7 @@ Moreover, the results also indicate that for higher loss ratios the negative imp
\input{./031_ErrorResilienceEvaluation/QualityEvaluation/TableMVPs.tex}
\end{table}
\subsection{Discussion}
\subsection{Remarks}
Overall, the results presented in the previous sub-sections show that \ac{hevc} has poor robustness against transmission errors, resulting in significant quality degradation, though dependent still on the video content and coding options.
As shown, some coding options, such as slice partition and intra refreshing period, have high correlation with the decoded video quality when transmission errors affect the compressed streams.
@@ -1,5 +1,5 @@
\newcommand{\pltw}{0.75\columnwidth}
\newcommand{\plth}{0.5\textheight}
\newcommand{\plth}{0.4\textheight}
\begin{gnuplot}[terminal=epslatex,terminaloptions={monochrome font ",\PlotFont" size \convertlen{\pltw},\convertlen{\plth}}]
load 'carreira_phd_thesis_gnuplot_template.cfg'
@@ -1,156 +1,97 @@
\newcommand{\ft}[0]{\footnotesize}
\newcommand{\pltw}{\columnwidth}
\newcommand{\plth}{0.6\textheight}
\newcommand{\plth}{0.7\textheight}
\begin{gnuplot}[terminal=epslatex,terminaloptions={monochrome font ",\PlotFont" size \convertlen{\pltw},\convertlen{\plth}}]
load 'carreira_phd_thesis_gnuplot_template.cfg'
set multiplot layout 3,2
set key width -3
set key width -1
set yrange[28:42]
set ytics 0,2,60
set title '\TitleFont Basketball Drill'
plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
0.0 40.080
1.0 39.198
3.0 37.351
5.0 35.953
10.0 33.024
e
0.0 39.900
1.0 38.462
3.0 36.705
5.0 35.526
10.0 33.680
e
0.0 39.970
1.0 37.988
3.0 34.884
5.0 32.921
10.0 29.059
e
# set title '\TitleFont Book Arrival'
# set yrange[28:42]
# set ytics 0,2,60
# set title '\TitleFont Basketball Drill'
# plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
# 0.0 40.390
# 1.0 39.635
# 3.0 37.954
# 5.0 36.821
# 10.0 34.185
# 0.0 40.080
# 1.0 39.198
# 3.0 37.351
# 5.0 35.953
# 10.0 33.024
# e
# 0.0 40.280
# 1.0 38.818
# 3.0 36.334
# 5.0 34.694
# 10.0 31.357
# 0.0 39.900
# 1.0 38.462
# 3.0 36.705
# 5.0 35.526
# 10.0 33.680
# e
# 0.0 40.320
# 1.0 39.093
# 3.0 36.939
# 5.0 34.280
# 10.0 30.948
# 0.0 39.970
# 1.0 37.988
# 3.0 34.884
# 5.0 32.921
# 10.0 29.059
# e
set yrange[31:41]
set ytics 31,2,60
set title '\TitleFont BQSquare'
plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
0.0 39.430
1.0 38.946
3.0 37.851
5.0 36.991
10.0 35.078
# set yrange[31:41]
# set ytics 31,2,60
# set title '\TitleFont BQSquare'
# plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
# 0.0 39.430
# 1.0 38.946
# 3.0 37.851
# 5.0 36.991
# 10.0 35.078
# e
# 0.0 39.300
# 1.0 38.486
# 3.0 36.973
# 5.0 35.779
# 10.0 33.624
# e
# 0.0 39.350
# 1.0 38.468
# 3.0 36.429
# 5.0 34.475
# 10.0 31.059
# e
set yrange[30:42]
set ytics 30,2,60
set title '\TitleFont Kendo'
plot '-' using 1:2 title '\KeyFont 1200 B/S' w lp ls 1, '-' using 1:2 title '\KeyFont 2400 B/S' w lp ls 2, '-' using 1:2 title '\KeyFont 4800 B/S' w lp ls 3, '-' using 1:2 title '\KeyFont SS' w lp ls 4
0.0 41.150
1.0 39.809
3.0 37.264
5.0 34.900
10.0 30.713
e
0.0 39.300
1.0 38.486
3.0 36.973
5.0 35.779
10.0 33.624
0.0 41.240
1.0 40.124
3.0 37.752
5.0 35.788
10.0 32.144
e
0.0 39.350
1.0 38.468
3.0 36.429
5.0 34.475
10.0 31.059
0.0 41.290
1.0 40.297
3.0 38.161
5.0 36.641
10.0 33.139
e
0.0 41.320
1.0 40.405
3.0 38.475
5.0 37.084
10.0 34.076
e
# set title '\TitleFont Cactus'
# plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
# 0.0 38.060
# 1.0 37.545
# 3.0 36.519
# 5.0 35.651
# 10.0 33.521
# e
# 0.0 38.000
# 1.0 37.707
# 3.0 37.400
# 5.0 37.270
# 10.0 36.930
# e
# 0.0 38.030
# 1.0 37.719
# 3.0 37.329
# 5.0 37.122
# 10.0 36.666
# e
# set title '\TitleFont Four People'
# plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
# 0.0 40.270
# 1.0 40.081
# 3.0 39.678
# 5.0 39.272
# 10.0 38.230
# e
# 0.0 40.130
# 1.0 39.862
# 3.0 39.406
# 5.0 39.005
# 10.0 38.115
# e
# 0.0 40.180
# 1.0 39.947
# 3.0 39.328
# 5.0 38.753
# 10.0 37.494
# e
# set title '\TitleFont Kendo'
# plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
# 0.0 41.320
# 1.0 40.405
# 3.0 38.475
# 5.0 37.084
# 10.0 34.076
# e
# 0.0 41.150
# 1.0 39.809
# 3.0 37.264
# 5.0 34.900
# 10.0 30.713
# e
# 0.0 41.240
# 1.0 40.124
# 3.0 37.752
# 5.0 35.788
# 10.0 32.144
# e
set yrange[36:44]
set ytics 36,2,60
# unset yrange
# unset ytics
set yrange[36.5:43.5]
set ytics 37,1,60
set title '\TitleFont Kimono'
plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
0.0 42.940
1.0 42.180
3.0 40.589
5.0 39.315
10.0 36.789
e
plot '-' using 1:2 title '\KeyFont 1200 B/S' w lp ls 1, '-' using 1:2 title '\KeyFont 2400 B/S' w lp ls 2, '-' using 1:2 title '\KeyFont 4800 B/S' w lp ls 3, '-' using 1:2 title '\KeyFont SS' w lp ls 4
0.0 42.880
1.0 42.247
3.0 41.587
@@ -163,6 +104,18 @@ e
5.0 40.650
10.0 39.841
e
0.0 42.910
1.0 42.001
3.0 40.519
5.0 39.585
10.0 38.254
e
0.0 42.940
1.0 42.180
3.0 40.589
5.0 39.315
10.0 36.789
e
# set title '\TitleFont Kristen Sara'
@@ -186,16 +139,10 @@ e
# 10.0 38.111
# e
set yrange[34:42]
set ytics 34,2,60
set yrange[34:41]
set ytics 34,1,60
set title '\TitleFont Park Scene'
plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
0.0 39.570
1.0 39.033
3.0 37.859
5.0 36.923
10.0 34.945
e
plot '-' using 1:2 title '\KeyFont 1200 B/S' w lp ls 1, '-' using 1:2 title '\KeyFont 2400 B/S' w lp ls 2, '-' using 1:2 title '\KeyFont 4800 B/S' w lp ls 3, '-' using 1:2 title '\KeyFont SS' w lp ls 4
0.0 39.470
1.0 38.905
3.0 38.385
@@ -208,17 +155,23 @@ e
5.0 37.856
10.0 37.133
e
set yrange[29:37]
set ytics 29,2,60
set title '\TitleFont People On Street'
plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
0.0 36.140
1.0 35.257
3.0 33.619
5.0 32.391
10.0 29.845
0.0 39.530
1.0 38.806
3.0 37.747
5.0 37.014
10.0 35.329
e
0.0 39.570
1.0 39.033
3.0 37.859
5.0 36.923
10.0 34.945
e
set yrange[28:36.5]
set ytics 28,2,60
set title '\TitleFont People On Street'
plot '-' using 1:2 title '\KeyFont 1200 B/S' w lp ls 1, '-' using 1:2 title '\KeyFont 2400 B/S' w lp ls 2, '-' using 1:2 title '\KeyFont 4800 B/S' w lp ls 3, '-' using 1:2 title '\KeyFont SS' w lp ls 4
0.0 35.900
1.0 34.736
3.0 33.795
@@ -231,17 +184,23 @@ e
5.0 32.490
10.0 31.323
e
0.0 36.030
1.0 34.236
3.0 31.765
5.0 30.494
10.0 28.042
e
0.0 36.140
1.0 35.257
3.0 33.619
5.0 32.391
10.0 29.845
e
set yrange[30:42]
set yrange[30:40.5]
set ytics 30,2,60
set title '\TitleFont Race Horses'
plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
0.0 40.030
1.0 38.846
3.0 36.403
5.0 34.608
10.0 30.944
e
plot '-' using 1:2 title '\KeyFont 1200 B/S' w lp ls 1, '-' using 1:2 title '\KeyFont 2400 B/S' w lp ls 2, '-' using 1:2 title '\KeyFont 4800 B/S' w lp ls 3, '-' using 1:2 title '\KeyFont SS' w lp ls 4
0.0 39.870
1.0 38.724
3.0 37.661
@@ -254,30 +213,47 @@ e
5.0 35.580
10.0 34.204
e
0.0 39.960
1.0 37.729
3.0 34.768
5.0 32.972
10.0 30.390
e
0.0 40.030
1.0 38.846
3.0 36.403
5.0 34.608
10.0 30.944
e
#
# set title '\TitleFont Tennis'
# plot '-' using 1:2 title '\KeyFont Single Slice/Frame' w lp ls 1, '-' using 1:2 title '\KeyFont 1200 Bytes/Slice' w lp ls 2, '-' using 1:2 title '\KeyFont 2400 Bytes/Slice' w lp ls 3
# 0.0 40.900
# 1.0 39.773
# 3.0 37.491
# 5.0 35.896
# 10.0 32.303
# e
# 0.0 40.680
# 1.0 39.242
# 3.0 37.515
# 5.0 36.545
# 10.0 35.064
# e
# 0.0 40.770
# 1.0 38.369
# 3.0 35.105
# 5.0 33.079
# 10.0 29.667
# e
set yrange[27:42]
set ytics 27,2,60
set title '\TitleFont Tennis'
plot '-' using 1:2 title '\KeyFont 1200 B/S' w lp ls 1, '-' using 1:2 title '\KeyFont 2400 B/S' w lp ls 2, '-' using 1:2 title '\KeyFont 4800 B/S' w lp ls 3, '-' using 1:2 title '\KeyFont SS' w lp ls 4
0.0 40.680
1.0 39.242
3.0 37.515
5.0 36.545
10.0 35.064
e
0.0 40.770
1.0 38.369
3.0 35.105
5.0 33.079
10.0 29.667
e
0.0 40.830
1.0 38.307
3.0 34.743
5.0 32.276
10.0 27.524
e
0.0 40.900
1.0 39.773
3.0 37.491
5.0 35.896
10.0 32.303
e
\end{gnuplot}