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
Currently, when there is an actuation error, the error dialog reports electrode IDs. This is not very useful to the user as it is difficult to map electrode IDs to the device view (electrode IDs are only shown to the user when hovering over a specific electrode).
I suggest that these error dialogs should show channel IDs, since these can be displayed on the device view using the "channel_labels" layer.
The text was updated successfully, but these errors were encountered:
In my mind, electrodes are what are being actuated (specific to the DMF chip, but not specific to the DropBot; e.g., the DropBot plugin may not even be installed) and channels are a DropBot implementation detail. @ryanfobel would you agree with this?1
That said, since we are only really concerned with the DropBot, I certainly agree that the electrode IDs are not particularly useful. However, this could be addressed by simply changing the id attribute of each electrode path in the SVG (i.e., the electrode IDs) to match the respective DropBot channel number. @ryanfobel what do you think?
1. In MicroDrop, all actuation-related code outside of the DropBot plugin operates on electrode IDs. The DropBot plugin then maps requests for actuation of electrodes to the corresponding hardware channels.
Currently, when there is an actuation error, the error dialog reports electrode IDs. This is not very useful to the user as it is difficult to map electrode IDs to the device view (electrode IDs are only shown to the user when hovering over a specific electrode).
I suggest that these error dialogs should show channel IDs, since these can be displayed on the device view using the "channel_labels" layer.
The text was updated successfully, but these errors were encountered: