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

Extend robot interfaces with vectorized methods #126

Closed
diegoferigo opened this issue Jan 28, 2020 · 1 comment
Closed

Extend robot interfaces with vectorized methods #126

diegoferigo opened this issue Jan 28, 2020 · 1 comment

Comments

@diegoferigo
Copy link
Collaborator

At the moment, most of the methods part of the robot interfaces operate on a single joint and accept as argument its name.

This could be a bottleneck if used in a real-time loop, we should first profile the code and then decide if we would benefit from vectorized methods.

Note that this support should pass through the implementation of similar vectorized methods also from the C++ side. As a bonus, using vectorized methods would also save us many SWIG calls that introduce their own overhead.

@diegoferigo
Copy link
Collaborator Author

The new ScenarI/O APIs #158 have been designed to fully support vectorization. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant