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

2019/tasks/robot eye #553

Closed
wants to merge 1 commit into from
Closed

Conversation

justinhart
Copy link
Member

Added the Robot Eye task.

@justinhart justinhart changed the base branch from master to 2019/restructure February 9, 2019 01:54
@kyordhel
Copy link
Contributor

kyordhel commented Feb 13, 2019

@justinhart Please edit the description of the PR explaining what this task is about (i.e. TL,DR; version).

@kyordhel kyordhel requested a review from a team February 13, 2019 10:24
@kyordhel kyordhel self-requested a review February 13, 2019 11:51
Copy link
Contributor

@kyordhel kyordhel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get the idea behind this, can't either find its relevance to @Home, and I don't think this fits under Housekeeper. Besides, where are we getting those clothes from?

Robot giving an informed opinion on operator's choice

For real? We don't have time for a parade in AtHome. Besides, I'm not taking fashion advice from a piece of scrap.

Robot handing objects

From a technical point of view, this overlaps with I want this and Landry sort, hence it's redundant

@@ -0,0 +1,40 @@
\section{Robot Eye [Housekeeper]}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the name for something more descriptive? I think in English the term valet is quite adequate.

% This test focuses on object perception, manipulation, and planning.

\subsection{Main Goal}
The operator is getting dressed and announces the occasion to the robot, which must help them to pick an appropriate ensemble for the occasion.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main goal is not clear. This is more like the background. From reading this I don't know what the robot must do, and I've helped my wife to choose an attire countless times. There is not even a scoresheet!


\subsection{Setup}
\begin{itemize}[nosep]
\item \textbf{Location:} Living room
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not in bedroom? I always dress up in the bedroom.

\begin{itemize}[nosep]
\item \textbf{Location:} Living room

\item \textbf{Clothing:} There is a rack of clothing from which the operator must choose, with shoes in a bin on the floor.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This rack of clothes must be added to Objects section under General Rules.
I'm quite confident the LOC will give us the finger if we need to go Primark/H&M for clothing nobody is going to use.


\item \textbf{Clothing:} There is a rack of clothing from which the operator must choose, with shoes in a bin on the floor.
\begin{itemize}[nosep]
\item\textit{Distractor objects}: There should be distractor objects in this set which are irrelevant to the scenarios named.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too vague. What is an Scenario? The word scenario is reserved in the rulebook for the Party Host and Housekeeper Scenarios.

\item \textbf{Clothing:} There is a rack of clothing from which the operator must choose, with shoes in a bin on the floor.
\begin{itemize}[nosep]
\item\textit{Distractor objects}: There should be distractor objects in this set which are irrelevant to the scenarios named.
\item\textit{Target objects}: There should be target objects (more than one per scenario) which fit the scenarios described.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word scenario is reserved in the rulebook for the Party Host and Housekeeper Scenarios.

\end{itemize}

\subsection{OC instructions}
5 hours before the test:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setup days | 1 day before the test | 2 hours before the test

Copy link
Member

@johaq johaq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @kyordhel. This seems impractical just from an organizational standpoint. Do we need to buy three pairs of shoes just for this task? In Montreal this would have meant 9 pairs, 3 for each arena.

Also for which stage is this task intended?

@justinhart
Copy link
Member Author

This probably needs a bit more work before it's ready for RoboCup@Home. I think that the core idea is good, but we probably need to workshop it more and may re-propose it in 2020.

@kyordhel
Copy link
Contributor

Based on #536 comments by @swachsmu and @iocchi, I think we can run some analysis on the task you're proposing.

I'm working on a scientific rulebook to re-visit all 2019 tests from a scientific perspective (challenges, state of the art research, and contributions), include the roadmaps, and future tests. It's a hell of a work, but I think you can help by writing this and other tests/tasks as research milestones there.

Will let you know when is pushed.

@MatthijsBurgh
Copy link
Collaborator

Most have been said. I just wanted to add the following.

Computervision, AI and Robotics are pretty close. Challenges should always be focused around Robotics. This challenge feels way too much Computervision and AI.

@kyordhel kyordhel closed this May 30, 2019
@LeroyR LeroyR deleted the 2019/tasks/RobotEye branch November 25, 2024 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants