Closed drdanz closed 3 years ago
The structure of OdometryData
is:
double odom_x;
double odom_y;
double odom_theta;
double base_vel_x;
double base_vel_y;
double base_vel_theta;
double odom_vel_x;
double odom_vel_y;
double odom_vel_theta;
We can encode this in 2 ways:
I personally prefer the first solution, because to the 8 channels you have to add also the others if you have enabled the log of other quantities and may mess up the structure of the mat file.
What do you think about it @randaz81 @drdanz @AlexAntn @traversaro ?
I am also for the first solution.
From the logic point of view, another possible solution would be to have three channels, each of them consisting of three values inside (if you notice, three values are positions, three values are velocities, three values are velocities in a different coordinate frame). But I don't know if it is feasible, so the first solution is ok.
According to @randaz81 the data he would like to dump on the R1 robot is the odometry data coming from the
ILocalization2D
interface.Data is generated by the
odomLocalizer
device, and is published on the yarp network bylocalization2DServer
(nowlocalization2D_nws_yarp
)