Lorenzo Rapetti
Lorenzo Rapetti
**Describe the bug** With @Zweisteine96 we noticed difference in the linear/angular serialization used used for iFeel data: - in the thrift message we use angular/linear for the pose (see [here](https://github.com/robotology/wearables/blob/59ea45c9c80dec9317790c5a4b8712a31a7d9ee1/msgs/thrift/WearableData.thrift#L55-L56)...
if the `IWearFrameVisualizerModule` is launched with some desired displacement offset, such as [iWearFrameVisualizerExample.txt](https://github.com/robotology/wearables/files/8095968/iWearFrameVisualizerExample.txt), all the frames seems to be visualized in the origin. It seems in fact that the transformation...
We have observed that launching an application with the `IWearRemapper` plus the `IWearLogger`, we were not able to terminate it correctly. In particular, we observed that the logger was able...
The idea is to add some simple example/test applications that can both serve new users to get in touch with the library and can avoid regression problems such as the...
Following the problem experienced in https://github.com/robotology/wearables/issues/91, we could add a CI check in order to spot this kind of problem. Example code in https://github.com/robotology/robotology-superbuild/pull/521.
It has to be developed an interface that map a [`multipleAnalogSensor`](http://www.yarp.it/group__dev__iface__multiple__analog.html) interface, into `IWear` interface.
As discussed in https://github.com/robotology/wearables/pull/25, we should update the [`iCubWearableDevice`](https://github.com/robotology/wearables/tree/master/devices/ICub) in order to use `RemoteControlBoardRemapper`. cc @diegoferigo @Yeshasvitvs
As @diegoferigo mentioned in https://github.com/robotology/wearables/pull/52#discussion_r327601554, this flag seems to be very specific for an application while the device is generic. A better solution would be to remove this flag from...
**Describe the bug** With @Zweisteine96 we noticed difference in the linear/angular serialization used used for iFeel data: - in the thrift message we use angular/linear for the pose (see [here](https://github.com/robotology/wearables/blob/59ea45c9c80dec9317790c5a4b8712a31a7d9ee1/msgs/thrift/WearableData.thrift#L55-L56)...
if the `IWearFrameVisualizerModule` is launched with some desired displacement offset, such as [iWearFrameVisualizerExample.txt](https://github.com/robotology/wearables/files/8095968/iWearFrameVisualizerExample.txt), all the frames seems to be visualized in the origin. It seems in fact that the transformation...