this is for holding javascript data
Nicolas Saunier edited Results.tex
about 9 years ago
Commit id: 5ed322388327f07c5dc0bea33180e1ffe8a86046
deletions | additions
diff --git a/Results.tex b/Results.tex
index 119f471..2f80812 100644
--- a/Results.tex
+++ b/Results.tex
...
% paul: "The number of user pairs per hour should be linearly correlated with the number of interaction instants as is demonstrated in Figure~\ref{fig:userpairs-interactions}. If they are not, it is possible that some site analysis areas are not comparable." not sure why...
% paul->nicolas: Added more details to explain this.
Most of the analysis is conducted on a pair of dedicated consumer-grade high-performance machines (INTEL Core i7 3770k processor with 16 to 32~GB of memory), with some work offloaded to a computing cluster when acceleration of work is necessary. Feature tracking performance depends on video resolution and special post-processing requirements such as stabilization or lens correction (for distortion). A typical one hour $800\times
600$ 600$~pixels video
at 30~frames per second is processed with current consumer-grade hardware in about an hour. A typical one hour $1280\times 960$ video with correction for distortion can be processed in about two hours. Basic analysis on one of these trajectory sequences takes between 5 minutes and 30 minutes, depending on traffic in the scene, while conflict analysis, particularly motion patterns, can typically take anywhere between 1 and 48 hours to complete. Conflict analysis processing times are very sensitive to the interaction complexity of the scene.