summaryrefslogtreecommitdiffstats
path: root/notFinishedCode
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode')
-rw-r--r--notFinishedCode/Report/test.aux2
-rw-r--r--notFinishedCode/Report/test.log8
-rw-r--r--notFinishedCode/Report/test.pdfbin1490496 -> 1491362 bytes
-rw-r--r--notFinishedCode/Report/test.tex21
-rw-r--r--notFinishedCode/Report/test.tex.backup15
-rw-r--r--notFinishedCode/Report/test.tex~21
-rw-r--r--notFinishedCode/Report/test.toc2
7 files changed, 43 insertions, 26 deletions
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index b46c28b..3c28b72 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -74,7 +74,7 @@
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Results on the web page}{28}}
\citation{pChart}
\@writefile{lof}{\contentsline {figure}{\numberline {18}{\ignorespaces }}{29}}
-\@writefile{toc}{\contentsline {section}{\numberline {9}How to use and start the system}{30}}
+\@writefile{toc}{\contentsline {section}{\numberline {9}Employing the test system software}{30}}
\@writefile{toc}{\contentsline {subsection}{\numberline {9.1}Required libraries}{30}}
\@writefile{toc}{\contentsline {subsection}{\numberline {9.2}Configuring hardware}{30}}
\@writefile{toc}{\contentsline {section}{\numberline {10}Conclusion}{31}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 9213a74..d47576c 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 25 OCT 2011 15:25
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 25 OCT 2011 15:41
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -395,7 +395,7 @@ File: sshTunnel.png Graphic file (type png)
<./sshTunnel.png (PNG copy)>] [24] [25]
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 630.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 631.
[26] [27] [28]
<resultsImage.png, id=128, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
@@ -424,9 +424,9 @@ r/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></usr/share/texmf-texlive/fonts/ty
pe1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-texlive/fonts/type1/public/
amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm
/cmsy9.pfb>
-Output written on test.pdf (32 pages, 1490496 bytes).
+Output written on test.pdf (32 pages, 1491362 bytes).
PDF statistics:
- 718 PDF objects out of 1000 (max. 8388607)
+ 720 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
96 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index 7e62bcb..61c06e9 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 5dc0feb..4d0ae3b 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -333,12 +333,13 @@ It selects automatically the important tests to perform. In the next step it
tries to identify the problem in the network.
More details can be found in the \emph{smart test} description.
\subsection{Controller class}
-The controller class is used to assign jobs to handlers (e.g. which one is going to be the caller
-and callee). Simultaneously, it defines the port address for the communication between
-the handlers and controller. If the callee or the caller are nanoBTS control
-boxes (i.e. BeagleBoards outside the Rechenzentrum), it will first create an
-SSH connection to make a tunnel before the local connection is created.
-The controller class sends all the required data regarding the test task to the handler.
+The controller class is used to assign jobs to handlers (in other words, which one is
+going to be the caller and callee). Simultaneously, it defines the port addresses for
+the communication between the handlers and the main test software (controller).
+If the callee or the caller are nanoBTS control boxes (i.e. BeagleBoards outside
+the Rechenzentrum), it will first create an SSH connection to make a tunnel before
+the local socket connection is created. Then the controller class sends all the
+required data regarding the test tasks to the handlers.
\clearpage
\section{Hardware design}
@@ -696,7 +697,7 @@ where it automatically shuts down.
All the performed test results are displayed on the web site. The results are displayed in real time after each selected test case is performed.
After all the test cases have been performed a topological picture is generated which represents the current state of the system, this can bee seen in the following figure.
Afterwards, when the result picture is generated, the test user can easily see what is wrong in the system. Various icons represent different subsystems.
-Reading the test results is simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
+Reading the test results is as simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
\begin{itemize}
\item Triangles represent BTS stations
@@ -716,7 +717,11 @@ We use the pChart library\footnote{It is under the GNU GPLv3 license and our pro
\par On the right side of the result picture the test user can immediatelly identify the network operability in percentage\footnote{The test user has to take into account that this percantage is only valid if a full test is performed.}. Bellow the network operability statistics are the ping results statistics located.
If one of the fields is red it means the subsystem is not online or cannot be seen by our server computer where the test software is located.
\newpage
-\section{How to use and start the system}
+\section{Employing the test system software}
+In this section the reader can find out how to install and how to use the test system.
+Our goal was to make a multiplatform test software, however we tested it only under Ubuntu
+11.04 32 bit Linux OS and the given instruction manual is only tested under that operating
+system.
\subsection{Required libraries}
\subsection{Configuring hardware}
\newpage
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 4275db2..13066d8 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -331,7 +331,15 @@ The processed data get forwarded to the controller class and in the end the clas
fetches the results from the test. This class contains the \emph{smart test} functionality.
It selects automatically the important tests to perform. In the next step it
tries to identify the problem in the network.
-More details can be enquired in the \emph{smart test} description.
+More details can be found in the \emph{smart test} description.
+\subsection{Controller class}
+The controller class is used to assign jobs to handlers (in other words, which one is
+going to be the caller and callee). Simultaneously, it defines the port addresses for
+the communication between the handlers and the main test software (controller).
+If the callee or the caller are nanoBTS control boxes (i.e. BeagleBoards outside
+the Rechenzentrum), it will first create an SSH connection to make a tunnel before
+the local socket connection is created. Then the controller class sends all the
+required data regarding the test tasks to the handlers.
\clearpage
\section{Hardware design}
@@ -689,7 +697,7 @@ where it automatically shuts down.
All the performed test results are displayed on the web site. The results are displayed in real time after each selected test case is performed.
After all the test cases have been performed a topological picture is generated which represents the current state of the system, this can bee seen in the following figure.
Afterwards, when the result picture is generated, the test user can easily see what is wrong in the system. Various icons represent different subsystems.
-Reading the test results is simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
+Reading the test results is as simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
\begin{itemize}
\item Triangles represent BTS stations
@@ -709,7 +717,8 @@ We use the pChart library\footnote{It is under the GNU GPLv3 license and our pro
\par On the right side of the result picture the test user can immediatelly identify the network operability in percentage\footnote{The test user has to take into account that this percantage is only valid if a full test is performed.}. Bellow the network operability statistics are the ping results statistics located.
If one of the fields is red it means the subsystem is not online or cannot be seen by our server computer where the test software is located.
\newpage
-\section{How to use and start the system}
+\section{Employing the test system software}
+In this section the reader will find out how to use the test system.
\subsection{Required libraries}
\subsection{Configuring hardware}
\newpage
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 4f7c812..6e27d79 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -333,13 +333,13 @@ It selects automatically the important tests to perform. In the next step it
tries to identify the problem in the network.
More details can be found in the \emph{smart test} description.
\subsection{Controller class}
-The controller class is used to assign jobs to handlers (e.g. which one is going to be the caller
-and callee). Simultaneously, it defines the port address for the communication between
-the handlers and controller. If the callee or the caller are nanoBTS control
-boxes (i.e. BeagleBoards outside the Rechenzentrum), it will first create an
-SSH connection to make a tunnel before the local connection is created.
-Controller and handler communication is executed in this class.
-Controller will send all information regarding test to the handler. Before sending the message, controller trying to wake up the handler and assign as caller or receiver with some information regarding port address for communication and the account information.
+The controller class is used to assign jobs to handlers (in other words, which one is
+going to be the caller and callee). Simultaneously, it defines the port addresses for
+the communication between the handlers and the main test software (controller).
+If the callee or the caller are nanoBTS control boxes (i.e. BeagleBoards outside
+the Rechenzentrum), it will first create an SSH connection to make a tunnel before
+the local socket connection is created. Then the controller class sends all the
+required data regarding the test tasks to the handlers.
\clearpage
\section{Hardware design}
@@ -697,7 +697,7 @@ where it automatically shuts down.
All the performed test results are displayed on the web site. The results are displayed in real time after each selected test case is performed.
After all the test cases have been performed a topological picture is generated which represents the current state of the system, this can bee seen in the following figure.
Afterwards, when the result picture is generated, the test user can easily see what is wrong in the system. Various icons represent different subsystems.
-Reading the test results is simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
+Reading the test results is as simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
\begin{itemize}
\item Triangles represent BTS stations
@@ -717,7 +717,10 @@ We use the pChart library\footnote{It is under the GNU GPLv3 license and our pro
\par On the right side of the result picture the test user can immediatelly identify the network operability in percentage\footnote{The test user has to take into account that this percantage is only valid if a full test is performed.}. Bellow the network operability statistics are the ping results statistics located.
If one of the fields is red it means the subsystem is not online or cannot be seen by our server computer where the test software is located.
\newpage
-\section{How to use and start the system}
+\section{Employing the test system software}
+In this section the reader can find out how to install and how to use the test system.
+Our goal was to make a multiplatform test system, however we tested it only under Ubuntu
+11.04 32 bit Linux OS and the given instructions are only tested under that system.
\subsection{Required libraries}
\subsection{Configuring hardware}
\newpage
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index eaa8b3d..7e30c12 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -30,7 +30,7 @@
\contentsline {section}{\numberline {8}Web page}{28}
\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{28}
\contentsline {subsection}{\numberline {8.2}Results on the web page}{28}
-\contentsline {section}{\numberline {9}How to use and start the system}{30}
+\contentsline {section}{\numberline {9}Employing the test system software}{30}
\contentsline {subsection}{\numberline {9.1}Required libraries}{30}
\contentsline {subsection}{\numberline {9.2}Configuring hardware}{30}
\contentsline {section}{\numberline {10}Conclusion}{31}