this is for holding javascript data
Nicolas Saunier edited Results.tex
almost 10 years ago
Commit id: d1b8bdd787e2e0a067c7bb103f878eee4612750a
deletions | additions
diff --git a/Results.tex b/Results.tex
index 29f8dcf..e43a091 100644
--- a/Results.tex
+++ b/Results.tex
...
At 30 frames per second, a data collection at an intersection over a period of 12 hours (e.g. 7 AM to 7 PM), over a driving distance of 50 metres and at an average driving speed of 30 km/h, and with an average hourly flowrate of 500 veh/h yields approximatly 1,080,000 instantaneous grouped observations. Additionally, each of these observations can have anywhere between 3 to 100 feature tracks associated with. The recommended number of features to aim for is roughly 15-20 per object: this yields manageble data sizes (roughly 500 MB of storage per hour of video) while maintinging and adequate level of data richness and object representation. Video storage needs will vary greatly by camera choice, resolution, framerate, and video encoding settings.
\ref{fig:interaction-sizes} Figure~\ref{fig:interaction-sizes} shows
interaction generation the orders of magnitude of the interactions observed in the various sites.
\subsection{Processing Times}