All Classes and Interfaces
Class
Description
This abstract class describes the functionality an agent mind interface should provide.
The BlackBoard is a storage container for competencies to share information
with each other.
parent class for all cmion components
A class that all events within cmion should inherit from to distinguish them
easily from other ION events
a storage container is used for storing data that is shared between the components.
competencies are represented by objects of subclasses of this class
an exception that competencies should throw when they want to
cancel execution
abstract base class for all events relating to the execution of a single competency
(e.g.
this component is responsible for executing plans of competencies it has received
(normally from the competency manager)
a plan of competencies that can be executed by the competency execution system,
this class is used to represent both instantiated and not instantiated execution plans.
abstract base class for all events relating to the execution of a competency plan
(e.g.
represents a step in a competency execution plan, can be instantiated or uninstantiated,
see comments in class CompetencyExecutionPlan for more on this distinction.
the competency library is the component that registers all components
the competency manager receives actions from the mind for execution and decomposes
them into a plan of competencies for execution
a competency manager rule maps a mind action and the state of available competencies
to a CompetencyExecutionPlan
this event signifies that cmion is ready for executing actions, it is mainly used as a
signal to the mind that it can start executing actions
this event signifies that the execution of a competency was cancelled
this type of event is raised by the competency execution system when a competency execution plan has been cancelled
the competency manager listens for those events
this type of event is raised by the competency execution system when a competency execution plan has failed
the competency manager listens for those events
this type of event is raised by the competency execution system when a competency execution plan is
starting to be carried out
this type of event is raised by the competency execution system when a competency execution plan has been carried out successfully
the competency manager listens for those events
this event signifies that the execution of a competency has failed
this event signifies that the execution of a competency has started
this event signifies that the execution of a competency has suceeded
this type of event is raised by the competency manager when a mind action was cancelled
the agent mind connector listens for those events and sends them to the agent mind
this type of event is raised by the competency manager when a mind action has failed
the agent mind connector listens for those events and sends them to the agent mind
this type of event is raised by the competency manager when a mind action has succeeded
the agent mind connector listens for those events and sends them to the agent mind
This event is raised whenever a property value has been set through a
RequestSetProperty.
This event is raised by a container whenever a property is removed from this
container.
this type of event can be raised by any competency.
this type of event can be raised by any sensing competency.
This event is raised by the SamgarConnector in the add ons package, when it
is ready (e.g.
an event informing that a new subcontainer has been added to a CMION StorageContainer
This will be raised by the owner container
an event informing that a new sub container has been removed from a CMION StorageContainer
This will be raised by the owner container
Note that this will only be raised if removal has been requested for the container itself,
if this container was removed because its parent, grandparent, etc, was removed, the event
will not be raised
example of the implementation of a competency, with comments explaining how
to define competencies, this is not actually doing anything serious
example of the implementation of a TCP remote competency, with comments
explaining how to define competencies, this is not actually doing anything serious
In this thread we communicate with the FAtiMA mind through a remote connection
in this class we pretend to be a fatima for the purpose of retaining the fatima
state in a migration scenario.
a collection of utility methods for handling the communication via the FAtiMA
protocol
specifies an interface for an architecture class that constructs the cmion components and
stores references to them
This event signals that the invite listener has received an invite.
a thread for listening on the invite listen port for invitations
an event that can be raised to signal that we would like an agent to migrate into this
(empty) embodiment.
the base class for mind actions, different minds (e.g.
an abstract class describing a competency, whose main execution is performed remotely,
in a different executable (possibly on a different machine) and that we communicate
with over the network.
A class encapsulating tcp communication with another process on the network.
a request that can be made to any CMION Storage Container for adding a new
sub container
this type of event is raised by the competency manager when it wants to cancel a
currently executing competency execution plan
the competency execution system listens for those events to stop the execution of the associated plan
this type of event is raised by the agent mind connector when the mind decides
to cancel a currently executing mind action
the competency manager listens for those events to stop the execution
this type of event is raised by the competency manager when it selects a new competency execution plan
the competency execution system listens for those events to carry out their execution
this type of event is raised by the agent mind connector when the mind sends a new action for execution
the competency manager listens for those events to plan their execution
Request a container to remove property of the given name.
a request that can be made to any CMION Storage Container for removing an
existing sub container (does not remove sub sub containers)
Request to set the given property to the given value.
this request can be scheduled with competencies to request it to run
stores information about a Samgar competency that is necessary to build the competency
dynamically and to chose it (e.g.
an example mind for demonstrating and testing migration by invite
The connector to a SuperSimpleMind (example implementation of a simple mind interface)
an example mind for migration demonstration puposes
The connector to a SuperSimpleMind (example implementation of a simple mind interface)
an example mind that does almost nothing except executing random actions,
this is just to show how one could interface a different mind then FAtiMA,
e.g.
The connector to a SuperSimpleMind (example implementation of a simple mind interface)
one of several test competencies to test the execution system
one of several test competencies to test the execution system
one of several test competencies to test the execution system
one of several test competencies to test the execution system
this is an example of a competency that is not started as part of an order
issued from the mind, but that continuously runs in the background, in this
case printing out a message every 5 seconds.
one of several test competencies to test the execution system
one of several test competencies to test the execution system
a specific subclass of cmion storage container with convenience methods added
for handling "agent" and "object" sub containers.
This input stream works in conjunction with the WrappedOutputStream
to introduce a protocol for reading arbitrary length data in a
uniform way.
This output stream works in conjunction with the WrappedInputStream
to introduce a protocol for sending arbitrary length data in a
uniform way.