Fix n_obs_steps handling to ensure correct channel shapes #2285
+40
−1
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.
🐛 Fix: Training crash when using
--policy.n_obs_steps=1Summary
Fixes a bug where training crashed when
--policy.n_obs_steps=1.Previously, the dataset returned tensors with the wrong number of channels, causing a
RuntimeErrorin the encoder.Changes
[H, W, C]→[C, H, W][N, H, W, C]→[N*C, H, W]image_transformsper framen_obs_steps🧪 How it was tested
n_obs_steps=1n_obs_steps>1[n_obs_steps*3, H, W]🔍 How to checkout & try
Fixes #2277