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
If you are submitting a bug report, please fill in the following details and use the tag [bug].
Describe the bug
The mdp.JointPositionActionCfg in ActionsCfg allow us to specify the desired joint order by passing joint_names and setting preserve_order=True. However, this is not effective when we specify order for all joints.
Steps to reproduce
Using task "Isaac-Velocity-Flat-Unitree-A1-v0" as example,
we expect the joint orders to be [0, 4, 8, 1, 5, 9, 2, 6, 10, 3, 7, 11]. However, the _joint_ids that the JointAction sees is still a None slice (slice(None, None, None)).
If you are submitting a bug report, please fill in the following details and use the tag [bug].
Describe the bug
The
mdp.JointPositionActionCfg
inActionsCfg
allow us to specify the desired joint order by passingjoint_names
and settingpreserve_order=True
. However, this is not effective when we specify order for all joints.Steps to reproduce
Using task "Isaac-Velocity-Flat-Unitree-A1-v0" as example,
when using the following config
we expect the joint orders to be
[0, 4, 8, 1, 5, 9, 2, 6, 10, 3, 7, 11]
. However, the_joint_ids
that the JointAction sees is still a None slice (slice(None, None, None)
).This is due to this logic in JointAction
It empties the
_joint_ids
even if we setpreserve_order
to be True. A suggested fix is to change the condition to bewhich allow users to force a certain joint order of the policy output.
System Info
Additional context
None
Checklist
Acceptance Criteria
The text was updated successfully, but these errors were encountered: