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
Released RELEASED

Package Description

Python interfaces for managing ROCON scheduler requests.

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.

CHANGELOG

Change history

0.7.0 (2014-05-28)

0.6.6 (2014-04-01)

  • Add thread locking for schedulers and requesters (#24).
  • Rename ResourceReply class ActiveRequest (#27).
  • Move resources module to another package (#26).
  • Remove some deprecated methods: abort(), free(), reject(), release() (#21)
  • Revise status labels and transitions.

0.6.5 (2013-12-19)

  • Experimental Python module for testing scheduler_msgs interface.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged concert_scheduler_requests at answers.ros.org

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
Released UNRELEASED

Package Description

Python interfaces for managing ROCON scheduler requests.

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.

CHANGELOG

Change history

0.7.0 (2014-05-28)

0.6.6 (2014-04-01)

  • Add thread locking for schedulers and requesters (#24).
  • Rename ResourceReply class ActiveRequest (#27).
  • Move resources module to another package (#26).
  • Remove some deprecated methods: abort(), free(), reject(), release() (#21)
  • Revise status labels and transitions.

0.6.5 (2013-12-19)

  • Experimental Python module for testing scheduler_msgs interface.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged concert_scheduler_requests at answers.ros.org