You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if the IWearFrameVisualizerModule is launched with some desired displacement offset, such as iWearFrameVisualizerExample.txt, all the frames seems to be visualized in the origin.
It seems in fact that the transformation that is read from the configuration file in here, is never used, but rather overwritten here by the measurement
Either they are provided online or by the config file. Either they are provided by config file or online or both.
If a frame info is loaded from the config file.
If new info are provided online, the frame position and rotations get updated.
if not they will not get updated and last info will be used.
At least this is the idea.
if the
IWearFrameVisualizerModule
is launched with some desired displacement offset, such asiWearFrameVisualizerExample.txt, all the frames seems to be visualized in the origin.
It seems in fact that the transformation that is read from the configuration file in here, is never used, but rather overwritten here by the measurement
cc @RiccardoGrieco @kouroshD
The text was updated successfully, but these errors were encountered: