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
\page physicsplugin Understanding the Physics Plugin
2
2
3
-
This is an introduction to different physics engines and how they are integrated into the Gazebo Physics library.
4
-
5
-
## Gazebo Physics
6
-
7
-
The \ref gz::physics "Gazebo Physics" library integrates external physics engines into the Gazebo Simulation eco-system.
8
-
It allows users to select from multiple supported physics engines based on their simulation needs.
9
-
Its plugin interface loads physics engines with requested features at runtime.
3
+
The \ref gz::physics "Gazebo Physics" library integrates physics engines into the Gazebo Simulation eco-system.
4
+
Each physics engine is wrapped into a Gazebo Physics Plugin that can be loaded in a Gazebo simulation.
5
+
The Physics Plugin interface loads physics engines with the requested features at runtime.
10
6
It is also possible to integrate your own selected physics engine by writing a compatible plugin interface.
11
7
12
8
To get a more in-depth understanding of how the physics plugin works in Gazebo, we will start with some high level concepts and definitions.
13
9
14
10
<!-- TODO: add tutorial on how to write your own physics plugin -->
15
11
16
-
###High Level Concept
12
+
## High Level Concept
17
13
18
14
Conceptually, the physics plugin can be viewed from two sides of its interface: user vs. implementation.
19
15
@@ -22,7 +18,7 @@ The interface is made possible through the \ref gz::plugin "Gazebo Plugin" libra
22
18
This "user side interface" makes the Gazebo Physics library "callable" from other Gazebo libraries.
23
19
24
20
The implementation side interface handles specific implementations of each `Feature`.
25
-
Depending on what external physics engine we are using (DART, TPE etc.), the interface might be different.
21
+
Depending on what physics engine we are using in the plugin (DART, TPE etc.), the interface might be different.
26
22
This interface is more internal facing, i.e. used mostly inside the Gazebo Physics library.
27
23
28
24
The implementation of the physics plugin revolves around four key elements.
@@ -38,7 +34,7 @@ The implementation of the physics plugin revolves around four key elements.
38
34
FeaturePolicy is a "policy class" used to provide metadata to features about what kind of simulation engine they are going to be used in.
39
35
Many physics simulations software libraries model 3-dimensional systems, though some (like Box2d) only consider 2-dimensional systems.
40
36
A FeaturePolicy is used to customize Gazebo Physics' APIs by the number of dimensions (2 or 3) and also the floating point scalar type (float or double).
41
-
Dartsim and TPE reference implementations both use FeaturePolicy3d (3 dimensions, double).
37
+
(All of the currently supported physics engines use FeaturePolicy3d i.e. 3 dimensions and double.)
42
38
43
39
3. \ref gz::physics::Feature "Feature"
44
40
@@ -52,10 +48,10 @@ The implementation of the physics plugin revolves around four key elements.
52
48
FeatureLists can be constructed in hierarchies, e.g. a `FeatureList` can be passed into another `FeatureList`, and the set of all features in the new list will be the sum.
53
49
54
50
55
-
###FeatureList Definitions
51
+
## FeatureList Organization
56
52
57
-
This list of `FeatureLists`is specific to the implementation of `Dartsim`and `TPE-plugin`.
58
-
Users do not need to organize their own plugin implementations this way.
53
+
For example, here are the `FeatureLists`used in the implementation of the `Dartsim`physics engine.
54
+
Plugin implementations for other engines may choose to organize features into `FeatureLists` differently.
59
55
60
56
| Name | Definition |
61
57
|---|---|
@@ -71,92 +67,46 @@ Users do not need to organize their own plugin implementations this way.
71
67
| SimulationFeatures | updates `World` and everything within by defined stepsize |
72
68
| WorldFeatures | sets options like solver and collision detector |
73
69
74
-
### Dart vs. TPE
75
-
76
-
<!-- TODO: add Bullet once it's supported -->
77
-
<!-- ### Bullet -->
70
+
## Available Physics Plugins
78
71
79
72
Dart ([Dynamic Animation and Robotics Toolkit](https://dartsim.github.io/)) is an open source library that provides data structures and algorithms for kinematic and dynamic applications in robotics and computer animation.
80
73
It is the default physics engine used in Gazebo Simulation.
81
74
The source code for Dartsim plugin can be found in [Gazebo Physics repository](https://github.com/gazebosim/gz-physics/tree/main) under `dartsim` directory.
82
75
83
76
TPE ([Trivial Physics Engine](https://github.com/gazebosim/gz-physics/tree/main/tpe)) is an open source library created by Open Robotics that enables fast, inexpensive kinematics simulation for entities at large scale.
84
77
It supports higher-order fleet dynamics without real physics (eg. gravity, force, constraint etc.) and multi-machine synchronization.
85
-
Gazebo support for TPE targets [Citadel](https://gazebosim.org/docs/citadel) and onward releases.
86
78
The source code for TPE plugin can be found in [Gazebo Physics repository](https://github.com/gazebosim/gz-physics/tree/main) under the `tpe/plugin` directory.
87
79
88
-
The following is a list of features supported by each physics engine to help users select one that fits their needs.
80
+
Bullet ([Bullet3 Physics Engine](https://github.com/bulletphysics/bullet3)) is an open source library that supports real-time collision detection and multi-physics simulation for robotics and other application domains.
81
+
Since Bullet supports two different APIs - a rigid-body API and a multibody API - with different physics implementations, there are two available plugin implementations:
82
+
- The `bullet` plugin implements the rigid-body API, and the source code can be found in [Gazebo Physics repository](https://github.com/gazebosim/gz-physics/tree/main) under the `bullet` directory.
83
+
- The `bullet-featherstone` plugin implements the multibody API (based on Featherstone's algorithms), and the source code can be found in [Gazebo Physics repository](https://github.com/gazebosim/gz-physics/tree/main) under the `bullet-featherstone` directory.
89
84
90
-
####Entity Comparison
85
+
### Entity Comparison
91
86
92
-
The following is a table of `Entity` names used in Gazebo Physics plugin interface, Dart and TPE.
87
+
The following is a table of `Entity` names used in the Gazebo Physics plugin interface, mapped to corresponding types in each supported physics engine.
93
88
Entities are arranged in top-down hierarchical order.
94
89
95
-
| Physics Plugin | Dart | TPE |
96
-
|:-:|:-:|:-:|
97
-
| Engine | Engine | Engine |
98
-
| World | World | World |
99
-
| Frame | Frame | N/A |
100
-
| Model | Skeleton | Model |
101
-
| Joint | Joint | N/A |
102
-
| Link | BodyNode | Link |
103
-
| Shape | Shape | Collision |
104
-
| Box/Sphere/Cylinder etc. | Box/Sphere/Cylinder etc. | Box/Sphere/Cylinder/Mesh etc. |
105
-
106
-
#### Feature Comparison
107
-
108
-
The following is a table of implemented `Features` of Dartsim and TPE-Plugin.
| Box/Sphere/Cylinder etc. | Box/Sphere/Cylinder etc. | Box/Sphere/Cylinder etc. | Box/Sphere/Cylinder etc. | Box/Sphere/Cylinder etc. |
100
+
101
+
<sup>1</sup> Frames are implicitly attached to joints, links, collisions or models in the Bullet physics engine.
102
+
103
+
<sup>2</sup> The Bullet rigid-body API does not have a concept of a Model, but the plugin maintains a collection of Links and Joints in the engine associated with a Model.
104
+
105
+
<sup>3</sup> There are multiple types in the Bullet Featherstone API to interact with joints, such as btMultiBodyJointLimitConstraint, btMultiBodyJointMotor and btMultiBodyJointFeedback.
106
+
107
+
### Feature Comparison
108
+
109
+
For a list of all available `Features` in the Gazebo Physics library, check the classes inherited from `Feature` in the [Gazebo Physics API](https://gazebosim.org/api/physics/8/hierarchy.html).
110
+
To check if a physics plugin implements a particular `Feature`, check the `FeatureLists` supported by that plugin as specified in the plugin.cc file, for example, [dartsim/src/plugin.cc](https://github.com/gazebosim/gz-physics/blob/main/dartsim/src/plugin.cc).
111
+
112
+
Next, check out the tutorial on \ref pluginloading "Loading physics plugins" on how to load a plugin and access a specific `Feature` interface of the plugin programmatically.
0 commit comments