Instructions to use nikghodki/microduck-roller-s1-299 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Microduck
How to use nikghodki/microduck-roller-s1-299 with Microduck:
# Replace SLOT with the slot specified in the model card (walk, stand, sitstand, ground_pick, kick_left, kick_right, roulade). sudo robotctl policy load SLOT nikghodki/microduck-roller-s1-299
- Notebooks
- Google Colab
- Kaggle
roller-s1-299
Mjlab-RollerSprint2m-MicroDuck
A perpetual policy for the microduck (61-D observation, 14 actions, 50 Hz, on rollers). Runs until told otherwise โ a gait, loaded into a policy slot.
Run it on a robot
sudo robotctl policy load <slot> nikghodki/microduck-roller-s1-299
The observation normalizer is baked into policy.onnx; feed raw observations.
manifest.json follows schema 2 of the microduck policy manifest (docs/policy-manifest.md in the daemon repo).
Training
- task_id:
Mjlab-RollerSprint2m-MicroDuck - repo:
https://github.com/pollen-robotics/microduck-challenges - branch:
md-planter - commit:
fe4036eb2 - checkpoint:
299 - seed:
1 - base:
mjlab-microduck 0.1.0 @ 1efd853be - started:
2026-10-29T10:10:37Z - exported from a checkout with uncommitted changes
Reproduce
Same code, same uv.lock, same command, same seed. Training it again yields a comparable policy, not the same weights: GPU reinforcement learning is not bit-reproducible across machines.
git clone https://github.com/pollen-robotics/microduck-challenges
cd microduck-challenges
git checkout fe4036eb2
uv sync
uv run train Mjlab-RollerSprint2m-MicroDuck --env.scene.num-envs 4096 --agent.max-iterations 300 --agent.seed 1 --agent.logger tensorboard --agent.run-name roller-s1
- Downloads last month
- 13