Skip to content

Commit c9cb9f7

Browse files
Update configuring-route-server.rst with new parameters (#680)
* Update configuring-route-server.rst Signed-off-by: Steve Macenski <stevenmacenski@gmail.com> * Update configuring-route-server.rst Signed-off-by: Steve Macenski <stevenmacenski@gmail.com> --------- Signed-off-by: Steve Macenski <stevenmacenski@gmail.com>
1 parent 967dcfa commit c9cb9f7

1 file changed

Lines changed: 127 additions & 1 deletion

File tree

configuration/packages/configuring-route-server.rst

Lines changed: 127 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,17 @@ Server Parameters
8181
Description
8282
The maximum planning time to use.
8383

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+
8495
:tracker_update_rate:
8596

8697
============== ========
@@ -169,6 +180,39 @@ Server Parameters
169180
Description
170181
Whether pruning the goal node from the route due to it being spatially past the goal pose requested (pose requests only ``use_poses``).
171182

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+
172216
:graph_filepath:
173217

174218
============== ===============
@@ -239,6 +283,88 @@ Server Parameters
239283
Edge Scorer Parameters
240284
**********************
241285

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+
242368
DistanceScorer
243369
--------------
244370

@@ -535,7 +661,7 @@ If it is blocked, it sets the edge blocked as blocked for rerouting around the b
535661
============== ============================
536662

537663
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.
539665

540666
:rate:
541667

0 commit comments

Comments
 (0)