The core
library provides support for backends. The core
library provides the classes required for interacting with backends and performing application tasks.
The table below contains descriptions of the library components.
The core library components
Component |
Description |
---|---|
Base class for specific backend implementations. |
|
Structure defining a set of base data. |
|
Class implementing a generator of unique IDs. |
|
Base class of devices. |
|
Class implementing an interface for the message bus. |
|
Class implementing an interface for the message bus endpoint. |
|
Template class that implements the container of neurons of the same model. |
|
Template class that implements the container of synapses of the same type. |
|
Class implementing the message subscription. |
|
Class implementing an interface for the tag dictionary. |
|
Class defining unique identifiers. |
|
Function implementing hashing of UIDs. |
|
Namespace that contains message interfaces. |
|
A namespace that contains the names and value types of known tags. |
The figure below shows how the library components interact.
In the Kaspersky Neuromorphic Platform, the BaseData
structure contains basic information about an object and includes UID
and TagMap
. The BaseData
structure is used in the following classes: Projection
, Population
, and Backend
. Therefore, each of them has a UID
and a set of tags with the TagMap
values.
The Population
and Projection
classes receive and send messages that are implemented in the classes of the messaging
namespace. Messages contain the sender's UID in the header.
The Backend
class contains the Device
and MessageBus
classes. The MessageBus
creates MessageEndpoint
and interacts with them by exchanging messages. Each MessageEndpoint
has a container of the Subscription
class.
Diagram of interactions between components in the core library