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
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.
The text was updated successfully, but these errors were encountered:
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?
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.
The text was updated successfully, but these errors were encountered: