-
Notifications
You must be signed in to change notification settings - Fork 44
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
WIP: mdr robocup tasks/find my mates #120
WIP: mdr robocup tasks/find my mates #120
Conversation
With this commit the launch files include nodes that are required by the node to run properly. E.g. mdr_question_answering now also executes mdr_speech_recognition and mdr_speech_matching.
This commit provides the pkg structure for the "find my mate" task of the RoboCup@Home competition. The state machine and launch file are not defined, yet. This will be addressed in the upcoming commits.
cmake_minimum_required(VERSION 2.8.3) | ||
project(mdr_find_my_mates) | ||
|
||
## Compile as C++11, supported in ROS Kinetic and newer |
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.
@argenos @alex-mitrevski what's the consensus for removing the auto-generated comments in CMakeLists.txt
? I personally prefer to remove them so the file is not too cluttered.
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.
I'm also in favor of removing it.
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.
I always remove those.
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.
Will do at some point.
This commit provides a description of the task, the sub-tasks, the goal and restrictions. Addtionally, a first state machine of the scenario is defined. The state machine focuses on one loop only and covers the best case of the scenario. In following commits further adjustments to the state machine need to be done.
This commit provides a more elaborated state machine of the scenario. It includes the second loop withing the scenario (search and analysis of a second guest) and the exit transitions in case of failure.
The following figure visualizes the scenario up to this point: It can be noted that some of the actions are related with each other. For example the _request_actions can most probably originate from the same action with a different content. The action Localize Person includes the following sub-processes:
The actions Analyze Location and Analyze Person refer to perception and the recognition of identifying objects. |
The aim is to define the "find my mates" scenario for the RoboCup@Home competition. This pull request addresses issue #105