Derived player_vector columns

Ten player_vector columns are computed from the columns read from the demo: second, x_vel, y_vel, z_vel, speed_2d, movement_angle, movement_angle_diff, phi_vel, theta_vel and ang_vel. Compute them after loading:

from pureskillgg_csgo_dsdk import (
    add_player_vector_derived_columns,
    player_vector_source_columns,
)

# Everything, on a whole player_vector.
player_vector = loader.get_channel({"channel": "player_vector"})
add_player_vector_derived_columns(player_vector)  # added in place

# Or load only what two of them need.
wanted = ["speed_2d", "z_vel"]
player_vector = loader.get_channel(
    {"channel": "player_vector", "columns": player_vector_source_columns(wanted)}
)
add_player_vector_derived_columns(player_vector, columns=wanted)

The values are the ones csgo-ppp writes:

• Velocities are differenced per player per round, so each player’s first sample in a round reads 0. A sample where any axis moved faster than 3,500 units a second (the engine’s cap) is a teleport and reads 0 too.

• movement_angle is the direction of movement, 0 to 360. movement_angle_diff is where the player looks minus where they move, -180 to 180. Both are missing when the player stands still.

• second is tick over the tick rate: 64 in CS2. Pass tick_rate for a CS:GO match; it is in the match’s header.

A derived column the frame already has is replaced, never read, so a file that stores them comes out the same as one that doesn’t. Rows must be in tick order within each player and round, as csgo-ppp writes them. For a frame holding more than one match, such as a tome, pass group_by=["match_key", "player_id", "round"]. A frame that lacks a column they are computed from raises MissingColumns.

Publishing

Set the new version with uv version <version> (or uv version --bump patch), then run make version. It commits pyproject.toml and uv.lock and pushes a signed v* tag, which triggers the publish workflow. Or run the version workflow by hand with a version number or a bump (patch, minor, major); it does both steps.

Publishing needs the PYPI_API_TOKEN repository secret. The version and format workflows also need GH_USER, GH_TOKEN, GIT_USER_NAME, GIT_USER_EMAIL, GPG_PRIVATE_KEY and GPG_PASSPHRASE.