Skip to content

Framework/bitbots rl motion#788

Open
sWintermoor wants to merge 92 commits intomainfrom
framework/bitbots_rl_motion
Open

Framework/bitbots rl motion#788
sWintermoor wants to merge 92 commits intomainfrom
framework/bitbots_rl_motion

Conversation

@sWintermoor
Copy link
Copy Markdown
Collaborator

@sWintermoor sWintermoor commented Apr 1, 2026

Summary

This change provides a framework for rl policies. Main purpose is to minimize boiler plate code and facilitate the integration of rl models.

Proposed changes

I did a full replacement of bitbots_motion/bitbots_rl_motion.
Furthermore, I added an action called "RLKick" which can be found in kick_action. It should be used instead of WalkKick, however, it isn't fully finished, and thus, it isn't in use. Additionally, I created a capsule for rl kick.
Last, I expanded motion.launch accordingly (start command for policy nodes is currently excluded).

Related issues

Behavior should be fixed. Policies take action independant of the current game state. As an example: If you replace @WalkKick with @RLKick in dsd and include the start command for policies, the kick policy takes immediate action.

Checklist

  • Run pixi run build
  • Write documentation
  • Test on your machine
  • Test on the robot
  • create issues for future work
  • Triage this PR and label it

@github-project-automation github-project-automation bot moved this to 🆕 New in Software Apr 1, 2026
@jaagut jaagut moved this from 🆕 New to 👀 In review in Software Apr 6, 2026
@jaagut jaagut requested review from Flova and jgueldenstein April 6, 2026 08:30
Copy link
Copy Markdown
Member

@Flova Flova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this large setup. Looks very promising so far. I still have some feedback as seen below. You can reach out to be for further questions :)

Comment thread pixi.toml Outdated
Comment thread src/bitbots_motion/bitbots_rl_motion/bitbots_rl_motion/policy_nodes.py Outdated
Comment thread src/bitbots_motion/bitbots_rl_motion/configs/wolfgang_config.yaml Outdated
Comment thread src/bitbots_motion/bitbots_rl_motion/handlers/ball_handler.py
Comment thread src/bitbots_motion/bitbots_rl_motion/handlers/command_handler.py
Comment thread src/bitbots_motion/bitbots_rl_motion/nodes/rl_node.py
Position_D_Gain: 0 #2800 # [/16] 0~16,383
Position_I_Gain: 0 #180000 # [/ 65,536] 0~16,383
#If robot starts to tremble, reduce Position_P_Gain
Position_P_Gain: 1200 #1100 # [/ 128] 0~16,383
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we changing these P-gain values? Can we still walk as usual with this?

servos:
# specifies which information should be read
read_position: true
read_velocity: false
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the velocities used for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

3 participants