this is for holding javascript data
Lucas Fidon edited subsubsection_Description_We_used_a__.tex
almost 8 years ago
Commit id: 63fb8a6a37cc6efc4b6da47b4654e76c6cdc2e1f
deletions | additions
diff --git a/subsubsection_Description_We_used_a__.tex b/subsubsection_Description_We_used_a__.tex
index f4f7f52..feaeea3 100644
--- a/subsubsection_Description_We_used_a__.tex
+++ b/subsubsection_Description_We_used_a__.tex
...
Furthermore this dataset provides both positions and accelerations, which are the data we were looking for.
\subsubsection{Extraction of data}
For our experiments we used only data during a restricted period of several minutes beginning at arbitrary time of the play.
Computationnaly Computationnaly, a trajectory will be defined as a set of 2-dimensional positions and accelerations regularly distributed in time.
Furthermore we will handle a set of synchronized trajectories. This synchronization is highly important since we will
used assume it when we will approximate the joint probability distribution of positions or accelerations of two players.
Data are read and extracted with a 25Hz frequency which corresponds to the best frequency we could have if we were extracting the trajectories directly from the videos of the soccer match. As each player is equipped with several sensors we combine their data to have one and only one trajectory per player.
Sometimes some data have been missed, but one can cope with this problem interpolating data so as to maintain synchronization between the different trajectories.