ROS Index
|
concert_scheduler_requests package from concert_scheduling repoconcert_resource_pool concert_scheduler_requests concert_scheduling concert_simple_scheduler |
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.7.0 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/utexas-bwi/concert_scheduling.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2014-05-28 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Jack O'Quin
Authors
- Jack O'Quin
Overview
The concert_scheduler_requests ROS package provides Python interfaces for managing scheduler requests within the Robotics in Concert framework.
Because different systems require scheduling policies, the ROCON design allows for multiple scheduler implementations. This package supplies a common infrastructure for various schedulers to use.
Scheduler Topics
The ROCON scheduler runs as a ROS node on same master as the ROCON conductor, the rocon services and other Solution components. It subscribes to an allocation topic named /rocon_scheduler of type scheduler_msgs/SchedulerRequests. Any ROCON service or application sending messages to that topic is called a requester. Each requester assigns itself a universally unique identifier and subscribes to a feedback topic using the hexadecimal string representation of its UUID, in the form /rocon_scheduler_0123456789abcdef0123456789abcdef. The scheduler will provide status feedback on that topic via scheduler_msgs/SchedulerRequests messages.
Scheduler Resource Requests
Each scheduler_msgs/SchedulerRequests message describes all resources currently desired by that requester. The status of each resource request is passed back and forth between the requester and the scheduler via scheduler_msgs/Request elements contained in the allocation and feedback topics.
Handling these messages and managing the states of each resource request can be quite tricky, because state changes flow over the two topics simultaneously. So, both schedulers and requesters need to perform state transitions carefully and consistently for every request.
This package provides interfaces for schedulers and requesters to perform those transitions correctly.
Change history
0.7.0 (2014-05-28)
- Target version for Indigo Igloo release.
- Rename rocon_scheduler_requests package to concert_scheduler_requests, replacing the earlier version.
0.6.6 (2014-04-01)
0.6.5 (2013-12-19)
- Experimental Python module for testing scheduler_msgs interface.
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged concert_scheduler_requests at Robotics Stack Exchange
|
|
concert_scheduler_requests package from concert_scheduling repoconcert_resource_pool concert_scheduler_requests concert_scheduling concert_simple_scheduler |
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.7.0 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/utexas-bwi/concert_scheduling.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2014-05-28 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Jack O'Quin
Authors
- Jack O'Quin
Overview
The concert_scheduler_requests ROS package provides Python interfaces for managing scheduler requests within the Robotics in Concert framework.
Because different systems require scheduling policies, the ROCON design allows for multiple scheduler implementations. This package supplies a common infrastructure for various schedulers to use.
Scheduler Topics
The ROCON scheduler runs as a ROS node on same master as the ROCON conductor, the rocon services and other Solution components. It subscribes to an allocation topic named /rocon_scheduler of type scheduler_msgs/SchedulerRequests. Any ROCON service or application sending messages to that topic is called a requester. Each requester assigns itself a universally unique identifier and subscribes to a feedback topic using the hexadecimal string representation of its UUID, in the form /rocon_scheduler_0123456789abcdef0123456789abcdef. The scheduler will provide status feedback on that topic via scheduler_msgs/SchedulerRequests messages.
Scheduler Resource Requests
Each scheduler_msgs/SchedulerRequests message describes all resources currently desired by that requester. The status of each resource request is passed back and forth between the requester and the scheduler via scheduler_msgs/Request elements contained in the allocation and feedback topics.
Handling these messages and managing the states of each resource request can be quite tricky, because state changes flow over the two topics simultaneously. So, both schedulers and requesters need to perform state transitions carefully and consistently for every request.
This package provides interfaces for schedulers and requesters to perform those transitions correctly.
Change history
0.7.0 (2014-05-28)
- Target version for Indigo Igloo release.
- Rename rocon_scheduler_requests package to concert_scheduler_requests, replacing the earlier version.
0.6.6 (2014-04-01)
0.6.5 (2013-12-19)
- Experimental Python module for testing scheduler_msgs interface.