You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @maxspahn, I've come across some hurdles in my project and this is a weird one. We know that joints can get actuated and actuated joints move links (dah!) but we expect that whenever a single joint is actuated, only links connected to that joint move, right?
This is the issue I've come across while I was testing stuff. We have an issue on this matter.
Given these samples:
we clearly see that the input action is intended to move one joint. But after a while, some other joints start moving. And I think this can cause some issues. Is this us or pyBullet? Because code is solid and I don't see any case that our input violate something in pyBullet's documentation.
Or have I gone mad? 😅Can you check this one? I can't find a logical explanation for this.
The text was updated successfully, but these errors were encountered:
The moment you are trying to exceed the joint limits, the behavior become weird in pybullet. The PID controller for velocities is probably saturating the torques too much. You should stop your while loop as soon as done becomes true, in your cases around step 300.
If you do so, you can plot the velocities, see below and you observe nothing weird about it.
Hello @maxspahn, I've come across some hurdles in my project and this is a weird one. We know that joints can get actuated and actuated joints move links (dah!) but we expect that whenever a single joint is actuated, only links connected to that joint move, right?
This is the issue I've come across while I was testing stuff. We have an issue on this matter.
Given these samples:
and
we clearly see that the input action is intended to move one joint. But after a while, some other joints start moving. And I think this can cause some issues. Is this us or
pyBullet
? Because code is solid and I don't see any case that our input violate something in pyBullet's documentation.Or have I gone mad? 😅Can you check this one? I can't find a logical explanation for this.
The text was updated successfully, but these errors were encountered: