pyrobots
A Python toolset for asynchronous, event-based control of robots
Science Score: 28.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
○codemeta.json file
-
○.zenodo.json file
-
○DOI references
-
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (15.2%) to scientific vocabulary
Keywords
Repository
A Python toolset for asynchronous, event-based control of robots
Basic Info
- Host: GitHub
- Owner: severin-lemaignan
- License: isc
- Language: Python
- Default Branch: master
- Homepage: http://pyrobots.readthedocs.org
- Size: 1.23 MB
Statistics
- Stars: 14
- Watchers: 11
- Forks: 6
- Open Issues: 1
- Releases: 0
Topics
Metadata Files
README.md
pyRobots: a toolkit for robot executive control
pyRobots provides a set of Python decorators to easily turn standard functions
into background tasks which can be cancelled at anytime and to make your controller
resource aware (no, a robot can not turn left AND right at the same time).
It also provides a event-based mechanism to monitor specific conditions and asynchronously trigger actions.
It finally provides a library of convenient tools to manage poses in a uniform way (quaternions, Euler angles and 4D matrices, I look at you) and to interface with existing middlewares (ROS, naoqi, aseba...).
pyRobots took some inspiration from the
URBI language.
If you use this code for your academic work, please cite it!
Installation
$ pip install pyRobots
(or, of course, from the source)
Main features
- Turns any Python function into a background action with the decorator
@action. - Robot actions are non-blocking by default: they are instanciated as futures (lightweight threads),
- Actions can be cancelled at any time via signals (the
ActionCancelledsignal is raised). - Lock specific resources with a simple
@lock(...)in front of the actions. When starting, actions will wait for resources to be available if needed. - Supports compound resources (like
WHEELS==LEFTWHEEL+RIGHTWHEEL) - Create event with
robot.whenever(<condition>).do(<action>) - Poses are managed explicitely and can easily be transformed from one reference frame to another one (integrates with ROS TF when available).
- Extensive logging support to debug and replay experiments.
Support for a particular robot only require to subclass GenericRobot for this
robot (and, obviously, to code the actions you want your robot to perform).
Documentation
Head to readthedocs. Sparse for now.
Minimum Working Example
...that includes the creation of a specific robot
```python import time from robots import GenericRobot from robots.decorators import action, lock from robots.resources import Resource from robots.signals import ActionCancelled
create a 'lockable' resource for our robot
WHEELS = Resource("wheels")
class MyRobot(GenericRobot):
def __init__(self):
super(MyRobot, self).__init__()
# create (and set) one element in the robot's state. Here a bumper.
self.state.my_bumper = False
# do whatever other initialization you need :-)
def send_goal(self, pose):
# move your robot using your favorite middleware
print("Starting to move towards %s" % pose)
def stop(self):
# stop your robot using your favorite middleware
print("Motion stopped")
def whatever_lowlevel_method_you_need(self):
pass
@lock(WHEELS) @action def move_forward(robot): """ We write action in a simple imperative, blocking way. """
# the target pose: simply x += 1.0m in the robot's frame. pyRobots
# will handle the frames transformations as needed.
target = [1.0, 0., 0., "base_link"]
try:
robot.send_goal(target)
while(robot.pose.distance(robot.pose.myself(), target) > 0.1):
# robot.sleep is exactly like time.sleep, except it lets the pyrobots
# signals pass through.
robot.sleep(0.5)
print("Motion succeeded")
except ActionCancelled:
# if the action is cancelled, clean up your state
robot.stop()
with MyRobot() as robot:
# Turn on DEBUG logging.
# Shortcut for logging.getLogger("robots").setLevel(logging.DEBUG)
robot.debug()
robot.whenever("my_bumper", value = True).do(move_forward)
try:
while True:
time.sleep(0.5)
except KeyboardInterrupt:
pass
```
Owner
- Name: Séverin Lemaignan
- Login: severin-lemaignan
- Kind: user
- Location: Barcelona, Spain
- Company: PAL Robotics
- Website: academia.skadge.org
- Twitter: skadge
- Repositories: 81
- Profile: https://github.com/severin-lemaignan
Citation (CITATION)
If you use pyRobots for your academic work, please cite this paper:
Lemaignan, Hosseini, Dillenbourg, "pyRobots: a Toolset for Robot Executive Control". IROS 2015.
For LaTeX users, you can use this BibTeX entry:
@inproceedings{lemaignan2015pyrobots,
author = {S\'everin Lemaignan and Anahita Hosseini and Pierre Dillenbourg},
title = {pyRobots: a Toolset for Robot Executive Control},
booktitle = {Proceedings of the 2015 IEEE/RSJ International Conference on Intelligent Robots and Systems},
year = {2015},
url = {https://github.com/chili-epfl/pyrobots}
}
GitHub Events
Total
Last Year
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 2
- Total pull requests: 6
- Average time to close issues: 8 months
- Average time to close pull requests: 17 days
- Total issue authors: 2
- Total pull request authors: 3
- Average comments per issue: 0.0
- Average comments per pull request: 1.0
- Merged pull requests: 3
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- dhood (1)
- paulolc (1)
Pull Request Authors
- anaDachia (4)
- dhood (1)
- lischenko (1)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- futures *
- numpy *
- futures *