Add execution policies to the example deluxe-interface Ref T136
Decimate sensors and make low-level agents await for sensory values, but leave high-level agent execute on each triggering by its default execution policy.
Description
Description
Details
Details
- Auditors
goetzinger - Provenance
Dávid Juhász Authored on Apr 19 2019, 12:52 PM • juhasz Pushed on Apr 19 2019, 12:52 PM - Parents
- R20:4f138adb30fa: Write API documentation for execution policies Ref T136
- Branches
- Unknown
- Tags
- Tasks
- Restricted Maniphest Task
Event Timeline
Comment Actions
@goetzinger , please have a look in how the deluxe interface can be used for setting execution policies.
Comment Actions
Seems fine for me. But I have two questions:
- Can I also set the agent to decimation(X) instead of awaitAll?
- What does the "0" mean in awaitAll?
Comment Actions
Of course! You can use decimation, awaitAll, or awaitAny for any agent.
- What does the "0" mean in awaitAll?
It is actually {0}, which is here a set that contains one element: 0. For awaitAll and awaitAny, you need to define which slaves you want the agent to wait for; slave positions indexed from 0. So here it means that the agent waits for its slave at position 0 to send a new message.