this is for holding javascript data
Paul St-Aubin edited Results.tex
almost 10 years ago
Commit id: 5337b7947a053f5ce948c9ac6d1bbd766896043c
deletions | additions
diff --git a/Results.tex b/Results.tex
index d9da2c4..2f4a58d 100644
--- a/Results.tex
+++ b/Results.tex
...
\subsection{Data Sizes}
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. 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 data sizes which are still manageble to work with (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.
\subsection{Processing Times}