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

Error Qualification #7

Open
Jmeyer1292 opened this issue Aug 5, 2018 · 2 comments
Open

Error Qualification #7

Jmeyer1292 opened this issue Aug 5, 2018 · 2 comments

Comments

@Jmeyer1292
Copy link
Owner

A nice feature of the library is that allows you to use floating point precision (instead of double) if you want the extra bits of speed. The cost is accuracy. This shows up in our tests but I want to make a tool that qualifies it for a set of parameters. It's different for different robots - big ones suffer more from accuracy problems.

@gavanderhoorn
Copy link
Collaborator

really just curious here: have you ever tried to quantify the performance difference? I'm aware of the choice between float and double having an impact on things like gpgpu and when working with really large matrices (fi). For the nr of elements in the vector/matrices opw_kinematics deals with, do you observe a similar effect?

@Jmeyer1292
Copy link
Owner Author

It's probably overkill to use anything but double. I just wanted the option to use this in things like gpgpu programming.

In my tests (found in open prs) I have seen:
Fk float vs double: 0.2 vs 0.5 us.

Ik float vs double: 1.5 vs 3 us.

@JeroenDM JeroenDM mentioned this issue Aug 6, 2018
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

No branches or pull requests

2 participants