Registering an arbitrary number of anchors methods about argos3 HOT 2 CLOSED

[...] This works by using the anchor's index as a key to a std::unordered_map inside a given Dynamics3d physics model. The map then provides the callback function with the positions and orientations that I need to send back to the space.

This looks to me like a sensible approach. If the number of elements in the map is not large, you might find that using a custom bucket-based implementation is faster. I'd go down this road only in a second moment, and if really necessary.

Perhaps it is possible to relax the requirements of / overload RegisterAnchorMethod to take a function object? At the moment this is not possible:
I designed the callback to strictly be a method of the physics model. This makes it more memory efficient and easier to write. Using a functor would be more flexible, but less efficient.

If you are really concerned about speed, you might experiment with having a single, standard callback for every anchor (callback as it is defined now), but then within the callback dispatch on the right functor defined by you. This kinda defeats the purpose of the anchors as they are designed now, but it could work.

from argos3.

Ok, I will use the std::unordered_map approach for now. Thanks for the feedback!

from argos3.