apurvaga commited on
Commit
18e39cd
·
verified ·
1 Parent(s): ab3940b

Clarify trajectory grouping

Browse files
Files changed (1) hide show
  1. README.md +1 -1
README.md CHANGED
@@ -53,7 +53,7 @@ decode them with `json.loads`.
53
  | `trajectory_step_added` | `step_index`, `step` (`thought`, `code`, `output`, `error`, `reward`, `misc`) |
54
  | `trajectory_finished` | `reward`, `finish_message`, `error_message` |
55
 
56
- To reconstruct a trajectory, group events by `trajectory_id`. The `task` in `trajectory_task_set` is the
57
  state at the start of the run (for TextCraft, `task.misc.initial_inventory` is the true starting inventory).
58
 
59
  ## Viewing with platoon's visualization tool
 
53
  | `trajectory_step_added` | `step_index`, `step` (`thought`, `code`, `output`, `error`, `reward`, `misc`) |
54
  | `trajectory_finished` | `reward`, `finish_message`, `error_message` |
55
 
56
+ Within a row, `events` interleaves events from the root agent and all of its sub-agents in time order. To get one agent's trajectory, filter by `trajectory_id`; each sub-agent's `parent_info` (in its `trajectory_created` event) links it to the agent that spawned it. Single-agent datasets have one trajectory per row. The `task` in `trajectory_task_set` is the
57
  state at the start of the run (for TextCraft, `task.misc.initial_inventory` is the true starting inventory).
58
 
59
  ## Viewing with platoon's visualization tool