Closed nunoguedelha closed 6 months ago
We held a kick-off meeting for this activity.
Attendees: Nuno Guedelha, Gabriele Nava
After discussing with Gabriele, we agreed on the following terms:
Nuno shall open, in an epic, an issue for each of the following steps. (#113) :white_check_mark:
Create the first controller block of the library: the YOGA++ controller #114 . (High priority, dependency of matlab-whole-body-simulator#32.
Define the granularity used in grouping the simulink blocks into library sub-system blocks. These sub-system blocks would populate the controllers library as well as the Kinematics and the Dynamics libraries.
Review it with Gabriele and Silvio.
Convert the remaining controllers into blocks in the controllers library and propagate it to the main models.
Implement the Kinematics library and propagate it to the other libraries and models.
Implement the Dynamics library and propagate it to the other libraries and models.
Notes:
library/simulink-library
.controllers
folder, e.g. whole-body-controllers/controllers/floating-base-balancing-torque-control
, are model examples integrating a controller block from the controllers library, eventually multiple blocks from the Kinematics or Dynamics libraries, with interface blocks for communicating either with the robot simulated on Gazebo, either with the robot simulated in matlab-whole-body-simulator
, either with the real robot.Add a mask to each controller for clearly defining its interface (Config
structure etc).
@gabrielenava , could you assign this to me, as we agreed, such that I convert it to an epic and add the sub-issues? Thx
The first step...
Create the first controller block of the library: the YOGA++ controller. (High priority, dependency of matlab-whole-body-simulator#32.
is top priority since we want to use the YOGA++ as a showcase for the matlab-whole-body-simulator
simulator (https://github.com/dic-iit/element_software-engineering/issues/24) which deadline is the 30th April.
It shall be the first issue (#114 ) under this Epic.
CC @traversaro , @DanielePucci
@gabrielenava could you please also assign #114 to me, and authorize me to add this repo to the board of https://github.com/dic-iit/matlab-whole-body-simulator.
@gabrielenava could you please also assign #114 to me, and authorize me to add this repo to the board of https://github.com/dic-iit/matlab-whole-body-simulator.
Done!
hello @traversaro
as nuno left the team some time ago and I am not aware of any plan for carrying on this activity, can I close this epic and all the associated issues for now?
Sure!
This repository implements a multitude of controllers that can be connected either to Gazebo, either to the real robot iCub. In order to facilitate the reuse of such controllers on other humanoid robots or their integration in other simulation frameworks that implement specific robot dynamics simulators like
matlab-whole-body-simulator
, we should create a library of controller blocks out of the models implemented in this repository:Once the library created, we shall integrate its blocks in the controller models implemented in this repository.
A first example of integration in an external framework, which motivated this task, can be found in https://github.com/dic-iit/matlab-whole-body-simulator/issues/32. This is also in line with what @gabrielenava wanted to do in https://github.com/robotology/whole-body-controllers/issues/95. The simulator in https://github.com/dic-iit/matlab-whole-body-simulator matches the requirements listed by @gabrielenava in that issue.