-
Notifications
You must be signed in to change notification settings - Fork 62
First draft of Restaurant 2026 #1000
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
base: master
Are you sure you want to change the base?
Conversation
|
I think this looks ok, just a minor adjustment to replace the term Deus ex Machina to be consistent with new terminology |
|
Hi, @TKang-P , yesterday i had some time to re-watch some of the RoboCup stream of the Restaurant task and my notes from our first RoboCup, and I think we should clarify a couple of things:
|
SparkRibeiro21
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please check the previous comment
|
Apply feedback:
|
SparkRibeiro21
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome :)
tasks/Restaurant.tex
Outdated
| \item The robot must interact with the customers directly. Teams are not allowed to assist or instruct them. | ||
| \item The robot may use up to one minute to instruct the \textit{Professional Barman}. | ||
| \item The robot may request guidance to a customer's table. | ||
| \item The robot may use up to two minutes to instruct the \textit{Professional Barman} per oreder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| \item The robot may use up to two minutes to instruct the \textit{Professional Barman} per oreder. | |
| \item The robot may use up to two minutes to instruct the \textit{Professional Barman} per order. |
|
The term "facing the customer seating area" is ambiguous and potentially misleading because the robot’s field of view is limited. Even if the robot starts facing a few tables, customers may be seated at any table, including those outside its initial field of vision. The starting position is usually next to the counter that may or may not be facing the costumers area. |
The term "facing the customer seating area" is anything but ambiguous. There is an area where customers can be sitting... The goal of this update is to provide information to teams of what happens in competitions but is not in the rule book. The starting position in not "usually" next to the counter, it has to be always next to the counter because this is stated in the rule book, any competition that failed to do so, is not following the rule book. Facing the customers area is what happens at every competition, RoboCup 2023, 2024 and 2025 have been so. The goal of this, is that this "unwritten rule" is stated in the rule book for clarity and transparency. Not to be a rule which only teams who have previously been in a competition know about. |
As long as you can guarantee that the counter and the tables will be arranged in a way that satisfies both conditions (“next to the counter” and “facing customers”), I’m fine with it. Otherwise, the robots may find the customers but won’t know where the counter is! |
Description
Updates for Restaurant 2026
To encourage teams to use barman rather than being stuck in the middle of the restaurant.
I didn't include the barman's guidance/pointing procedure that automatically executed after 1 minute.
Because it will not change the robot's behavior and only make it look worse.