google-deepmind/pysc2

replay_actions isn't generic and doesn't do what you'd expect

Open

#51 opened on Aug 29, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (7,868 stars) (1,162 forks)batch import
help wanted

Description

Hi, I used a Ubuntu16.06 and installed the game successfully. All the functions work well except for running python -m pysc2.bin.replay_actions --replays='/home/hxu/StarCraftII/Replays/Replays/f57ab36fd55aad2bf3b24645fe37c16824f4af1eb6a08654be43381a8ed2eef0.SC2Replay'. Here is what I've got. There are partial stats but not sequential events or state-action pairs.

Getting replay list: /home/hxu/StarCraftII/Replays/Replays/f57ab36fd55aad2bf3b24645fe37c16824f4af1eb6a08654be43381a8ed2eef0.SC2Repl ay 1 replays found.

[0] Starting up a new SC2 instance. Version: B55958 (SC2.3.16) Build: Jul 31 2017 13:19:41 Command Line: '"/home/hxu/StarCraftII/Versions/Base55958/SC2_x64" -listen 127.0.0.1 -port 21645 -dataDir /home/hxu/StarCraftII/ -te mpDir /tmp/sc-5QgJ1W/ -displayMode 0' Starting up... Startup Phase 1 complete Startup Phase 2 complete Creating stub renderer... Listening on: 127.0.0.1:21645 (21645) Startup Phase 3 complete. Ready for commands. [0] SC2 Started successfully. [0] Got replay: /home/hxu/StarCraftII/Replays/Replays/f57ab36fd55aad2bf3b24645fe37c16824f4af1eb6a08654be43381a8ed2eef0.SC2Replay [0] ------------------ Replay Info f57ab36fd5 ------------------ [0] map_name: "Catallena LE (Void)" [0] player_info { [0] player_info { [0] player_id: 1 [0] race_requested: Terran [0] race_actual: Terran [38/1813] [0] } [0] player_result { [0] player_id: 1 [0] result: Defeat [0] } [0] player_mmr: 3437 [0] player_apm: 83 [0] } [0] player_info { [0] player_info { [0] player_id: 2 [0] race_requested: Zerg [0] race_actual: Zerg [0] } [0] player_result { [0] player_id: 2 [0] result: Victory [0] } [0] player_mmr: 3381 [0] player_apm: 107 [0] } [0] game_duration_loops: 23529 [0] game_duration_seconds: 1050.47509766 [0] game_version: "3.16.1.55958" [0] data_build: 55958 [0] base_build: 55958 [0] data_version: "5BD7C31B44525DAB46E64C4602A81DC2" [0] ------------------------------------------------------------ [0] Starting f57ab36fd5 from player 1's perspective ============================================= Summary 10 secs ============================================= Replays: 0, Steps total: 0

Camera move: 0, Select pt: 0, Select rect: 0, Control group: 0

Maps: 1 {Catallena LE (Void): 1}

Races: 2 {Zerg: 1, Terran: 1}

Unit ids: 0 {}

Valid abilities: 0 {}

Made abilities: 0 {}

Valid actions: 0 {}

Made actions: 0 {} Races: 2 {Zerg: 1, Terran: 1}

Unit ids: 0 {}

Valid abilities: 0 {}

Made abilities: 0 {}

Valid actions: 0 {}

Made actions: 0 {}

Crashing replays: 0 []

Invalid replays: 0 [] ---------------------------------------------- Process stats ---------------------------------------------- [ 0] replay: f57ab36fd5, replays: 0, steps: 0, game loops: 0, last: start_replay, 0 s ago

Contributor guide

Tech stack
python
Domain
clidata
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Python programmingFamiliarity with StarCraft II replaysUnderstanding of pysc2 codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the replay actions script in pysc2/bin/ to understand why it outputs only summary stats instead of sequential actions. The issue reporter provided a specific replay where the script ran but did not produce actions. Look at the code flow: it starts SC2, gets replay info, but then the step loop does not seem to collect actions. Check if the script is missing a loop to step through the replay and record actions, or if there is a configuration issue. Examine any related configuration files or command line arguments that control verbosity. Also review any comments or linked issues for prior discussions on this behavior.