See: Description
| Class | Description |
|---|---|
| JavaBehaviour<AGENT> |
Base class for definitions of senses and acts of SPOSH bot.
|
| Enum | Description |
|---|---|
| PoshTreeEvent |
Enum for events that can change the POSH plan.
|
| Annotation Type | Description |
|---|---|
| SPOSHAction |
Marker that will annotate actions that should be made available for SPOSH engine
in the
behaviour class. |
| SPOSHSense |
Marker that will annotate senses that should be made available for SPOSH engine
in the
behaviour class. |
Classes and interfaces used with behavior class. Behavior class is an obsolete method of implementing primitives, i.e. actions and senses, for *POSH plans. The idea is that user will create a special behavior class, where some methods will be actions or senses.
When engine would request to call an action, the IWorkExecutor would
take the behavior class and it would try to find a method annotated
with @SPOSHAction and that method would be called.
The methods of senses would have annotation @SPOSHSense.
This way of specifying has several problems, e.g. names of actions/senses
can be same as names of java methods, so action with dash like
pick-iteam are not possible.
Even bigger problem is execution of actions, there is no cleanup code for actions, so when another action is executed after e.g. move, it has no idea if agent is actually moving or not.
Copyright © 2018 AMIS research group, Faculty of Mathematics and Physics, Charles University in Prague, Czech Republic. All rights reserved.