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
The action reconfiguration at edges was a late addition to our navigation pipeline and it was a bit messy, mainly because its a separate service configured by a different file which adds a lot of complexity to the system, additional points of problems and unnecessary delays.
The way to overcome this, is to fully integrate the edge re-configuring into the navigation server (#33 ). The new map format (#35 ) already provides for this in the edge definition where the config field can be used to define parameters that can be reconfigured using the rqt_reconfigure interface.
edges: # List of edges departing from the node
- action: move_action # Action Namenode: WayPoint002config: &move_action_config_1 # Action Configurationinflation_radius: 0.0# Action Parameterstop_vel: 0.55recovery_behaviours_config: ''action_type: 'move_action_msgs/MoveActionGoal'# Goal type for the Actiongoal:
target_pose: $node.pose
The text was updated successfully, but these errors were encountered:
Edge reconfigure for the new map is now implemented in the main navigation script (navigation.py) but not as yet for the execute policy server, which is due to be integrated with navigation.py. Issue #33 needs to be resolved before this issue can be fully resolved.
The action reconfiguration at edges was a late addition to our navigation pipeline and it was a bit messy, mainly because its a separate service configured by a different file which adds a lot of complexity to the system, additional points of problems and unnecessary delays.
The way to overcome this, is to fully integrate the edge re-configuring into the navigation server (#33 ). The new map format (#35 ) already provides for this in the edge definition where the
config
field can be used to define parameters that can be reconfigured using therqt_reconfigure
interface.The text was updated successfully, but these errors were encountered: