Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content

BEC MotorMap

Summary

The motor_map API is unclear to me. There are a couple of commands for which I do not know what they exactly do.

Observed behavior

image

  • set_background_value
  • set_num_dim_points both do not seem to have any effect. Also not sure what the purpose was ^^
  • set_precision seems irrelevant for the visualisation, probably still from control panel.

Also set_data() reveals that the app stores all positions. I am not sure if this is a good idea, or at least a better cleanup policy should be defined, i.e. a maximum storage of the last 10000 points.

In addition, I am failing to reduce the trace of the motors as you can see in the screenshot. Maybe the relevant function is not exposed.

image

Proposed solution

Put this on hold until we take time to go through the full API of all widgets, to decide which functions are relevant, can be consolidated or hidden for users.