Skip to content
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

Good enough for a alpha release? #2

Merged
merged 127 commits into from
Mar 2, 2021
Merged

Good enough for a alpha release? #2

merged 127 commits into from
Mar 2, 2021

Conversation

marcbone
Copy link
Collaborator

No description provided.

Marco Boneberger and others added 30 commits December 8, 2020 12:36
This includes getting the joint infos, calculate inverse kinemtatics, setting joint motor commands and some debug visualizer settings
@marcbone
Copy link
Collaborator Author

marcbone commented Feb 24, 2021

only for the scale or for everything?

For almost everything, we could make the function generic over Into<nalgebra::EquivalentType>. The user's code would be clean and they would be able to decide between e.g. [f64; 3] and Point3<f64> depending on what works best for them and the generic bounds would document exactly the expected type. The implementation would get messier, though.

Is done.

I do agree on the potential confusion with the function names, though. Maybe we also create a set_joint_motor_control that we mark as deprecated? It could just call set_joint_motor_control_2. Or maybe it doesn't matter and I'm just being too picky about a *_2 function appearing without a matching previous.

I renamed it to set_joint_motor_control. Seems like the function got deprecated in pybullet over 4 years ago. I guess no one is using it anymore. Are you fine with that? I also added "setJointMotorControl2" and "set_joint_motor_control_2" as doc aliases

@neachdainn
Copy link
Owner

I renamed it to set_joint_motor_control. Seems like the function got deprecated in pybullet over 4 years ago. I guess no one is using it anymore. Are you fine with that? I also added "setJointMotorControl2" and "set_joint_motor_control_2" as doc aliases

Good by me! I'll have to look up the doc aliases - I'm vaguely aware that they exist but I've never actually read up on them.

@marcbone
Copy link
Collaborator Author

marcbone commented Mar 1, 2021

Good by me! I'll have to look up the doc aliases - I'm vaguely aware that they exist but I've never actually read up on them.

If you type the aliases into the search function the set_joint_motor_control_2 will light up.

I guess we have everything. Can I merge it? 😅

@neachdainn
Copy link
Owner

You're good to merge whenever!

@marcbone marcbone merged commit b6a5569 into master Mar 2, 2021
@marcbone marcbone deleted the marco_dev branch April 17, 2021 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants