data.tracking: Player Tracking Data
In aaronzpearson/fvp: Force-Velocity-Power Player Profiling

Description Usage Arguments Details Value Functions Note

This is a generic function that builds a data.frame that can be applied in subsequent analyses. If the athlete's data is not in the form provided by this function, the _.player.profile() functions will return an error because of inconsistent variable names.

data.tracking(game.speed, game.accel)

gps.data(game.speed, game.accel)

sa.data(game.speed, game.accel)

`game.speed`	The player's speed vector
`game.accel`	The player's acceleration vector

Although _.data() functions return cleaned data, they do not behave the same. Rather, each function is built to accomodate future analyses within the same family of functions. For example, gps.data() and sa.data() functions build data sets that are comprised of a player's observed speed and acceleration. Conversely, scout.data() takes on a players distance and time splits. Therefore, it is recommended that functions be kept within their family.

Functions that are of the form _.data._() do not handle player tracking data. Rather, they are utilized in analyses that require more information like a player's height and mass.

A data.frame that contains clean player tracking data

gps.data: Handles GPS and LPS player tracking data
sa.data: Handles speed-acceleration player tracking data

The input game data is assumed to be in metric. Speed must be in m/s and acceleration in m/s/s. If it is not, values that are returned are not representative of a player's true sprint potential. If your data needs to be converted, use the convert.to.metric() function. See the convert.to.metric() documentation for examples on automating the process.

aaronzpearson/fvp documentation built on Jan. 16, 2022, 12:39 a.m.