Previous: Other Actions, Up: Built-Ins [Contents][Index]
The following actions are available when the system is running in TeleoR mode (after the command teleor
has been executed in the interpreter).
An interpreter command that can be used in teleor mode when an agent has been started using
start_agent
.Actions
is a list of actions that agent wants the robotic interface to perform. The given actions must have been declared as discrete or durative.
act actions(list(discrete || durative))
Kill the current agent started using
start_agent
.
act kill_agent()
Kill the task with name
Task
started usingstart_task
.
act kill_task(atom)
start_agent(Handle, Convention)
Start a new agent.
Handle
is the message address of the robot interface or simulation with which the agent will interact.Convention
is the percepts update convention being used. This is one of:all
if the robot sends all the percepts each time it sends percepts orupdates
if the robot only sends changes to percepts.Percepts can be post-pocessed using one of the user defined actions
post_percepts_all_
orpost_percepts_updates_
. See below.
act start_agent(handle, atom)
Start a new task (as a thread) whose name is
Name
.TRCall
is the TeleoR call to be executed in the thread.
act start_task(atom, trcall)
This is a user defined action that is executed when processing percepts after the system defined percepts process when using the
all
convension. Both the system defined handler and the user handler are processed atomically.
post_percepts_all_(list(dyncall))
post_percepts_updates_(Percepts)
This is a user defined action that is executed when processing percepts after the system defined percepts process when using the
updates
convension. Both the system defined handler and the user handler are processed atomically.
post_percepts_updates_(list(percept_update_))
Previous: Other Actions, Up: Built-Ins [Contents][Index]