fix_pi_sparse_checkout.md

Fixing Sparse Checkout Warning on Pi

The Issue

Git is warning that local files exist that aren't tracked by sparse checkout yet. This is expected since we created some files directly on the Pi.

Solution: Commit or Stash Local Changes

Option 1: Commit the Pi-specific files (Recommended)

cd ~/EDTH2025/Erewhon

# Check what's changed
git status

# Add the Pi-specific files
git add PI_COMMANDS.md test_pi_model.sh requirements_pi_*.txt PI_SETUP.md ADD_LEROBOT_TO_PI.md

# Commit them
git commit -m "Add Pi deployment files and test script"

# Now add LeRobot to sparse checkout
git sparse-checkout add src/policies/ACT/lerobot/src

# Pull to get the LeRobot files
git pull

# You may need to push your commit first if there's a conflict
git push

Option 2: Stash the changes temporarily

cd ~/EDTH2025/Erewhon

# Stash local changes
git stash

# Add LeRobot to sparse checkout
git sparse-checkout add src/policies/ACT/lerobot/src

# Pull the files
git pull

# Restore your changes
git stash pop

Option 3: Force reapply (if files are safe to overwrite)

cd ~/EDTH2025/Erewhon

# Force reapply sparse checkout patterns
git sparse-checkout reapply

# Add LeRobot
git sparse-checkout add src/policies/ACT/lerobot/src

# Pull
git pull

After Fixing

Once the sparse checkout is updated and you have the LeRobot files:

# Verify LeRobot is there
ls -la src/policies/ACT/lerobot/src/lerobot/

# Clean up manually copied directory
rm -rf lerobot/

# Install missing packages
source venv/bin/activate
pip install -r requirements_pi_others.txt

# Test the model
./test_pi_model.sh

🎯 I Recommend Option 1

The files you created on the Pi (test scripts, requirements, docs) are useful and should be committed back to the repo so they're version controlled and available on other machines.