You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,11 +115,11 @@ The `action_result` is an enumerated value denoting the result of the action (us
115
115
116
116
### Standard Communication Channels
117
117
118
-
Tasks and robot definition files declare actions and observations, and these files are include through [BenchBot Add-ons](https://github.com/roboticvisionorg/benchbot_addons). The add-on creator is free to add and declare channels as they please, but it is a better experience for all if channel definitions are as consistent as possible across the BenchBot ecosystem.
118
+
Tasks and robot definition files declare actions and observations, and these files are include through [BenchBot add-ons](https://github.com/roboticvisionorg/benchbot_addons). The add-on creator is free to add and declare channels as they please, but it is a better experience for all if channel definitions are as consistent as possible across the BenchBot ecosystem.
119
119
120
120
So if you're adding a robot that move between a set of poses, declare a channel called `'move_next` with no arguments. Likewise, a robot that receives image observations should use a channel named `'image_rgb'` with the same format as described below. Feel free to implement the channels however you please for your robot, but consistent interfaces should always be preferred.
121
121
122
-
If you encounter a task using non-standard channel configurations, the API has all the functionality you need as a user to handle them (`actions` & `config` properties, plus observation dict returned by `step()`& `reset()`). On the other hand, maybe the non-standard channel should be a new standard. New standard communication channels are always welcome; please open a pull request with the details!
122
+
If you encounter a task using non-standard channel configurations, the API has all the functionality you need as a user to handle them (`actions`, `config`, & `observations` properties). On the other hand, maybe the non-standard channel should be a new standard. New standard communication channels are always welcome; please open a pull request with the details!
123
123
124
124
#### Standard action channels:
125
125
@@ -164,6 +164,7 @@ The API handles communication for all parts of the BenchBot system, including co
|`actions`| Returns the list of actions currently available to the agent. This will update as actions are performed in the environment (for example if the agent has collided with an obstacle this list will be empty). |
167
+
|`observations`| Returns the lists of observations available to the agent. |
167
168
|`step(action, **action_args)`| Performs the requested action with the provided named action arguments. See [Using the API to communicate with a robot](#using-the-api-to-communicate-with-a-robot) above for further details. |
SUCCESS : Action has finished successfully and the robot is ready for a new action
36
-
FINISHED : Action has finished successfully and the robot has finished all its goals
37
-
COLLISION : Action has not finished successfully and the robot has collided with an obstacle
35
+
36
+
Values
37
+
------
38
+
SUCCESS :
39
+
Action succeeded, and the robot is ready for a new action
40
+
FINISHED :
41
+
Action succeeded, and the robot is finished in the current scene
42
+
COLLISION :
43
+
Action failed, and the robot has colliding with an obstacle
38
44
"""
39
45
SUCCESS=0,
40
46
FINISHED=1,
41
47
COLLISION=2
42
48
43
49
44
50
classBenchBot(object):
45
-
"""BenchBot handles communication between the client and server systems, and abstracts away hardware and simulation, such that code written to be run by BenchBot will run with either a real or simulated robot"""
46
-
47
-
SUPPORTED_ACTIONS= {
48
-
'_debug_move': [],
49
-
'move_next': [],
50
-
'move_distance': ['distance'],
51
-
'move_angle': ['angle']
52
-
}
53
-
51
+
"""BenchBot handles communication between the client and server systems,
52
+
and abstracts away hardware and simulation, such that code written to be
53
+
run by BenchBot will run with either a real or simulated robot
54
+
"""
54
55
@unique
55
56
classRouteType(Enum):
56
-
""" """
57
+
"""Enum denoting type of route (used in building routes when talking
0 commit comments