rayvburn / humap_local_planner

Human-aware robot trajectory planner using a hybrid trajectory candidates generation and spatiotemporal cost functions
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

get rid of the `ContextualizedCostFunction` #98

Closed rayvburn closed 1 year ago

rayvburn commented 1 year ago

the classical ObstacleCostFunction does the same plus checks if footprint is in a legal position (collision-free)

rayvburn commented 1 year ago

Examined if ObstacleCostFunction operates using the resultant costmap that has all layers embedded and it is true.

What was compared:

A new channel was added to the PCL created with createCostGridPcl method - obs_cost. With a circular footprint created with 1e-06 radius, the obs_cost channel duplicates occ_cost. By this means, the ObstacleCostFunction cost function uses the resultant costmap (with obstacles and social contexts, if enabled), so there is no need to use ContextualizedCostFunction