id
stringlengths
15
54
text
stringlengths
3
133k
title
stringclasses
1 value
automap_project/octomapserver_144.txt
* Maintainer status: maintained * Maintainer: Wolfgang Merkt <opensource AT wolfgangmerkt DOT com> * Author: Armin Hornung * License: BSD * Bug / feature tracker: [ https://github.com/OctoMap/octomap_mapping/issues ](https://github.com/OctoMap/octomap_mapping/issues) * Source: git [ https://github.com/Oc...
automap_project/90_107.txt
## Footer
automap_project/octomapserver_151.txt
Please cite our paper if you use OctoMap in your research.
automap_project/90_47.txt
Pick a username
automap_project/90_101.txt
Milestone
automap_project/multipleprojectedmap_46.txt
[ about ](/about/) | [ faq ](/faq/) | [ help ](/help/ "help") | [ privacy policy ](/privacy/) | [ terms of service ](/terms/)
automap_project/90_86.txt
**[ laelliott ](/laelliott) ** commented Jun 16, 2023
lifecycle_deactivate/lifecycle_489.txt
* Update the demos to C++17. ( [ #594 ](https://github.com/ros2/demos/issues/594) ) * [rolling] Update maintainers - 2022-11-07 ( [ #589 ](https://github.com/ros2/demos/issues/589) ) * Contributors: Audrow Nash, Chris Lalancette
lifecycle_deactivate/lifecycle_248.txt
Every child of LifecycleNodes have a set of callbacks provided. These callbacks go along with the applied state machine attached to it. These callbacks are:
lifecycle_deactivate/lifecycle_466.txt
CHANGELOG
lifecycle_deactivate/hardwarecomponentsus_22.txt
7. Remove all lines with ` status_ = ... ` or ` status::... `
lifecycle_deactivate/lifecycle_406.txt
# Run the demo
lifecycle_deactivate/lifecycle_887.txt
1. configuring: We initialize our publisher and timer 2. activate: We activate the publisher and timer in order to enable a publishing 3. deactivate: We stop the publisher and timer 4. cleanup: We destroy the publisher and timer
lifecycle_deactivate/lifecycle_1225.txt
In the case you want to get the current state of the ` lc_talker ` node, you would call:
lifecycle_deactivate/lifecycle_17.txt
#### Additional Links
lifecycle_deactivate/lifecycle_214.txt
* lifecycle_talker * lifecycle_listener * lifecycle_service_client
lifecycle_deactivate/lifecycle_398.txt
## What\'s happening
lifecycle_deactivate/lifecycle_233.txt
[lc_listener] notify callback: Transition from state unconfigured to configuring [lc_listener] notify callback: Transition from state configuring to inactive
lifecycle_deactivate/lifecycle_644.txt
The principle is implemented in this demo as the typical talker/listener demo. However, imaging a real scenario with attached hardware which may have a rather long booting phase, i.e. a laser or camera. One could image bringing up the device driver in the configuring state, start and stop only the publishing of the dev...
lifecycle_deactivate/lifecycle_846.txt
_No message files found._
lifecycle_deactivate/lifecycle_1371.txt
If we have a look at the code, there is one significant change for the lifecycle talker compared to a regular talker. Our node does not inherit from the regular ` rclcpp::node::Node ` but from ` rclcpp_lifecycle::LifecycleNode ` .
lifecycle_deactivate/lifecycle_716.txt
### Messages
lifecycle_deactivate/lifecycle_1184.txt
Alternatively, these three programs can be run together in the same terminal using the launch file:
lifecycle_deactivate/lifecycle_384.txt
#### Authors
lifecycle_deactivate/lifecycle_810.txt
The next step would be to execute a state change:
lifecycle_deactivate/lifecycle_583.txt
#### Maintainers
lifecycle_deactivate/lifecycle_174.txt
### Messages
lifecycle_deactivate/lifecycle_811.txt
$ ros2 lifecycle set /lc_talker configure Transitioning successful
lifecycle_deactivate/lifecycle_659.txt
The lifecycle listener on the same time receives a notification as it listens to every state change notification of the lifecycle talker. In fact, the listener receives two consecutive notifications. One for changing from the primary state \"unconfigured\" to \"configuring\". Because the configuring step was successful...
lifecycle_deactivate/20211WRMeetupGetting_8.txt
{ auto current_command = input_command_.readFromRT(); for (size_t i = 0; i < command_interfaces_.size(); ++i) { if (!std::isnan((*current_command)->data[i])) { command_interfaces_[i].set_value((*current_command)->data[i]); } } if (state_publisher_ && state_publisher_->trylock()) { state_publisher_->msg_.header....
lifecycle_deactivate/hardwarecomponentsus_10.txt
If ` hardware_interface::return_type::ERROR ` is returned from ` read() ` or ` write() ` methods of a hardware_interface class, ` on_error(previous_state) ` method will be called to handle any error that happened.
lifecycle_deactivate/lifecycle_613.txt
[ composition ](/p/composition/github-ros2-demos) [ demo_nodes_cpp ](/p/demo_nodes_cpp/github-ros2-demos) [ demo_nodes_cpp_native ](/p/demo_nodes_cpp_native/github-ros2-demos) [ demo_nodes_py ](/p/demo_nodes_py/github-ros2-demos) [ dummy_map_server ](/p/dummy_map_server/github-ros2-demos) [ dummy_robot_bringup ](/p/dum...
lifecycle_deactivate/lifecycle_1311.txt
[ action_tutorials_cpp ](/p/action_tutorials_cpp/github-ros2-demos) [ action_tutorials_interfaces ](/p/action_tutorials_interfaces/github- ros2-demos) [ action_tutorials_py ](/p/action_tutorials_py/github-ros2-demos) [ composition ](/p/composition/github-ros2-demos) [ demo_nodes_cpp ](/p/demo_nodes_cpp/github-ros2-demo...
lifecycle_deactivate/lifecycle_26.txt
Our implementation differentiates between ` Primary States ` and ` Transition States ` . Primary States are supposed to be steady states in which any node can do the respected task. On the other hand, Transition States are meant as temporary intermediate states attached to a transition. The result of these intermediate...
lifecycle_deactivate/lifecycle_718.txt
### Services
lifecycle_deactivate/lifecycle_1023.txt
Primary States (steady states):
lifecycle_deactivate/lifecycle_1393.txt
The next step would be to execute a state change:
lifecycle_deactivate/lifecycle_113.txt
* Update maintainers to Audrow Nash and Michael Jeronimo ( [ #543 ](https://github.com/ros2/demos/issues/543) ) * Contributors: Audrow Nash
lifecycle_deactivate/lifecycle_3.txt
1. [ Home ](/) 2. [ Packages ](/packages) 3. lifecycle
lifecycle_deactivate/lifecycle_1191.txt
At the same time the lifecycle listener receives a notification as it listens to every state change notification of the lifecycle talker. In fact, the listener receives two consecutive notifications. One for changing from the primary state \"unconfigured\" to \"configuring\", and a second notification changing the stat...
lifecycle_deactivate/lifecycle_1321.txt
#### Maintainers
lifecycle_deactivate/lifecycle_946.txt
$ ros2 service call /lc_talker/get_state lifecycle_msgs/GetState requester: making request: lifecycle_msgs.srv.GetState_Request() response: lifecycle_msgs.srv.GetState_Response(current_state=lifecycle_msgs.msg.State(id=1, label='unconfigured'))
lifecycle_deactivate/lifecycle_850.txt
_No plugins found._
lifecycle_deactivate/lifecycle_204.txt
Primary States (steady states):
lifecycle_deactivate/lifecycle_1289.txt
### Wiki Tutorials
lifecycle_deactivate/lifecycle_86.txt
It returns a list of all possible transitions this node can execute.
lifecycle_deactivate/lifecycle_309.txt
## 0.13.0 (2021-03-25)
lifecycle_deactivate/lifecycle_671.txt
# The demo code
lifecycle_deactivate/lifecycle_1031.txt
## What\'s happening
lifecycle_deactivate/lifecycle_703.txt
## 0.5.1 (2018-06-28)
lifecycle_deactivate/lifecycle_942.txt
$ ros2 lifecycle list lc_talker - configure [1] Start: unconfigured Goal: configuring - shutdown [5] Start: unconfigured Goal: shuttingdown
lifecycle_deactivate/lifecycle_554.txt
### Package Dependencies
lifecycle_deactivate/lifecycle_1180.txt
In order to run this demo, we open three terminals and source our ROS 2 environment variables either from the binary distributions or the workspace we compiled from source.
lifecycle_deactivate/lifecycle_952.txt
The above description points to the current state of the development as for beta1. The future todo list for this topic comprises:
lifecycle_deactivate/lifecycle_759.txt
The principle is implemented in this demo as the typical talker/listener demo. However, imaging a real scenario with attached hardware which may have a rather long booting phase, i.e. a laser or camera. One could image bringing up the device driver in the configuring state, start and stop only the publishing of the dev...
lifecycle_deactivate/lifecycle_1314.txt
* Overview * 0 Assets * 7 Dependencies * 0 Tutorials * 0 Q & A
lifecycle_deactivate/lifecycle_1174.txt
The ` lifecycle_talker ` represents a managed node and publishes according to which state the node is in. We split the tasks of the talker node into separate pieces and execute them as follows:
lifecycle_deactivate/lifecycle_362.txt
### Services
lifecycle_deactivate/lifecycle_1300.txt
_No message files found._
lifecycle_deactivate/ros2fromthegroundupp_41.txt
RCLCPP_INFO(get_logger(), "CameraNode configured."); return rclcpp_lifecycle::node_interfaces::LifecycleNodeInterface::CallbackReturn::SUCCESS; } /* During the activate lifecycle transition, the on_activate function is called, * which activates the publis...
lifecycle_deactivate/lifecycle_680.txt
At the same time, every lifecycle node has by default 5 different communication interfaces.
lifecycle_deactivate/hardwarecomponentsus_15.txt
2. If using BaseInterface as base class then you should remove it. Specifically, change:
lifecycle_deactivate/lifecycle_2.txt
[ ](https://lunrjs.com/guides/searching.html "Help to Search")
lifecycle_deactivate/lifecycle_329.txt
## 0.8.0 (2019-09-26)
lifecycle_deactivate/lifecycle_510.txt
## 0.12.1 (2021-03-18)
lifecycle_deactivate/lifecycle_153.txt
## 0.7.1 (2019-04-26)
lifecycle_deactivate/lifecycle_1138.txt
_No plugins found._
lifecycle_deactivate/lifecycle_1397.txt
In this case we see that currently, the available transitions are ` configure ` and ` shutdown ` . The complete state machine can be viewed with the following command, which can be helpful for debugging or visualization purposes:
lifecycle_deactivate/lifecycle_296.txt
* Use default on_activate()/on_deactivate() implemenetation of Node ( [ #552 ](https://github.com/ros2/demos/issues/552) ) * Contributors: Ivan Santiago Paunovic
lifecycle_deactivate/lifecycle_1152.txt
Package containing demos for lifecycle implementation
lifecycle_deactivate/lifecycle_460.txt
All of the above commands are nothing more than calling the lifecycle node\'s services. With that being said, we can also call these services directly with the ros2 command line interface:
lifecycle_deactivate/lifecycle_497.txt
## 0.19.0 (2022-01-14)
lifecycle_deactivate/lifecycle_1320.txt
_No additional links._
lifecycle_deactivate/lifecycle_104.txt
# Changelog for package lifecycle
lifecycle_deactivate/lifecycle_1009.txt
#### Package Summary
lifecycle_deactivate/lifecycle_1202.txt
For the rest of the demo, you will see similar output as we deactivate and activate the lifecycle talker and finally shut it down.
lifecycle_deactivate/lifecycle_1292.txt
_Not currently indexed._
lifecycle_deactivate/lifecycle_541.txt
* Updated for NodeOptions Node constructor. ( [ #308 ](https://github.com/ros2/demos/issues/308) ) * Contributors: Michael Carroll
lifecycle_deactivate/lifecycle_424.txt
The lifecycle listener receives the same set of notifications as before. Lifecycle talker changed its state from inactive to active.
lifecycle_deactivate/lifecycle_407.txt
In order to run this demo, we open three terminals and source our ROS 2 environment variables either from the binary distributions or the workspace we compiled from source.
lifecycle_deactivate/lifecycle_637.txt
For a more verbose explanation on the applied state machine, we refer to the design page which provides an in-detail explanation about each state and transition.
lifecycle_deactivate/lifecycle_444.txt
* Service ` <node_name>__change_state ` : triggers a transition for the current node.
lifecycle_deactivate/lifecycle_1063.txt
# The demo code
lifecycle_deactivate/lifecycle_1112.txt
## 0.7.1 (2019-04-26)
lifecycle_deactivate/lifecycle_1221.txt
* Service ` <node_name>__get_available_transitions ` : Same as above, meant to an introspection tool.
lifecycle_deactivate/lifecycle_1156.txt
* Mabel Zhang * Michael Jeronimo
lifecycle_deactivate/lifecycle_959.txt
* Remove unnecessary dependency on ros2run ( [ #413 ](https://github.com/ros2/demos/issues/413) ) * Contributors: Michel Hidalgo
lifecycle_deactivate/lifecycle_354.txt
### Package Dependencies
lifecycle_deactivate/lifecycle_182.txt
Failed to get question list, you can ticket an issue [ here ](https://github.com/ros-infrastructure/rosindex/issues/new)
lifecycle_deactivate/lifecycle_509.txt
## 0.13.0 (2021-03-25)
lifecycle_deactivate/lifecycle_739.txt
* Karsten Knese
lifecycle_deactivate/lifecycle_1093.txt
All of the above commands are nothing else than calling the lifecycle node\'s services. With that being said, we can also call these services directly with the ros2 command line interface:
lifecycle_deactivate/lifecycle_14.txt
**Tags** | _No category tags._ ---|--- **Version** | 0.20.3 **License** | Apache License 2.0 **Build type** | AMENT_CMAKE **Use** | RECOMMENDED ### Repository Summary
lifecycle_deactivate/lifecycle_1054.txt
[lc_client] Transition 2 successfully triggered. [lc_client] Node lc_talker has current state active.
lifecycle_deactivate/lifecycle_616.txt
* Overview * 0 Assets * 7 Dependencies * 0 Tutorials * 0 Q & A
lifecycle_deactivate/lifecycle_582.txt
_No additional links._
lifecycle_deactivate/lifecycle_442.txt
* Service ` <node_name>__get_state ` : query about the current state of the node.
lifecycle_deactivate/lifecycle_289.txt
* Update the demos to C++17. ( [ #594 ](https://github.com/ros2/demos/issues/594) ) * [rolling] Update maintainers - 2022-11-07 ( [ #589 ](https://github.com/ros2/demos/issues/589) ) * Contributors: Audrow Nash, Chris Lalancette
lifecycle_deactivate/lifecycle_917.txt
If we have a look at the code, there is one significant change for the lifecycle talker compared to a regular talker. Our node does not inherit from the regular ` rclcpp::node::Node ` but from ` rclcpp_lifecycle::LifecycleNode ` .
lifecycle_deactivate/20211WRMeetupGetting_3.txt
Have fun! Use-cases from wilderness - ros2_control + MoveIt2 Use-cases from wilderness ● UR driver: https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver ○ The first open-source driver with ros2_control integration ○ Needs special features: ■ Digital and analog inputs and outputs ■ General robot operation: un...