this is for holding javascript data
Enzo Ferrante edited section_Introduction_The_current_works__.tex
almost 8 years ago
Commit id: 2093bfdd77d2446f2660f23dc7146b5d418b4347
deletions | additions
diff --git a/section_Introduction_The_current_works__.tex b/section_Introduction_The_current_works__.tex
index 4085227..bc955dd 100644
--- a/section_Introduction_The_current_works__.tex
+++ b/section_Introduction_The_current_works__.tex
...
\section{Introduction}
The current State-of-the art works on soccer match analysis
used use extra high level data and annotation (such as whoscored, transfertmark) which require human annotation and so preprocessing. In this project we limited our input to the video of a match filmed with a multi-camera system. We focus on an unsupervised classification of the players based on clustering of their trajectories which are extracted automatically from the video of a match during a short period of time. Bases on this classification we want to be able to determine the leaders of the game, to anticipate the displacement of the players or to find pattern in the paths of the players. This information is deeply woven into the fabric of team strategy analysis and thus lead to high level semantic data about the match.
The problem of tracking players with multiple camera have been achieved consistently for instance in \cite{Ben_Shitrit_2011} even if their paths may intersect over long period of time.
On another hand the clustering process is closely linked to the choice of a metric between the object we want to classify: here the players' trajectories. Most of the time the metrics used are based on euclidian metric. However only discrete trajectories are available in the form of array which can be of different sizes with different time discretization or with different speed and euclidian metric are irrelevant to measure trajectories interdependencies. So, in our case, a relevant clustering process should be decomposed into 2 parts: