@@ -55,6 +55,7 @@ Contents
55
55
* [ Links] ( #links )
56
56
* [ Introduction] ( #intro )
57
57
* [ Use cases] ( #uses )
58
+ * [ Applications] ( #apps )
58
59
* [ Minimal example] ( #example )
59
60
* [ Visitors] ( #visitors )
60
61
* [ Supported types] ( #types )
@@ -107,6 +108,13 @@ Use cases
107
108
5 . Implementation of parsers for specific data formats, e.g., ` URDF ` .
108
109
109
110
111
+ <a name =" apps " ></a >
112
+ Applications
113
+ ------------
114
+
115
+ - < https://github.com/asherikov/ariles_urdf > : proof of concept ` URDF ` parser.
116
+ - < https://github.com/asherikov/intrometry > : telemetry collection library.
117
+
110
118
111
119
<a name =" example " ></a >
112
120
Minimal example
@@ -182,7 +190,7 @@ representation formats, in particular:
182
190
* ` Octave ` script, output only, no dependencies:
183
191
< https://asherikov.github.io/ariles/2/group__octave.html >
184
192
185
- * ` ROS ` parameter server, via standard ` ROS ` libs:
193
+ * ` ROS ` parameter server, via ` ROS ` libs:
186
194
< https://asherikov.github.io/ariles/2/group__rosparam.html >
187
195
188
196
* A set of flattened key-value pairs, output only, no dependencies:
@@ -191,9 +199,9 @@ representation formats, in particular:
191
199
* ` graphviz ` dot files for diagram generation:
192
200
< https://asherikov.github.io/ariles/2/group__graphviz.html >
193
201
194
- * ` ROS2 ` parameters, via standard ` rclcpp ` lib:
202
+ * ` ROS2 ` parameters, via ` rclcpp ` lib:
195
203
< https://asherikov.github.io/ariles/2/group__ros2param.html > ` ROS2 `
196
- parameters is not designed to fully reflect yaml structure as explained here
204
+ parameters are not designed to fully reflect yaml structure as explained here
197
205
< https://github.com/ros2/rcl/issues/463 > , so while ` ariles ` can dump and read
198
206
anything, there are certain workarounds in place that are described in more
199
207
details in the ` ROS2 ` demo [ ` ./tests/api_v2/demo_api_v2_ros2.cpp ` ]
0 commit comments