player.profile: Player Profiling
In aaronzpearson/fvp: Force-Velocity-Power Player Profiling

Description Usage Arguments Details Value Functions Note

This is a generic function that builds player profiles from game data much like the functions gps.player.profile(), gps.game.profile(), sa.player.profile(), and scout.player.profile. Depending on the function used, player profiles will return either observed or modeled values.

player.profile(player.name = NA, game.data, r2 = 0.95)

build.player.profile(player.name = NA, max.speed, max.accel)

gps.player.profile(player.name = NA, game.data)

gps.player.profile.game(
  player.name = NA,
  game.data,
  min.speed = 0.3,
  max.speed.threshold = 95,
  sample.rate = 10
)

sa.player.profile(player.name = NA, game.data, r2 = 0.95)

scout.player.profile(player.name = NA, sprint.data)

`player.name`	The player's name
`game.data`	The player's cleaned game data
`r2`	The minimum r^2 when fitting the model

The intention of player.profile(), and similar functions, is to provide sports practitioners with pertinent information on the given athlete's mechanical sprint abilities. Practitioners can apply this information in _.results.model() functions to build data sets that represent the athlete's mechanical speeds, accelerations, and distances covered as a function of time.

It is suggested that the player.name argument be filled to be effectively applied to functions like compare.player.profiles().

Thank you to Patrick Ward for the first iteration of scout.player.profile().

An athlete's player profile which includes the player's name, their maximal attainable speed, maximal attainable acceleration, and their acceleration constant.

build.player.profile: Manually create a player's profile
gps.player.profile: GPS player profile from a player's potential abilities
gps.player.profile.game: GPS player profile from a player's observed abilities
sa.player.profile: Speed-acceleration player profile from a player's GPS data
scout.player.profile: Sprint test player profile from a player's split times and distances

The functions sa.player.profile() and scout.player.profile() must be called explicitly because their helper functions differ significantly.

The functions fv.player.profile() and fvp.player.profile() are unique functions and are not assessed in the same manner. Therefore, the generic function is not applicable.

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.