py_trees icon indicating copy to clipboard operation
py_trees copied to clipboard

Python implementation of behaviour trees.

Results 57 py_trees issues
Sort by recently updated
recently updated
newest added

In 2.1.5 it's good to see sequence without memory, but the semantics seem to be wrong. From [1], I would expect the tree: ``` root = py_trees.composites.Sequence(memory=False) root.add_child(py_trees.behaviours.TickCounter(1)) root.add_child(py_trees.behaviours.Success('Reached second...

I am doing **setup()** method (from _py_trees.trees.BehaviourTree()_) in non-main thread and I am getting following error: `ValueError: signal only works in main thread`. How to deal with this without transferring...

flag:question
component:trees

Hi, we're trying to use this library to control a dual arm manipulator to perform an assembly task. Sometimes we'll get errors in the middle of the task due to...

flag:question
component:trees

I think ComparisonExpression could benefit from generics to improve type specificity. What happens now is that because operator is declared to take two `Any`s, mypy returns: ` error: Returning Any...

The display module has a few problems. **Must-solve** * The updated status of each and every ticked behaviour must be reflected for visualisation purposes and not lost. This currently occurs...

component:composites
component:behaviours
component:display
type:design

There are two cases for marking the status of a behaviour as INVALID: 1. A higher priority interrupt 2. A decorator or a parallel also sets INVALID on a running...

flag:question
component:composites
component:decorators

Feature request from someone at TRI: * `On Entry` behaviour/subtree * `Body` behaviour/subtree * `On Body Failure` behaviour/subtree * `On Body Success` behaviour/subtree The assembly should faithfully reproduce a typical...

type:feature
component:idioms

Selectors w/ memory and Sequences w/o memory slipped in via #324, #325 with defaults that didn't break api, but weren't really consistent inasmuch as the former has a deafult of...

type:enhancement
component:composites

Some small issues were uncovered around tip/decorators in `1.x` / `2.x`. See #175 and #181. The test suite of interest is in `test_tip.py` of those release branches. This currently highlights...

type:bug
component:composites
component:decorators

**History** Parallels came in post selectors & sequences and as a result, api had already formed around `current_child` and `tip()` for composites and subsequent tooling (visualisation) which worked on the...

component:composites
type:design