- Jun 20, 2019
-
-
Mohammad Haghighipanah authored
-
Carl Delsey authored
-
bpwilcox authored
fix linters and uncrustify white line use unordered map for transitions
-
- Jun 19, 2019
-
-
Dan Rose authored
-
Mohammad Haghighipanah authored
* added recovery node
-
Matthew Hansen authored
-
- Jun 18, 2019
-
-
Michael Jeronimo authored
-
Dan Rose authored
uncrustify
-
Dan Rose authored
Use get_name() so that if parent name is renamed, the child name will use that as its prefix (thanks, Scott!)
-
Dan Rose authored
This way, if __node:= is passed to the node executable, it gets overridden on each subnode and these subnodes get unique names.
-
- Jun 14, 2019
- Jun 13, 2019
-
-
Michael Jeronimo authored
-
Michael Jeronimo authored
Now that lifecycle nodes properly support use_sim_time, we can get the current time from the node itself rather than relying on the rclcpp_node, which is a temporary bridging solution to interface to ROS2 functionality that doesn't yet support lifecycle nodes. This PR is one of several steps that we'll take in order to remove the rclcpp_nodes from the navigation code, thereby reducing the overall number of nodes in the system and therefore the overall number of topics and services.
-
Michael Jeronimo authored
We don't yet have a full solution for bringing nodes into a state where their parameters can be reconfigured and then the nodes reactivated. So, we don't want to expose a partial solution for the Dashing release that could potentiall be confusing for users. Currently, all lifecycle node parameters are read during on_configure. Going forward, we will re-assess all parameters to allow for other options, such as on_activate. Once parameters are associated with different state transitions, we'll then have to clearly document the parameters and their state associations and/or come up with an automated way to allow for node reconfiguration.
-
bpwilcox authored
-
Michael Jeronimo authored
Also checked bt_navigator and nav2_robot, which are clean.
-
Michael Jeronimo authored
This functionality will be removed from the nav2 repository and eventually revived in a separate repository. The plan is to separate out the generic Behavior Tree functionality first into a separate repo and then we can build a mission execution system using this generic BT functionality, also in a separate repo. Then, we will be able to span navigation, grasping, and other kinds of tasks, all coordinated using BTs.
-
Michael Jeronimo authored
-
- Jun 11, 2019
-
-
Mohammad Haghighipanah authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Matthew Hansen authored
-
Carlos A. Orduno authored
after halting a bt action node
-
Michael Jeronimo authored
-
Michael Jeronimo authored
* Add an all-in-one launch file for nav2 developers * Add an option to specify the rviz config file * Fix some errors found by Carl in review
-
Michael Jeronimo authored
-
Carlos A. Orduno authored
-