Skip to content
Snippets Groups Projects
  1. Jun 13, 2019
    • Michael Jeronimo's avatar
      Call now on the main lifecycle nodes instead of rclcpp_nodes (#845) · 6be3a082
      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.
      6be3a082
    • Michael Jeronimo's avatar
      Delete pause/resume buttons and services (#838) · baddfdd8
      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.
      baddfdd8
    • bpwilcox's avatar
      d42cbd1b
    • Michael Jeronimo's avatar
      Run lint tools on lifecycle_manager and nav2_tasks (#839) · 8b4d4d93
      Michael Jeronimo authored
      Also checked bt_navigator and nav2_robot, which are clean.
      8b4d4d93
    • Michael Jeronimo's avatar
      Remove the nav2_mission_executor directory (#837) · 28f6dedc
      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.
      28f6dedc
    • Michael Jeronimo's avatar
  2. Jun 11, 2019