doc update

Author: hpuhr

doc/screenshots/osgview_style_radar_detection_type.png

@@ -94,7 +94,7 @@ \subsubsection{Configuration}
 
 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. \\
 
-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. \\
+For each track number (existing in an UTN) a number of checks are performed, and a probability of dubious target report is calculated. Which checks are used can be defined as follows, but are focused on short tracks or physically dubious movement. \\
 
 \begin{itemize}  
 \item Probability [1]: Probability of dubious track
@@ -122,11 +122,30 @@ \subsubsection{Configuration}
 
 \subsubsection{Calculation}
 
-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). \\
+As a summary, the test data is used to calculate the number of dubious tracks in relation to the total number of tracks, which gives the probability of dubios track (PDT). If this probability is larger than the required one, the requirement is failed. \\
 
-Gaps are, if a minimum or maximum gap length is used, only counted if the detected gap fulfills the thresholds. \\
+A track is be ignored (from dubious detection) if the last-updating sensor parameter is active, and the track was updated by at any point by any other sensor. \\
 
-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.
+The total track updates are marked as dubious if any of the following cases hold:
+\begin{itemize}  
+\item 'Mark Primary-Only' is used, and the track is always primary-only (no secondary attributes)
+\item 'Minimum Updates' are used, and the number of track updates is smaller than the required threshold
+\item 'Minimum Duration' is used, and the duration of the track is smaller than the required threshold
+\end{itemize}
+\ \\
+
+For the movement checks, for each track update the movement is checked. If the Minimum/Maximum Comparison Time check fails, the respective track update is skipped (not checked). \\ 
+
+The following checks can be performed:
+\begin{itemize}  
+\item 'Maximum Groundspeed': The track update's groundspeed (as output from the Tracker) is checked against the threshold
+\item 'Maximum Acceleration': The track update's groundspeed derivative (difference to the previous value divided by time delta) is checked against the threshold
+\item 'Maximum Turnrate': The track update's track-angle derivative (difference to the previous value divided by time delta) is checked against the threshold
+\item 'Maximum ROCD': The track update's Mode C derivative (difference to the previous value divided by time delta) is checked against the threshold
+\end{itemize}
+\ \\
+
+For each track, the number of target reports failing the movement checks (PDU) is calculated and the ratio to the total number of track updates is calculated. If this ratio is larger than the 'Dubious Probability', the track is marked as dubious.
 
 \subsubsection{Result Values}
 
@@ -137,22 +156,34 @@ \subsubsection{Result Values}
   \begin{tabularx}{\textwidth}{ | l | X |  l | }
     \hline
     \textbf{Name} & \textbf{Description} & \textbf{Example} \\ \hline
