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
At the moment the fleet adapters are using a somewhat roundabout strategy to inform the fleet adapter about where and how robots can perform cleaning tasks. It would be nice if we could incorporate that information directly into the nav graph yaml file, drawn and exported using the traffic editor.
I imagine we'd want to add these features:
Create a new type of nav graph entries parallel to lanes and vertices, maybe call it paths
Give each paths element a sequence of vertices that don't (necessarily) exist on the nav graph
Give the paths elements attributes/tags, similar to what we do for vertices
At the moment the fleet adapters are using a somewhat roundabout strategy to inform the fleet adapter about where and how robots can perform cleaning tasks. It would be nice if we could incorporate that information directly into the nav graph yaml file, drawn and exported using the traffic editor.
I imagine we'd want to add these features:
lanes
andvertices
, maybe call itpaths
paths
element a sequence of vertices that don't (necessarily) exist on the nav graphpaths
elements attributes/tags, similar to what we do for verticesMaybe this could be a format to consider:
The text was updated successfully, but these errors were encountered: