Add exclude parameter to S3 pull functionality #205
Merged
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
exclude
parameter to S3 pull functionality to filter out directories during syncpull_model_trajectories
helper to automatically exclude checkpoints and logsMotivation
Often when analyzing trajectory data, we only need the trajectory files themselves, not the model checkpoints or logs. Model checkpoints can be very large (gigabytes), and downloading them consumes significant bandwidth and storage space. This is especially important when working on mobile connections or with limited bandwidth.
Changes
ExcludableOption
type with valid options:"checkpoints"
,"logs"
,"trajectories"
s3_sync()
to accept and use exclude patterns with AWS CLI's--exclude
flagpull_model_from_s3()
and_experimental_pull_from_s3()
to accept and pass through exclude parameterpull_model_trajectories()
helper to automatically exclude checkpoints and logsTest plan
Created and ran
test_s3_exclude.py
to verify:email-agent-216-4
in projectemail_agent
🤖 Generated with Claude Code