OpenNN is a software library written in C++ for advanced analytics. It implements neural networks, the most successful machine learning method.
Some typical applications of OpenNN are business intelligence (customer segmentation, churn prevention…), health care (early diagnosis, microarray analysis…) and engineering (performance optimization, predictive maitenance…).
OpenNN does not deal with computer vision or natural language processing.
The main advantage of OpenNN is its high performance. This library outstands in terms of execution speed and memory allocation. It is constantly optimized and parallelized in order to maximize its efficiency.
The documentation is composed by tutorials and examples to offer a complete overview about the library.
OpenNN is developed by Artelnics, a company specialized in artificial intelligence.
Features
- Extensive documentation.
- Unit testing.
- Many examples.
Categories
Scientific/Engineering, Artificial Intelligence, Machine Learning, Computer Vision Libraries, Natural Language Processing (NLP)License
GNU Library or Lesser General Public License version 3.0 (LGPLv3)Follow OpenNN - Open Neural Networks Library
User Reviews
-
OpenNN is an advanced open source class library which implements neural networks. This library has been developed in C++ programming language so that, it has better memory management and higher processing speed. It is really recommended. I have used it for different type of projects and it has generated successfully models.
-
Excellent C++ library for designing neural networks for different type of problems. It also has a large amount for preproccesing the data and testing the methods.
-
Great library to perform every desired action with neural networks. It has a good design and a perfect flexibility and generality to create the model that each problem requires. Nice new version solving some bugs and improving the documentation.
-
Just started using OpenNN. I like the design of the library, but implementation of the API leaves something to be desired, as there is complete and utter confusion over whether ownership of objects being passed in and returned passes with the object or remains behind. It has cost me a lot of time burrowing through the source to figure out what it is in each case, and hence fix up the crashes you get when you get it wrong. Why do people code C++ this way? Did they cut their teeth on Java or some other gaebage collected language where every object is owned by the system? I'm happy to fix the API, or at least document it to make it usable, but it seems the code published on github lags the released 3.0 version available on SF FRS. Is this some guys private code repository?
-
No usable documentation available, just a few examples and you need to understand on your own how to use it. There are some other libs around that are a lot better, at least for my use.