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
In the MR #1476, the clipping functionality to individual action terms was introduced. However, there are issues with this implementation:
The clipping parameter is a dictionary. While this may make sense for joint actions (where keys are the names of the joints), it doesn't mean anything at all for other action terms such as task-space action terms
The clipping is applied to the processed actions. This isn't how any/many libraries think about for clipping. Clipping is done on the raw actions usually (as done in Clips actions to large limits before applying them to the environment #984). In the case of JointAction, the clipping internally might still make sense but then it should be clipping to the simulation joint limits and must be optional (while clipping of raw actions is a MUST for training stability)
I propose that"
The clipping of processed actions should be specific to only JointAction (where it may even make sense)
Proposal
In the MR #1476, the clipping functionality to individual action terms was introduced. However, there are issues with this implementation:
I propose that"
Checklist
Acceptance Criteria