Conversation
| "pos_x": pos_x_axis, | ||
| "pos_y": pos_y_axis, | ||
| "pos_z": pos_z_axis, | ||
| "euler_x": euler_x_axis, | ||
| "euler_y": euler_y_axis, | ||
| "euler_z": euler_z_axis, |
There was a problem hiding this comment.
I don't think this will work as most gamepads only have 2 joysticks, but this is expecting 3. Have you tested this?
There was a problem hiding this comment.
i have not tested this, is it possible to set pos, click a button and then set orientation ?. if it is possible, please make the necessary changes. if this is not possible(or it doesn't feel intuitive), what would you suggest as the alternative ?
There was a problem hiding this comment.
Why are you submitting code that you have not tested?
|
These require functional examples that converge. |
|
the example i included does converge, but not very well, further tuning is required. could you help with the reward engineering ?. The main issue I am facing is that, when the command position is more than half a meter from the current position the robot just gives up and falls on the ground, I have tried increasing the timeout, increase the reward weight, increase sensitivity. But I couldn't get a satisfactory result, https://github.com/user-attachments/assets/f3df1780-89f6-42e8-be6f-4921eb664e8c |
Are these new managers for actual environments/robots you're working with that do converge? If so, the example doesn't have to use the Go2 robot, and you can import a robot that you're working with as the example. Both examples are for the position command, and neither seems to demonstrate the pose command. Have you verified that PoseCommandManager works? Also, you copied the README files without updating their contents. Please stop blindly copying code without updating it for your usecase. |
2 participants
Adds the position command manager and the pose command manager and the accompanying reward functions for tracking