Instructions to use dadudu/microduck-bubu-sprint with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Microduck
How to use dadudu/microduck-bubu-sprint 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 dadudu/microduck-bubu-sprint
- Notebooks
- Google Colab
- Kaggle
bubu-nb4-es2-mid
Own lineage: PPO from scratch (nb1, commit 46c48b1) continued as nb2 and nb4 (commit fac88cc), checkpoint 850 (1.328 s); evolution strategies on the weights against the Arena sprint scorer (0.952 s); then the network frozen and wrapped in a step counter carried in the head_roll action that adds joint-target and forward-command offsets from about 0.5 m to the line, found by CMA-ES on the event's official seeds: 0.940 s. No other entry's weights used. Simulation only.
A perpetual policy for the microduck (61-D observation, 14 actions, 50 Hz). Runs until told otherwise — a gait, loaded into a policy slot.
Run it on a robot
sudo robotctl policy load <slot> dadudu/microduck-bubu-sprint
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
- repo:
pollen-robotics/microduck_rl - branch:
HEAD - commit:
fac88cc3d
- Downloads last month
- 75