You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-197Lines changed: 2 additions & 197 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,12 @@ You can use Kaspersky Neuromorphic Platform to do the following:
12
12
13
13
- Create spiking neural networks (SNNs) and train these on various types of input data, such as telemetry, events, images, 3D data, audio, and tactile data.
14
14
- Convert artificial neural networks (ANNs) into spiking networks and train these.
15
-
- Optimize the structure of the loaded neural networks.
16
15
- Conduct applied research in the field of input data classification and other application domains of neural networks.
17
16
- Develop new neural network topologies, for example, impulse analogs of convolutional neural networks that involve convolution in space and time.
18
17
- Develop new models of synaptic plasticity.
19
18
- Implement new neuron models.
20
19
- Implement application solutions based on neuromorphic spiking neural networks in the field of robotic manipulators, Internet of Things, unmanned systems, human-machine interaction, wearable devices, and optimization planning.
21
-
- Implement application solutions on devices with low power consumption or using neuromorphic processors.
20
+
- Implement application solutions on devices with low power consumption using neuromorphic processors.
22
21
23
22
You can use the C++ and Python languages to accomplish these tasks. The platform supports CPUs as well as the AltAI-1 neuromorphic processor unit designed for energy-efficient execution of neural networks in various types of intelligent devices.
24
23
@@ -93,199 +92,6 @@ To work with the platform, the following software must be installed on the devic
93
92
- python3-tqdm
94
93
- TensorFlow 2.13.1
95
94
96
-
## Installing the platform
97
-
98
-
For the development of application solutions on Linux, you can install the platform in one of the following ways:
99
-
100
-
- Install deb packages.
101
-
- Install packages for the development of application solutions in Python.
102
-
103
-
When working with the platform source code on Linux or Windows, you can build the platform or an application solution using C++. The platform build can be used to develop the Kaspersky Neuromorphic Platform.
104
-
105
-
### Installing deb packages
106
-
107
-
_To install the deb packages:_
108
-
109
-
1. To install deb packages containing CPU and `AltAI SNN` backend binaries, run the following commands as root:
When installing the `knp-altai-backend_<motiv_version>_amd64.deb` package, accept the AltAI-1 backends and `ANN2SNN` package Terms of Use. Your acceptance of the Terms of Use is a prerequisite for installing the package. The package installation process will be interrupted unless you accept the Terms of Use.
118
-
119
-
1. To install the deb package with C ++ framework binary code, run the following command as root:
When installing the `knp-altai-backend-dev_<motiv_version>_amd64.deb` package, accept the AltAI-1 backends and `ANN2SNN` package Terms of Use. Your acceptance of the Terms of Use is a prerequisite for installing the package. The package installation process will be interrupted unless you accept the Terms of Use.
135
-
136
-
1. To install the deb package with a Python framework for an `AltAI SNN` backend, run the following as root:
1. To install the deb packages with `ANN2SNN` package and `AltAI ANN2SNN` backend binary code, run the following commands as root:
143
-
144
-
```
145
-
dpkg -i <path-to-deb-package>/knp_ann2snn.deb
146
-
```
147
-
148
-
When installing the `knp_ann2snn.deb` package, accept the AltAI-1 backends and `ANN2SNN` package Terms of Use. Your acceptance of the Terms of Use is a prerequisite for installing the package. The package installation process will be interrupted unless you accept the Terms of Use.
149
-
150
-
1. To install the deb package with platform usage examples, run the following command as root:
-`<path-to-deb-package>` is the path to the deb package;
165
-
-`<knp_version>` is the Kaspersky Neuromorphic Platform version.
166
-
-`<motiv_version>` is the version of the backends for the AltAI-1 neuromorphic processor and the `ANN2SNN` package.
167
-
168
-
### Installing Python development packages
169
-
170
-
The following DEB or WHL packages must be installed for Python development:
171
-
172
-
- deb packages:
173
-
-`knp-python3-framework_<knp_version>_amd64.deb`: a deb package containing a Python framework for an `AltAI SNN` backend.
174
-
-`knp_ann2snn.deb`: a deb package with the `ANN2SNN` package, `AltAI ANN2SNN` backend binary code for the AltAI-1 neuromorphic processor, and a component for placing the neural network on AltAI-1.
175
-
- whl packages for installing from PyPI:
176
-
-`knp-<knp_version>-py3-none-any.whl`: a whl package containing a Python framework for an `AltAI SNN` backend.
177
-
178
-
-`knp_ann2snn_x86_64_<motiv_version>-py3-none-any.whl`: a whl package with the `ANN2SNN` package, `AltAI ANN2SNN` backend binary code for the AltAI-1 neuromorphic processor, and a component for placing the neural network on AltAI-1.
179
-
180
-
This package is installed on x86-based computers.
181
-
182
-
-`knp_ann2snn_aarch64-<motiv_version>-py3-none-any.whl`: a whl package with the `ANN2SNN` package and the `AltAI ANN2SNN` backend binary code for the AltAI-1 neuromorphic processor.
183
-
184
-
This package is installed on ARM-based computers.
185
-
186
-
where:
187
-
188
-
-`<knp_version>` is the version of Kaspersky Neuromorphic Platform.
189
-
-`<motiv_version>` is the version of the backends for the AltAI-1 neuromorphic processor and the `ANN2SNN` package.
190
-
191
-
_To install deb packages for Python development:_
192
-
193
-
1. To install the deb package with a Python framework for an `AltAI SNN` backend, run the following as root:
1. To install the deb packages with `ANN2SNN` package and `AltAI ANN2SNN` backend binary code, run the following commands as root:
200
-
201
-
```
202
-
dpkg -i <path-to-deb-package>/knp_ann2snn.deb
203
-
```
204
-
205
-
When installing the `knp_ann2snn.deb` package, accept the AltAI-1 backends and `ANN2SNN` package Terms of Use. Your acceptance of the Terms of Use is a prerequisite for installing the package. The package installation process will be interrupted unless you accept the Terms of Use.
206
-
207
-
where:
208
-
209
-
-`<path-to-deb-package>` is the path to the deb package;
210
-
-`<knp_version>` is the Kaspersky Neuromorphic Platform version.
211
-
212
-
Use the `pip3` package manager to install whl packages from the PyPI platform.
213
-
214
-
_To install the whl packages:_
215
-
216
-
1. To install a whl package containing a Python framework for an `AltAI SNN` backend, run the following command:
- `<knp_version>` is the version of Kaspersky Neuromorphic Platform.
239
-
- `<motiv_version>` is the version of the backends for the AltAI-1 neuromorphic processor and the `ANN2SNN` package.
240
-
241
-
### Scenario for building a platform project or an application solution
242
-
243
-
You can build a platform or an application solution in C++. The platform build can be used when developing the Kaspersky Neuromorphic Platform.
244
-
245
-
When developing application solutions, you can install the required deb packages instead of building the solution.
246
-
247
-
You can also use the Docker image `knp-build-image` included in the platform distribution kit to build the platform or an application.
248
-
249
-
A platform or application solution build script consists of the following stages:
250
-
251
-
1. Obtaining the platform source code
252
-
253
-
You can get the platform source code in one of the following ways:
254
-
255
-
- Download the archive with the source code from the platform repository and unpack it to the working directory.
256
-
- Clone the platform repository.
257
-
258
-
1. Defining the Boost_ROOT setting in Windows
259
-
260
-
In Windows, define the `Boost_ROOT` setting. To do this, create an environment variable or specify the path to the installed Boost library in the `CMakePresets.json` file located in the root directory with the platform source code.\
261
-
You can define the path to the installed Boost library as a CMake invocation parameter using the following command:
262
-
263
-
```
264
-
cmake -DBOOST-ROOT=<pathtoinstalledBoostlibrary>
265
-
```
266
-
267
-
1. Configuring the build settings for the application solution
268
-
269
-
In case of an application solution build, describe the build process in the `CMakeLists.txt` file. Specify the directory with the application to be built using the `add_subdirectory` function, specify the executable file using the `add_executable` function, and specify the platform libraries to be connected to the project using the `target_link_libraries` function. You can use the following libraries:
270
-
271
-
- `neuron_traits`
272
-
- `synapse_traits`
273
-
- `core`
274
-
- `meta`
275
-
- `devices`
276
-
- `backends`
277
-
- `framework`
278
-
279
-
1. Configuring a platform or an application solution build
280
-
281
-
If you are building a platform or an application solution on Linux, configure the build using the CMake build system. For more details on configuring a build using CMake, refer to the <a href="https://cmake.org/documentation/">CMake documentation</a>.\
282
-
If you are building the platform or application solution in Windows, configure the build in Visual Studio. To do this, open the platform or application project by selecting the required `CMakeLists.txt` file and configure the cache. In case of an application solution build, select the `CMakeLists.txt` file of the application solution. In case of a platform build, select the `CMakeLists.txt` file located in the root directory with the platform source code.\
283
-
The first build configuration with CMake may take too long to complete and fail with network errors. If network errors occur, please run the build configuration again.
284
-
285
-
1. Starting the build
286
-
287
-
Start the platform or application solution build. For more details on starting the build of projects, refer to the <a href="https://cmake.org/documentation/">CMake documentation</a> or the documentation of the integrated development environment being used.
288
-
289
95
## Trademark notices
290
96
291
97
Registered trademarks and service marks are the property of their respective owners.
@@ -307,6 +113,5 @@ This is an open source project. If you are interested in making a code contribut
Copy file name to clipboardExpand all lines: examples/mnist-client/README.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ The `visualize_network.cpp` program file contains implementations of the followi
87
87
*`draw_annotated_subgraph` function that draws a network graph with inscriptions for node names or IDs.
88
88
*`draw_subgraph` function that draws a connected subgraph.
89
89
*`make_reverse_list` function that creates a reverse adjacency list where each node has a list of nodes to which it is adjacent.
90
-
*`find_connected_set` function that fins an independent subgraph inside a network graph.
90
+
*`find_connected_set` function that finds an independent subgraph inside a network graph.
91
91
*`divide_graph_by_connectivity` function defined in the `visualize_network.h` file.
92
92
*`print_connected_subset` function that prints the description of a network subgraph.
93
93
*`print_network_description` function defined in the `visualize_network.h` file.
@@ -138,12 +138,9 @@ If you install the `knp-examples` package, the example binary file is located in
138
138
139
139
`$ mnist-client`
140
140
141
-
You can also build the example by using CMake. The example binary file will be located in the `/build/bin` directory. To execute the created binary file, run the following commands:
141
+
You can also build the example by using CMake. The example binary file will be located in the `build/bin` directory. To execute the created binary file, run the following commands:
0 commit comments