-    Sector Layer & Name of the sector layer & fir\_cut\_sim \\ \hline
-    Reqirement Group & Name of the requirement group & Mandatory  \\ \hline
-    Reqirement & Name of the requirement & Detection  \\ \hline
-    Num Results & Total number of results & 728  \\ \hline
-    Num Usable Results & Number of usable results & 417  \\ \hline
-    Num Unusable Results & Number of unusable results & 311  \\ \hline
-    \#Updates/\#EUIs [1] & Total number update intervals & 7960  \\ \hline
-    \#MUIs [1] & Number of missed update intervals & 2221  \\ \hline
-    PD [\%] & Probability of Detection & 72.10  \\ \hline
-    Condition &  & >= 90.00  \\ \hline
-    Condition Fulfilled &  & Failed  \\ \hline
+    Sector Layer & Name of the sector layer & fir\_body\_cut \\ \hline
+    Reqirement Group & Name of the requirement group & Required \\ \hline
+    Reqirement & Name of the requirement & Dubious \\ \hline
+    Num Results & Total number of results & 690 \\ \hline
+    Num Usable Results & Number of usable results & 504 \\ \hline
+    Num Unusable Results & Number of unusable results & 186 \\ \hline
+    Use & To be used in results & true \\ \hline
+    \#Pos [1] & Number of updates & 44697 \\ \hline
+    \#PosInside [1] & Number of updates inside sector & 33498 \\ \hline
+    \#PosOutside [1] & Number of updates outside sector & 11199 \\ \hline
+    \#DU [1] & Number of dubious updates inside sector & 2691 \\ \hline
+    PDU [\%] & Probability of dubious update & 8.03 \\ \hline
+    \#T [1] & Number of tracks & 594 \\ \hline
+    \#DT [1] & Number of dubious tracks & 394 \\ \hline
+    Duration [s] & Duration of all tracks & 129462.93 \\ \hline
+    Duration Dubious [s] & Duration of dubious tracks & 14551.83 \\ \hline
+    Duration Non-Dubious [s] & Duration of non-dubious tracks & 114911.10 \\ \hline
+    Average Duration Dubious [s] & Average duration of dubious tracks & 36.93 \\ \hline
+    Duration Ratio Dubious [\%] & Duration ratio of dubious tracks & 11.24 \\ \hline
+    Duration Ratio Non-Dubious [\%] & Duration ratio of non-dubious tracks & 88.76 \\ \hline
+    PDT [\%] & Probability of dubious track & 66.33 \\ \hline
+    Condition &  & <= 90.00 \\ \hline
+    Condition Fulfilled &  & Passed \\ \hline
 \end{tabularx}
 \end{table}
 \end{center}
 
-Also, a table is given for all single targets, sorted by PD.
+Also, a table is given for all single targets, sorted by PDT.
 
 \paragraph{Single Target}
 
@@ -162,12 +193,21 @@ \subsubsection{Result Values}
     \hline
     \textbf{Name} & \textbf{Description} & \textbf{Example} \\ \hline
     Use & To be used in results & true \\ \hline
-    \#EUIs [1] & Expected Update Intervals & 6 \\ \hline
-    \#MUIs [1] & Missed Update Intervals & 5 \\ \hline
-    PD [\%] & Probability of Detection & 16.67 \\ \hline
-    Reference Period 0 & Time inside sector & [15:47:22.680,15:47:45.828] \\ \hline
-    Reference Period 1 & Time inside sector & [15:47:53.844,15:47:57.844] \\ \hline
-    Condition &  & >= 90.00 \\ \hline
+    \#Up [1] & Number of updates & 354 \\ \hline
+    \#PosInside [1] & Number of updates inside sector & 354 \\ \hline
+    \#PosOutside [1] & Number of updates outside sector & 0 \\ \hline
+    \#DU [1] & Number of dubious updates inside sector & 33 \\ \hline
+    PDU [\%] & Probability of dubious update & 9.32 \\ \hline
+    \#T [1] & Number of tracks & 7 \\ \hline
+    \#DT [1] & Number of dubious tracks & 4 \\ \hline
+    Duration [s] & Duration of all tracks & 1339.86 \\ \hline
+    Duration Dubious [s] & Duration of dubious tracks & 92.50 \\ \hline
+    Duration Non-Dubious [s] & Duration of non-dubious tracks & 1247.36 \\ \hline
+    Average Duration Dubious [s] & Average duration of dubious tracks & 23.13 \\ \hline
+    Duration Dubious Ratio [\%] & Duration ratio of dubious tracks & 6.9 \\ \hline
+    Duration Non-Dubious Ration [\%] & Duration ratio of non-dubious tracks & 93.1 \\ \hline
+    PDT [\%] & Probability of dubious track &  \\ \hline
+    Condition &  & <= 90.00 \\ \hline
     Condition Fulfilled &  & Failed \\ \hline
 \end{tabularx}
 \end{table}

doc/screenshots/osgview_style_track_m3a_age.png

@@ -181,8 +181,10 @@ \subsubsection{Style}
  \item Color by ADS-B Position Quality: Color is defined by the ADS-B NUCp/NACp value of the target report
  \item Color by Flight Level: Color is defined by the Mode C code/Flight level
  \item Color by Speed: Color is defined by groundspeed value
