Skip to content
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.

Addition of how the toTick variable is reset and clarification of toTickFromLastIteration function #3

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Addition of how the toTick variable is reset and clarification of toTickFromLastIteration function #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
235f09d
resetting the toTick variable in the control nodes with memory
ct2034 Mar 12, 2024
69fd930
explanation of toTickFromLastIteration function
ct2034 Mar 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions rep-2018.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,11 +211,17 @@ as shown below.

::

In the following pseudocode and the one for *Fallback with Memory*, the
function *toTickFromLastIteration* returns the value of the variable toTick
from the last iteration of this control flow node. If it is the first
iteration, it returns 1.

toTick ← toTickFromLastIteration();
for j ← toTick to n do
response ← child(j).tick()
if response != Success then
return response
toTick ← 1
return Success

The *Fallback with Memory* node executes, which corresponds to routing
Expand Down Expand Up @@ -243,6 +249,7 @@ below.
response ← child(j).tick()
if response != Failure then
return response
toTick ← 1
return Failure

The *(Reactive) Parallel* node with success threshold :math:`k`
Expand Down