https://www-ui.is.s.u-tokyo.ac.jp/~takeo/papers/kexi_chi2011_roboshop.pdf
- When Professor Inami was at KMD
- It’s like using Photoshop to write various instructions on the layers of a room and have the robot execute them asynchronously.
robot task management
- It seems like FMRG SingleSite ~202310 is doing the same thing (blu3mo)
・This scenario shows that the system has to support asynchronous control. Besides, setting multiple tasks in a constrained location (Bob’s apartment) requires spatial and temporal coordination. Assigning each task individually would create unintentional time overlaps or gaps. The interface needs a time scheduling mechanism to address possible task conflicts and inefficiencies.
- That makes sense, right? (blu3mo)(blu3mo)
- Roboshop is also a UI for multiple tasks compared to previous studies.
-
Roboshop supports more structured sketching, called Rainbow Sketch, for the assignment and management of multiple tasks.
- Similar problems to FMRG SingleSite ~202310 could occur.
If you set the task of vacuuming the whole house and more than one vacuum robot is available, the system commands all the available vacuum robots to work cooperatively.
- This is similar to FMRG’s approach.
Users worry about the housework performed by the home robots. A housework recording and playing function will comfort the users. They will then be able to check the history of the housework by home robots.
-
The value lies in being able to confirm what has been done.
-
Things to consider
- How does it handle the timeline and the status of completion/incompletion?
- Tasks are represented as layers.
- Ah, so the subsequent operations come on top of the layers, so you can also understand the spatial dependencies. (blu3mo)(blu3mo)
- But they’re all crammed into one screen.
- How do they validate the UI for freeform operations?
- How does it handle the timeline and the status of completion/incompletion?