Switch trajectory storage from YAML to JSONL format #204
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Why this change?
Kyle originally suggested using YAML for human readability, but the performance cost turned out to be too high. This PR switches to JSONL (newline-delimited JSON) format while maintaining full backward compatibility.
Changes
trajectory_logging.py
to serialize as JSONL (one JSON object per line).jsonl
extensionload_trajectories
implementations (removed art-e specific version)aggregate_trajectories
module for step-level metric aggregationBackward Compatibility
.yaml
and.jsonl
filesTrade-offs
Test plan
🤖 Generated with Claude Code