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: configuration/packages/configuring-route-server.rst
+127-1Lines changed: 127 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,17 @@ Server Parameters
81
81
Description
82
82
The maximum planning time to use.
83
83
84
+
:costmap_topic:
85
+
86
+
============== ============================
87
+
Type Default
88
+
-------------- ----------------------------
89
+
string 'global_costmap/costmap_raw'
90
+
============== ============================
91
+
92
+
Description
93
+
The costmap to use for the server-level costmap subscriber. This is created to aid the goal intent extractor (if BFS-based terminal route node finding is enabled) and also shared with the Collision Monitor Operation and Costmap Edge Scorer if set to the same topic. Otherwise, those plugins will create their own subscribers to their respective costmap topics.
94
+
84
95
:tracker_update_rate:
85
96
86
97
============== ========
@@ -169,6 +180,39 @@ Server Parameters
169
180
Description
170
181
Whether pruning the goal node from the route due to it being spatially past the goal pose requested (pose requests only ``use_poses``).
171
182
183
+
:enable_nn_search:
184
+
185
+
============== ===============
186
+
Type Default
187
+
-------------- ---------------
188
+
bool true
189
+
============== ===============
190
+
191
+
Description
192
+
Whether to use Breadth-first search to find the nearest traversible node (true) or simply the nearest node (false) for the start and goal when using pose requests.
193
+
194
+
:max_nn_search_iterations:
195
+
196
+
============== ===============
197
+
Type Default
198
+
-------------- ---------------
199
+
int 10000
200
+
============== ===============
201
+
202
+
Description
203
+
The maximum number of iterations to perform Breadth-first search to find the start and goal closest traversible nodes.
204
+
205
+
:num_nearest_nodes:
206
+
207
+
============== ===============
208
+
Type Default
209
+
-------------- ---------------
210
+
int 5
211
+
============== ===============
212
+
213
+
Description
214
+
The number of nearest-neighors to extract from a Kd-tree in order to check against in the Breadth-first search.
215
+
172
216
:graph_filepath:
173
217
174
218
============== ===============
@@ -239,6 +283,88 @@ Server Parameters
239
283
Edge Scorer Parameters
240
284
**********************
241
285
286
+
CostmapScorer
287
+
-------------
288
+
289
+
This edge scoring plugin will score based on the cost of the costmap over the edge.
290
+
291
+
:weight:
292
+
293
+
============== ============
294
+
Type Default
295
+
-------------- ------------
296
+
double 1.0
297
+
============== ============
298
+
299
+
Description
300
+
Relative edge scoring weighting.
301
+
302
+
:costmap_topic:
303
+
304
+
============== ==========================
305
+
Type Default
306
+
-------------- --------------------------
307
+
string global_costmap/costmap_raw
308
+
============== ==========================
309
+
310
+
Description
311
+
Costmap topic to use for scoring.
312
+
313
+
:max_cost:
314
+
315
+
============== ============
316
+
Type Default
317
+
-------------- ------------
318
+
double 253.0
319
+
============== ============
320
+
321
+
Description
322
+
Maximum cost to consider an route blocked (253.0)
323
+
324
+
:use_maximum:
325
+
326
+
============== ============
327
+
Type Default
328
+
-------------- ------------
329
+
bool true
330
+
============== ============
331
+
332
+
Description
333
+
Whether to score based on single maximum or average
334
+
335
+
:invalid_on_collision:
336
+
337
+
============== ============
338
+
Type Default
339
+
-------------- ------------
340
+
bool true
341
+
============== ============
342
+
343
+
Description
344
+
Whether to consider collision status as a terminal condition
345
+
346
+
:invalid_off_map:
347
+
348
+
============== ============
349
+
Type Default
350
+
-------------- ------------
351
+
bool true
352
+
============== ============
353
+
354
+
Description
355
+
Whether to consider route going off the map invalid
356
+
357
+
:check_resolution:
358
+
359
+
============== ============
360
+
Type Default
361
+
-------------- ------------
362
+
int 1
363
+
============== ============
364
+
365
+
Description
366
+
Resolution to check costs at (1 = costmap resolution, 2 = 2x costmap resolution, etc)
367
+
242
368
DistanceScorer
243
369
--------------
244
370
@@ -535,7 +661,7 @@ If it is blocked, it sets the edge blocked as blocked for rerouting around the b
535
661
============== ============================
536
662
537
663
Description
538
-
The costmap topic to use for collision checking. May be local or global costmap depending on the desired collision checking horizon.
664
+
The costmap topic to use for collision checking. May be local or global costmap depending on the desired collision checking horizon. If set to the same as the server's costmap topic, then it will be shared here as well without duplicate subscriptions.
0 commit comments