You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Question about internal loop vs. counter management for Repeater node #938
Why do you use an internal loop instead of using a counter forcing the Repeater node to be ticked "num_cycles_" times ?
My naive implementation would be:
Status status = m_child->tick();
if (status == Status::RUNNING)
{
return Status::RUNNING;
}
else if (status == Status::FAILURE)
{
return Status::FAILURE;
}
if ((m_num_cycles > 0) && (++m_counter == m_num_cycles))
{
m_counter = m_num_cycles;
return Status::SUCCESS;
}
return Status::RUNNING;
I guess with your method, you do not have the timestamp of the tree between each iteration ? I think the last method is more in the spirit of BT: blocking less each node and each iteration scheduled by a fixed time stamp ?
Activity
facontidavide commentedon Feb 4, 2026
yes, that should be changed probably