Davide Faconti comments

Results 437 comments of


                                            Davide Faconti

Plugin tutorial (and passing ros2 node to tree nodes)

There is now a specific tutorial about plugins. For ROS2 specific code, see here: https://github.com/BehaviorTree/BehaviorTree.ROS2/tree/humble/btcpp_ros2_samples

confused about halt() method

> So how to trigger this function? I'm confused. Using `ReactiveSequence` or `Parallel` or any other node that implement concurrent behaviors. At the level of C++, halt() is **not** something...

confused about halt() method

@ekouters >This general rule / guideline for implementing custom nodes is missing in any of the documentation or code comments I have gone through. Isn't this what I explain in...

confused about halt() method

> was uncertain about when a ControlNode should halt() its children. Each **ControlNode** will have its own logic. ### **halt()** means "If you are in a RUNNING state, you must...

can ros subscriber callback work under behavior tree?

Please, see here: https://github.com/BehaviorTree/BehaviorTree.ROS2/

"Any::cast failed because it is empty" better handling or logging

Directly accessing the blackboard to initialize variables of the node is discouraged. There is a specific tutorial that offer a better alternative: https://www.behaviortree.dev/docs/tutorial-basics/tutorial_08_additional_args This is the intended behavior, since I...

Need Complete Documentation for all BT Nodes with Examples

The best option is to read the comments in the header files, most of the time. Any specific list of nodes I should prioritize, in your opinion?

Floating point truncated exception when loading bag with messages with INT64 fields with values bigger than std::numerical_limits<double>::max

PlotJuggler can only manage numbers that can be represented as double. What would be the desired behavior in this case? Truncation? There is no other solution

Floating point truncated exception when loading bag with messages with INT64 fields with values bigger than std::numerical_limits<double>::max

that will take me considerable more time than simply remove the exception. I will do it once I have time. Feel free of course to create a PR to fix...