this is for holding javascript data
Lucas Fidon edited subsection_Dataset_subsubsection_Description_We__.tex
almost 8 years ago
Commit id: 1728a3d39b0c319f2d1e41c915e4a2838c36ab8e
deletions | additions
diff --git a/subsection_Dataset_subsubsection_Description_We__.tex b/subsection_Dataset_subsubsection_Description_We__.tex
index 55530f7..3f9efc6 100644
--- a/subsection_Dataset_subsubsection_Description_We__.tex
+++ b/subsection_Dataset_subsubsection_Description_We__.tex
...
\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 we defined a trajectory as a set of ordered x and y-axis positions and accelerations regularly distributed in time.
\verb|class \verb|
class trajectory:
def __init__(self):
"""
initialization of a trajectory
"""
self.id = ""
self.nbstep = 0 #nombre de pas
self.pos = []
#vecteur des positions #positions list
self.acc = [] #vecteur des accelerations
self.date = [] #dates associees aux positions et acceleration
self.datepred = 0. #sert seulement au chargementdes donnees
self.xpred = 0.
self.ypred = 0.
self.accxpred = 0.
self.accypred =
0.| 0.
|
Furthermore we will handle a set of synchronized trajectories. This synchronization is highly important since we will used it when we will approximate the joint probability distribution of positions or accelerations of two players.
Data are read and extracted with a frequency of 25 Hz which correspond to the best frequency we could have if we were extracting directly from the videos of the soccer match. As each players is equipped with several sensor we combine their data to have one and only one trajectory per player or ball.