task_behavior_engine icon indicating copy to clipboard operation
task_behavior_engine copied to clipboard

Something seems to be unreasonable with example3

Open haik opened this issue 5 years ago • 1 comments

The output of example3 is:

ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_3
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_3
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_3
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
ACTIVE Executing finish_counts:count_2
ACTIVE Executing finish_counts:count_1
SUCCESS All children succeeded in finish_counts

Before moving on to count2, it will re-start count1. But why should it? I don’t really understand it. I was wondering if anyone can help me?

haik avatar Feb 08 '20 11:02 haik

Since sequencer always run the first node at each tick

icech avatar Jul 04 '20 10:07 icech