Cell 7: 100% avoiding grenade parsing by using parseticks only import glob import numpy…
- User
Cell 7: 100% avoiding grenade parsing by using parse_ticks only
import glob import numpy as np from awpy import Demo
1) Tick‑level props guaranteed by demoparser2 for CS2 1v1 demos
feature_cols = [ "X", # world X "Y", # world Y "Z", # world Z "pitch", # look up/down "yaw", # look left/right "health", # hit points "is_airborne", # in the air? ]
button bit‑mask constants for label extraction
IN_ATTACK = 1 IN_FORWARD = 8 IN_MOVELEFT = 512 IN_MOVERIGHT = 1024
2) Collect all .dem files in this directory
demo_files = glob.glob("*.dem") print(f"Found {len(demo_files)} demos:", demo_files)
all_X, all_Y = [], []
for path in demo_files: dem = Demo(path) try: # ⚡️ ONLY parse tick data → never touches grenades or rounds tick_df = dem.parse_ticks(player_props=feature_cols + ["buttons"]) df = tick_df.to_pandas() except Exception as e: print(f"⚠️ Skipping {path}: parse_ticks() error → {e}") continue
# 3) Check for missing columns missing = [c for c in feature_cols + ["buttons"] if c not in df.columns] if missing: print(f"⚠️ Skipping {path}: missing {missing}") continue # 4) Build feature matrix (drop the buttons column) feats = df[feature_cols].astype(np.float32, copy=False).to_numpy() # 5) Decode the buttons bitmask into a single action label btn = df["buttons"].astype(int).to_numpy() actions = np.zeros(len(btn), dtype=np.int64) # priority: shoot > forward > left > right actions[btn & IN_ATTACK > 0] = 4 actions[btn & IN_FORWARD > 0] = 1 actions[btn & IN_MOVELEFT > 0] = 2 actions[btn & IN_MOVERIGHT > 0] = 3 all_X.append(feats) all_Y.append(actions)6) Concatenate across all demos
if not all_X: raise RuntimeError("No demos parsed successfully—check errors above.")
X = np.concatenate(all_X, axis=0) # shape = [total_ticks, len(feature_cols)] Y = np.concatenate(all_Y, axis=0) # shape = [total_ticks,]
print("✔️ X shape:", X.shape, " Y shape:", Y.shape)
print(X)
Assistant
Understanding the CS2 Demo Parser Code
This code demonstrates a robust approach to extract player movement and action data from Counter-Strike 2 demo files while avoiding potential parsing issues with grenades. Let me explain how it works:
Core Functionality
The script extracts player position, view angles, and actions from CS2 demo files using the
awpylibrary'sDemoclass. The key improvement here is using only theparse_ticks()method instead of more comprehensive parsing that might cause errors when processing grenade data.Key Components
-
Feature Definition: The code identifies 7 essential player properties to track:
- 3D position coordinates (X, Y, Z)
- View angles (pitch, yaw)
- Health
- Airborne status
-
Button Mapping: It defines bit masks to extract player actions from the raw button inputs:
- Shooting (IN_ATTACK = 1)
- Moving forward (IN_FORWARD = 8)
- Moving left (IN_MOVELEFT = 512)
- Moving right (IN_MOVERIGHT = 1024)
-
Processing Flow:
- Find all demo files in the current directory
- For each file, parse only the tick-level data
- Extract features into array X
- Convert button presses into categorical action labels in array Y
- Concatenate data from all demos
Error Handling
The code includes robust error handling:
- Catches and reports parsing exceptions
- Checks for missing columns in the parsed data
- Validates that at least one demo was processed successfully
Purpose
This script is likely preparing data for a machine learning model that will predict player actions based on their in-game state. The extracted arrays (X for features, Y for labels) are in the standard format expected by most ML frameworks.
The prioritization in the action labeling (shooting > forward > left > right) suggests the model will focus on predicting the most important action when multiple buttons are pressed simultaneously.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.