Skip to content

Commit 9ba0d72

Browse files
committed
doc update
1 parent 6a70f00 commit 9ba0d72

File tree

8 files changed

+112
-10
lines changed

8 files changed

+112
-10
lines changed
5.04 KB
Loading
86.1 KB
Loading
5.43 KB
Loading
14.3 KB
Loading

doc/user_manual/eval/eval_requirements.tex

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,98 @@ \subsubsection{Result Values}
8181
\end{table}
8282
\end{center}
8383

84+
85+
\subsection{Dubious Tracks}
86+
\label{sec:eval_req_dubious_tracks}
87+
88+
\subsubsection{Configuration}
89+
90+
\begin{figure}[H]
91+
\includegraphics[width=14cm,frame]{../screenshots/eval_req_dubious_tracks.png}
92+
\caption{Evaluation Dubious Tracks}
93+
\end{figure}
94+
95+
The 'Dubious Tracks' requirement can be used to check for dubious tracks generated by a \textbf{Tracker} data-source (using the attributed track number). This requirement checks based on test data only, so the reference data is of no importance. \\
96+
97+
For each track number (existing in an UTN) a number of checks are performed, and a probability of dubious target report is caluclated. Which checks are used can be defined as follows, but are focused on short tracks or physically dubious movement. \\
98+
99+
\begin{itemize}
100+
\item Probability [1]: Probability of dubious track
101+
\item Probability Check Type: $\geq$
102+
\item Use only from L.U. Sensor: Checkbox if only data from a single last-updating sensor id should be considered
103+
\item L.U. Sensor [1]: Last-updating sensor id (number, as in the 'Manage Data-Sources' task)
104+
\item Minimum Comparison Time [s]: Skip movement checks if time between updates is smaller than the defined time
105+
\item Maximum Comparison Time [s]: Skip movement checks if time between updates is larger than the defined time
106+
\item Mark Primary-Only: Checkbox if all primary-only tracks should be counted as dubious
107+
\item Use Minimum Updates: Checkbox if tracks with less than the defined number of updates should be counted as dubious
108+
\item Minimum Updates [1]: Minimum number of updates
109+
\item Use Minimum Duration: Checkbox if tracks with a duration less than the defined time should be counted as dubious
110+
\item Minimum Duration [s]: Minimum duration
111+
\item Use Maximum Groundspeed: Checkbox if maximum groundspeed should be used
112+
\item Maximum Groundspeed [kts]: Maximum groundspeed to be considered
113+
\item Use Maximum Acceleration: Checkbox if maximum acceleration should be used
114+
\item Maximum Acceleration [$m/s^{2}$]: Maximum acceleration to be considered
115+
\item Use Maximum Turnrate: Checkbox if maximum turnrate should be used
116+
\item Turnrate Groundspeed [deg/s]: Maximum groundspeed to be considered
117+
\item Use Maximum ROCD: Checkbox if turnrate rate of climb/descent should be used
118+
\item Maximum ROCD [ft/s]: Maximum rate of climb/descent to be considered
119+
\item Dubious Probability [1]: Probability of dubious target report to classify a track as dubious
120+
\end{itemize}
121+
\ \\
122+
123+
\subsubsection{Calculation}
124+
125+
As a summary, the reference is used to calculate the number of expected update intervals inside the sector layer (\#EUI). Then, for the test data, if the reference exists at the time, time differences between target reports are checked and the number of misses/gaps are calculated as number of missed update intervals (\#MUI). \\
126+
127+
Gaps are, if a minimum or maximum gap length is used, only counted if the detected gap fulfills the thresholds. \\
128+
129+
The ratio of \#MUI and \#EUI gives the probability of missed update interval, the counter-probability gives the Probability of Detection (PD). The PD must greator or equal than the defined 'Probability' for the requirement to pass.
130+
131+
\subsubsection{Result Values}
132+
133+
\paragraph{Sector}
134+
135+
\begin{center}
136+
\begin{table}[H]
137+
\begin{tabularx}{\textwidth}{ | l | X | l | }
138+
\hline
139+
\textbf{Name} & \textbf{Description} & \textbf{Example} \\ \hline
140+
Sector Layer & Name of the sector layer & fir\_cut\_sim \\ \hline
141+
Reqirement Group & Name of the requirement group & Mandatory \\ \hline
142+
Reqirement & Name of the requirement & Detection \\ \hline
143+
Num Results & Total number of results & 728 \\ \hline
144+
Num Usable Results & Number of usable results & 417 \\ \hline
145+
Num Unusable Results & Number of unusable results & 311 \\ \hline
146+
\#Updates/\#EUIs [1] & Total number update intervals & 7960 \\ \hline
147+
\#MUIs [1] & Number of missed update intervals & 2221 \\ \hline
148+
PD [\%] & Probability of Detection & 72.10 \\ \hline
149+
Condition & & >= 90.00 \\ \hline
150+
Condition Fulfilled & & Failed \\ \hline
151+
\end{tabularx}
152+
\end{table}
153+
\end{center}
154+
155+
Also, a table is given for all single targets, sorted by PD.
156+
157+
\paragraph{Single Target}
158+
159+
\begin{center}
160+
\begin{table}[H]
161+
\begin{tabularx}{\textwidth}{ | l | X | l | }
162+
\hline
163+
\textbf{Name} & \textbf{Description} & \textbf{Example} \\ \hline
164+
Use & To be used in results & true \\ \hline
165+
\#EUIs [1] & Expected Update Intervals & 6 \\ \hline
166+
\#MUIs [1] & Missed Update Intervals & 5 \\ \hline
167+
PD [\%] & Probability of Detection & 16.67 \\ \hline
168+
Reference Period 0 & Time inside sector & [15:47:22.680,15:47:45.828] \\ \hline
169+
Reference Period 1 & Time inside sector & [15:47:53.844,15:47:57.844] \\ \hline
170+
Condition & & >= 90.00 \\ \hline
171+
Condition Fulfilled & & Failed \\ \hline
172+
\end{tabularx}
173+
\end{table}
174+
\end{center}
175+
84176
\subsection{Extra Data}
85177
\label{sec:eval_req_extra_data}
86178

doc/user_manual/eval/evaluation.tex

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -176,6 +176,8 @@ \subsection{Targets Tab}
176176
\caption{Evaluation Targets tab with loaded data}
177177
\end{figure}
178178

179+
180+
179181
\subsection{Filter Tab}
180182

181183
\begin{figure}[H]
@@ -389,6 +391,7 @@ \subsection{Filtering Targets}
389391
\item Remove Primary-Only Targets: Removes primary-only targets (w/o secondary attributes)
390392
\item Remove Mode A/C Code onlys: Removes targets without Mode S attributes
391393
\item Remove by Mode A Code: Removes targets having a Mode A code given in the list
394+
\item Remove by Mode C Code: Removes targets having a Mode C code smaller than the given value
392395
\item Remove by Target Address: Removes targets having a Mode S target address given in the list
393396
\item Remove by Non-Detection of DBObject: Removes targets not being detected by a given DBOObject (e.g. sensor type)
394397
\end{itemize}

doc/user_manual/osg/osg_style_tab.tex

Lines changed: 16 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ \subsection{Style Tab}
33

44
\begin{figure}[H]
55
\center
6-
\includegraphics[width=9cm,frame]{../screenshots/osgview_style_tab.png}
6+
\includegraphics[width=8cm,frame]{../screenshots/osgview_style_tab.png}
77
\caption{OSG View Style tab}
88
\end{figure}
99

@@ -265,18 +265,25 @@ \subsubsection{Style Examples}
265265

266266
\subsubsection{Render Order}
267267

268-
In the render order widget, the drawing order of all DBObjects is specified. The one at the top is drawn last (over all others), so it is useful to move the most important DBObject (for the current inspection) to the top.
268+
In the render order widget, the drawing order of the drawn geometry is specified. The one at the top is drawn last (over all others), so it is useful to move the most important DBObject (for the current inspection) to the top.
269269

270270
\begin{figure}[H]
271-
\includegraphics[width=10cm,frame]{../screenshots/osgview_render_order.png}
271+
\includegraphics[width=8cm,frame]{../screenshots/osgview_render_order.png}
272272
\caption{OSG View render order}
273273
\end{figure}
274274

275-
To change the drawing order click on the DBObject to move and use the buttons on the right side. Please note that no redraw is required and that the drawing order is persisted in the configuration.
276-
%
275+
Using the 'Order By' checkbox, the drawing order can be defined based on:
276+
\begin{itemize}
277+
\item DBObject: Data-source type (e.g. Tracker, Radar, ...)
278+
\item ds\_id: Data-source (e.g. Tracker1, Tracker2, Radar3, ...)
279+
\end{itemize}
280+
\ \\
281+
282+
To change the drawing order click on the item to move and use the buttons on the right side. Please note that no redraw is required and that the drawing order is persisted in the configuration. \\
283+
277284
\begin{itemize}
278-
\item \includegraphics[width=0.5cm]{../../data/icons/top.png} Move to Top: Move DBO to top position
279-
\item \includegraphics[width=0.5cm]{../../data/icons/up.png} Move Up: Move DBO one position up
280-
\item \includegraphics[width=0.5cm]{../../data/icons/down.png} Move Down: Move DBO one position down
281-
\item \includegraphics[width=0.5cm]{../../data/icons/bottom.png} Move to Bottom: Move DBO to the bottom position
285+
\item \includegraphics[width=0.5cm]{../../data/icons/top.png} Move to Top: Move item to top position
286+
\item \includegraphics[width=0.5cm]{../../data/icons/up.png} Move Up: Move item one position up
287+
\item \includegraphics[width=0.5cm]{../../data/icons/down.png} Move Down: Move item one position down
288+
\item \includegraphics[width=0.5cm]{../../data/icons/bottom.png} Move to Bottom: Move item to the bottom position
282289
\end{itemize}

doc/user_manual/user_manual.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@
225225
\begin{center}
226226
\normalsize\textsf{by Helmut Puhr}\par
227227
\medskip
228-
\normalsize\textsf{Version 0.6.2 \textit{Tenacious Tapir}}\par\textsf{Alpha Release}\par
228+
\normalsize\textsf{Version 0.6.3 \textit{Ubiquitous Unicorn}}\par\textsf{Alpha Release}\par
229229
\end{center}
230230
\vspace*{\fill}
231231
\begin{center}

0 commit comments

Comments
 (0)