+ \item Color by Radar Detection Type: Color is defined by Radar detection type (PSR, SSR, PSR+SSR, ...)
  \item Color by Track Angle: Color is defined by direction of movement value
- \item Color by Tracker Detection Type: Color is defined by detection type (PSR, SSR, Combined, ...)
+ \item Color by Track Detection Type: Color is defined by Tracker detection type (PSR, SSR, Combined, ...)
+ \item Color by Track Age Type: Color is defined by track age of variable (measured\_mode3a\_age\_s, modec\_age, ...)
 \end{itemize}
 \  \\
 
@@ -238,6 +240,12 @@ \subsubsection{Style Examples}
   \caption{OSG View Color by flight level}
 \end{figure}
 
+\begin{figure}[H]
+    \hspace*{-2.5cm}
+    \includegraphics[width=19cm,frame]{../screenshots/osgview_style_radar_detection_type.png}
+  \caption{OSG View Color by Radar detection type}
+\end{figure}
+
 \begin{figure}[H]
     \hspace*{-2.5cm}
     \includegraphics[width=19cm,frame]{../screenshots/osgview_style_speed.png}
@@ -253,7 +261,7 @@ \subsubsection{Style Examples}
 \begin{figure}[H]
     \hspace*{-2.5cm}
     \includegraphics[width=19cm,frame]{../screenshots/osgview_style_tracker_detection_type.png}
-  \caption{OSG View Color by tracker detection type}
+  \caption{OSG View Color by track detection type}
 \end{figure}
 
 Please note that:
@@ -263,6 +271,62 @@ \subsubsection{Style Examples}
  \item The method used to determine the detection type is currently being discussed/tested by users and will be documented after being accepted.
 \end{itemize}
 
+\begin{figure}[H]
+    \hspace*{-2.5cm}
+    \includegraphics[width=19cm,frame]{../screenshots/osgview_style_track_m3a_age.png}
+  \caption{OSG View Color by track Mode 3/A age}
+\end{figure}
+
+\begin{figure}[H]
+    \hspace*{-2.5cm}
+    \includegraphics[width=19cm,frame]{../screenshots/osgview_style_track_mlt_age.png}
+  \caption{OSG View Color by track MLAT age}
+\end{figure}
+
+Please note, in this style one can set the following parameters (by clicking the respective value):
+In this style, one can change the following parameters:
+
+\begin{itemize}
+ \item Variable used (naming as in ASTERIX, mostly), i.e.:
+ \begin{itemize}
+    \item measured\_alt\_baro\_age\_s
+    \item measured\_mode3a\_age\_s
+    \item modec\_age
+    \item track\_es\_age
+    \item track\_mds\_age
+    \item track\_mlt\_age
+    \item track\_psr\_age
+    \item track\_ssr\_age
+    \item track\_mhg\_age
+    \item track\_ias\_age
+    \item track\_tas\_age
+    \item track\_sal\_age
+    \item track\_fss\_age
+    \item track\_tid\_age
+    \item track\_com\_age
+    \item track\_sam\_age
+    \item track\_acs\_age
+    \item track\_bvr\_age
+    \item track\_gvr\_age
+    \item track\_ran\_age
+    \item track\_tar\_age
+    \item track\_tan\_age
+    \item track\_gsp\_age
+    \item track\_vun\_age
+    \item track\_met\_age
+    \item track\_emc\_age
+    \item track\_pos\_age
+    \item track\_gal\_age
+    \item track\_pun\_age
+    \item track\_mb\_age
+    \item track\_iar\_age
+    \item track\_mac\_age
+    \item track\_bps\_age
+ \end{itemize}
+ \item Time Interval used
+ \item Colors for the 4 intervals (+ None = not set color)
+\end{itemize}
+
 \subsubsection{Render Order}
 
 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.