Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide visual indications of near-future robot motions #22

Closed
amalnanavati opened this issue Apr 19, 2023 · 2 comments · Fixed by #54
Closed

Provide visual indications of near-future robot motions #22

amalnanavati opened this issue Apr 19, 2023 · 2 comments · Fixed by #54
Assignees
Labels
critical-path Issues that are critical path for deployment

Comments

@amalnanavati
Copy link
Contributor

Users and caregivers need some mental model of future robot motion to decide how to best interact with it. For example:

  1. Consider the case where there is food on the fork that the user doesn't want to eat, and they call a caregiver to remove it. There should be a clear indication of whether the robot will move soon or not (e.g., is it fully stationary or is it just stationary because it's planning) so they can decide whether to approach it. See Atharva's comment here.
  2. Consider the case where the robot is getting close enough to the user that they are getting worries, but not so close that they feel in imminent danger. At that time, they would probably like to know whether the robot will stop soon or keep going to decide whether to hit the e-stop or not.

In both cases, the crucial point is that users' should receive a visual indication of the robot's near-future motions.

One idea is the following:

  1. On screens where the robot will not move, write that on the screen so users' know it is safe to approach the robot.
  2. On screens where the robot will move, show a progress bar so users can know how much longer (roughly) they can expect the robot to move. A ++ is to first show the progress bar as one color for planning time, and then one color for motion time, so users get a very clear idea of what proportion of distance the robot will keep moving.
@amalnanavati amalnanavati mentioned this issue Apr 19, 2023
2 tasks
@Raidakarim Raidakarim self-assigned this Apr 23, 2023
@Raidakarim
Copy link
Contributor

Raidakarim commented Apr 25, 2023

Here is a slidedeck with some initial thoughts of mine. The comments on this slidedeck includes feedback for improvement from Amal @amalnanavati. This is the javascript progress bar library that can be useful for implementation.

I currently don't have the time to actively work on this issue. So, if anyone in the web app team wants to assign it to themselves, please feel free to. Otherwise, I can self-assign this issue to myself in the future when I am done with my current issues.

@Raidakarim Raidakarim removed their assignment Apr 25, 2023
@amalnanavati
Copy link
Contributor Author

This issue is blocked by #34 but is a priority once that is merged in.

@amalnanavati amalnanavati added the critical-path Issues that are critical path for deployment label May 9, 2023
@Raidakarim Raidakarim self-assigned this May 11, 2023
@Raidakarim Raidakarim mentioned this issue May 18, 2023
4 tasks
@amalnanavati amalnanavati linked a pull request May 24, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical-path Issues that are critical path for deployment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants