ROS IndexNo version for distro humble showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro jazzy showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro kilted showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro rolling showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro galactic showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro iron showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro melodic showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged challenge_navigation at Robotics Stack Exchange
No version for distro noetic showing github. Known supported distros are highlighted in the buttons above.
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | TODO |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | RoboCup challenge implementations |
| Checkout URI | https://github.com/tue-robotics/tue_robocup.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-08-13 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | robocup-home |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
No description available
Additional Links
No additional links.
Maintainers
- Rein Appeldoorn
Authors
No additional authors.
Challenge Navigation 2016
Responsible: Rein Appeldoorn
Test Log
- 2016-01-12: Performed fine, same state as rwc 2015. No person detected implemented yet.
- 2016-01-12: Performed test with object and human recognition, works fine except for the segmentation, we need a z-min z-max option in segment function.
Setup
amigo1/sergio1:
astart/sstart # (if not already running)
amigo2/sergio1:
ahardware/shardware: base, spindle, arms (left-arm is used) head
amigo1/sergio1:
amiddle/smiddle
amigo3:
rosrun challenge_navigation challenge_navigation.py [robot_name]
During a real competition
On the dev PC:
sshamigo3 #This will not work because amigo is unplugged
During the challenge
- The robot enters the arena
- The robot will (try to) go to the first waypoint (dinner_table) and finally say whether it reached its goal or not. The idea of this challenge is to demonstrate flexibility of the navigation: if one path appears to be blocked, the robot should be able to either replan or clear the way to its goal. So don’t be easy on the navigation! Block a (few) paths to test this!
- The robot will (try to) go to the second waypoint (black_cabinet2) and finally say whether it reached its goal or not. Again, you may want to block a path to test the navigation.
- After this message the robot will go to the exit
During a real competition
- Plug the network cable back in
- The sshamigo3 will connect
- type ‘hear continue’ in the sshamigo3 console.
CHANGELOG
No CHANGELOG found.
Package Dependencies
| Deps | Name |
|---|---|
| rospy | |
| robot_skills | |
| robot_smach_states | |
| catkin |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.