Am 19.03.2015 um 14:00 schrieb Malte Wirkus: > I personally like to have both separated. Because in my opinion the have > different tasks (while related, they are still different). +1 > > The transformer is calculating transforms from a graph of > transformations. A kinematics component knows how to compute kinematic > calculations given different joint types. > In my opinion there is no need to make the transformer "understand" the > difference between robotic mechanisms. +1 > Malte > > On 19.03.2015 13:53, Sylvain Joyeux wrote: >> On Thu, Mar 19, 2015 at 7:13 AM, Malte Wirkus <[email protected]> wrote: >>> I think https://github.com/rock-control/control-orogen-robot_frames does >>> what you want. >> Great! I did not know about that one. >> >>> Not as feature of the transformer, but creating RBS from >>> from joint data by calculating forward kinematics. >> What would be your feeling about making it a transformer feature ? >> Worth it, or useless ? (Disclaimer: since robot_frames exists, I have >> a lot less incentive to do the integration in the transformer anyways >> ;-)) >> >> Sylvain >> > _______________________________________________ > Rock-dev mailing list > [email protected] > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
-- Dipl. Inf. Janosch Machowinski SAR- & Sicherheitsrobotik Universität Bremen FB 3 - Mathematik und Informatik AG Robotik Robert-Hooke-Straße 1 28359 Bremen, Germany Zentrale: +49 421 178 45-6611 Besuchsadresse der Nebengeschäftstelle: Robert-Hooke-Straße 5 28359 Bremen, Germany Tel.: +49 421 178 45-6614 Empfang: +49 421 178 45-6600 Fax: +49 421 178 45-4150 E-Mail: [email protected] Weitere Informationen: http://www.informatik.uni-bremen.de/robotik _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
