aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/introduction/methodology_plrsearch.rst
diff options
context:
space:
mode:
authorVratko Polak <vrpolak@cisco.com>2019-02-15 13:03:23 +0100
committerTibor Frank <tifrank@cisco.com>2019-02-15 13:25:38 +0000
commitc123e1590b7de379db10124c9d6d32bd2e20e848 (patch)
tree145bdf123bc6e1bc7822d7e5255ef1e2bcfd1fbc /docs/report/introduction/methodology_plrsearch.rst
parentf70e219c1231fd95a59a60a8e41ae3d8f59b512d (diff)
Improve PLRsearch graphical example
+ Two graphs now. + Larger font in graphs. + More descriptions within graphs. + Text before graphs explaining what is shown. Change-Id: I1da6b55abe7380b61988e03d83f34f7f991085d6 Signed-off-by: Vratko Polak <vrpolak@cisco.com> (cherry picked from commit cc5914d182053c300785771860424ae2d76a50c9)
Diffstat (limited to 'docs/report/introduction/methodology_plrsearch.rst')
-rw-r--r--docs/report/introduction/methodology_plrsearch.rst56
1 files changed, 47 insertions, 9 deletions
diff --git a/docs/report/introduction/methodology_plrsearch.rst b/docs/report/introduction/methodology_plrsearch.rst
index 7529acae6e..65ac590222 100644
--- a/docs/report/introduction/methodology_plrsearch.rst
+++ b/docs/report/introduction/methodology_plrsearch.rst
@@ -338,12 +338,50 @@ as the observed trends have varied characteristics.
Probably, using a more realistic fitting functions
will give better estimates than trend analysis.
-Graphical example
-`````````````````
+Graphical examples
+``````````````````
+
+The following pictures show the upper and lower bound (one sigma)
+on estimated critical rate, as computed by PLRsearch, after each trial measurement
+within the 30 minute duration of a test run.
+
+Both graphs are focusing on later estimates. Estimates computed from
+few initial measurements are wildly off the y-axis range shown.
+
+L2 patch
+--------
+
+This test case shows quite narrow critical region. Both fitting functions
+give similar estimates, the graph shows the randomness of measurements,
+and a trend. Both fitting functions seem to be somewhat overestimating
+the critical rate. The final estimated interval is too narrow,
+a longer run would report estimates somewhat bellow the current lower bound.
+
+.. only:: latex
+
+ .. raw:: latex
+
+ \begin{figure}[H]
+ \centering
+ \graphicspath{{../_tmp/src/introduction/}}
+ \includegraphics[width=0.90\textwidth]{PLR_patch}
+ \label{fig:PLR_patch}
+ \end{figure}
+
+.. only:: html
+
+ .. figure:: PLR_patch.svg
+ :alt: PLR_patch
+ :align: center
+
+Vhost
+-----
-The following picture shows the estimated average of the critical rate
-computed by the two fitting functions after each trial measurement
-within the 30 minute duration of a PLRsearch test run.
+This test case shows quite broad critical region. Fitting functions give
+fairly differing estimates. One overestimates, the other underestimates.
+The graph mostly shows later measurements slowly bringing the estimates
+towards each other. The final estimated interval is too broad,
+a longer run would return a smaller interval within the current one.
.. only:: latex
@@ -352,14 +390,14 @@ within the 30 minute duration of a PLRsearch test run.
\begin{figure}[H]
\centering
\graphicspath{{../_tmp/src/introduction/}}
- \includegraphics[width=0.90\textwidth]{PLRsearch}
- \label{fig:PLRsearch}
+ \includegraphics[width=0.90\textwidth]{PLR_vhost}
+ \label{fig:PLR_vhost}
\end{figure}
.. only:: html
- .. figure:: PLRsearch.svg
- :alt: PLRsearch
+ .. figure:: PLR_vhost.svg
+ :alt: PLR_vhost
:align: center
.. _plrsearch draft: https://tools.ietf.org/html/draft-vpolak-bmwg-plrsearch-00