I didn't understand the underlying model..Is there any hard constraint to interface gepetto with sot and ros? ...
I saw in pinocchio tutorial that the viewer is created via corba but don't understand the "why" of the current twisted design..(neither the use of corba in this context):/
Further the parser seamed not to parse joints so i rewrites all and simplified it a lot...
So this version of the viewer:
can be used as standalone application or used via python wrapper (see test.py)...not via corba
support all Threading Model of osg
can control robot from other thread throught RobotUpdate "remote controller".
TODO:
-define a (minimal) corba Interface in gepetto-viewer-corba
-populate attached SE3Model and add dirtyflag and sync with SE3Model method
-add more features (addView, addNode, setAnimationPath...)
I have also began to make urdf a Bullet ragdoll using osgBullet, ask me if you interested in it
I didn't understand the underlying model..Is there any hard constraint to interface gepetto with sot and ros? ... I saw in pinocchio tutorial that the viewer is created via corba but don't understand the "why" of the current twisted design..(neither the use of corba in this context):/ Further the parser seamed not to parse joints so i rewrites all and simplified it a lot...
So this version of the viewer: can be used as standalone application or used via python wrapper (see test.py)...not via corba support all Threading Model of osg can control robot from other thread throught RobotUpdate "remote controller".
TODO: -define a (minimal) corba Interface in gepetto-viewer-corba -populate attached SE3Model and add dirtyflag and sync with SE3Model method -add more features (addView, addNode, setAnimationPath...)
I have also began to make urdf a Bullet ragdoll using osgBullet, ask me if you interested in it