-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support specifying link pose wrt parent joint #8
Comments
For the records, the currently implemented behavior is compatible with URDF requirements, therefore if the SDF loaded into jaxsim is converted from any URDF, the resulting model is automatically compatible with jaxsim. |
The new joint model introduced with the functional APIs in #108 (more specifically, #101) should now support the definition of a successor-to-child transform In particular, we initialize this transform here: jaxsim/src/jaxsim/math/joint_model.py Lines 101 to 105 in e917034
And then we combine it to compute the overall parent-to-child transform jaxsim/src/jaxsim/api/kin_dyn_parameters.py Lines 401 to 407 in e917034
We should write a test making sure that this feature is implemented as expected, but for the time being we can consider this issue as solved. |
* Update `pixi` lockfile in CI * Use uniquely named branches when opening PRs * Install `pixi-diff-to-markdown` via `pixi`
* Update `pixi` lockfile in CI * Use uniquely named branches when opening PRs * Install `pixi-diff-to-markdown` via `pixi`
* Update `pixi` lockfile in CI * Use uniquely named branches when opening PRs * Install `pixi-diff-to-markdown` via `pixi` Add dummy `jaxsim.rbda.contacts.rigid` module [WIP] Add rigid contact model implementation Still not working for recurrency while jit-compiling. Update `ODEState` to handle rigid contacts Fix missing argument in `ODEState.zero` function Pass new argument to `ODEState.zero` from `wrap_system_dynamics_for_integration` Handle rigid contacts in `system_velocity_dynamics` and `system_dynamics` Update `jaxsim.api.contact.collidable_point_dynamics` Update `collidable_point_dynamics` return type Make `ContactsParams` and `ContactModel` inherit from `JaxsimDataclass` Fixes in rigid contact model Decouple functions computing system acceleration and contact forces Update `aux_dict` returned by `collidable_point_dynamics` Add `qpax` dependency in `ci_cd.yml` Move `qpax` as private import Fix installation of `qpax` dependency in CICD Move `inactive_collidable_points_prev` to RigidContactState Generalize handling of contact states [WIP] Restore inactive collidable points status array as `RigidContactParams` attribute Remove impact detection and activation state at previous iteration Improve computation of post impact system velocity [WIP] Update system velocity in `jazsim.api.model.step` Compute impact velocity in `jaxsmi.api.model.step`
Currently, as inheritance of the kinematics formulated by the RBDA book, our physics assumes that the link frames are positioned exactly over the successor frame of their parent joint.
This means that all SDF models having a non-trivial
/link/pose
are not yet supported. Note that this does not constrains in any way model creation, in fact, any non-supported model could be edited without a big effort to combine the pose of child elements of the links (inertial, visual, collisions, ...) with the unsupported link pose.In any case, this limitation has to be solved from our side. It is not trivial, since we need to treat differently the successor frame of a joint and the frame of its child link.
The text was updated successfully, but these errors were encountered: