2-APL UPC project.
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

fixed some stuffs

cyberslas fdd34127 9030bf3e

+1 -1
+1 -1
docs/2apl-doc.tex
··· 598 598 599 599 The transition for external actions broadcast an event to the multi-agent system level and waits for the return value from the environment in one transition step. 600 600 601 - $$ {t \neq \bot \& \gamma \vDash_{g} G(r)} \over {\langle \iota, \sigma, \gamma, \{(@env(\alpha(t_{1}, \ldots, t_{n}), V), r, id)\},\theta, \xi \rangle \underrightarrow{env(\alpha(t_{1}\theta, \ldots, t_{n}\theta), t)} \langle \iota, \sigma, \gamma, \{\}, \theta \cup \{ V \diagup t\}, \xi \rangle } $$ 601 + $$ {t \neq \bot \& \gamma \vDash_{g} G(r)} \over {\langle \iota, \sigma, \gamma, \{(@env(\alpha(t_{1}, \ldots, t_{n}), V), r, id)\},\theta, \xi \rangle \xrightarrow{env(\alpha(t_{1}\theta, \ldots, t_{n}\theta), t)} \langle \iota, \sigma, \gamma, \{\}, \theta \cup \{ V/t\}, \xi \rangle } $$ 602 602 603 603 If the return value is a failure exception, then the execution of the external action is considered as failed. As a consequence, the action is not removed from the plan base and its identifier is added to the agent's event base. 604 604