NeuralNetwork.NET | inspired neural network library built from scratch in C | Machine Learning library

by Sergio0694 C# Version: v2.1.3 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | NeuralNetwork.NET Summary

NeuralNetwork.NET is a C# library typically used in Artificial Intelligence, Machine Learning, Deep Learning, Pytorch, Tensorflow applications. NeuralNetwork.NET has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

NeuralNetwork.NET is a .NET Standard 2.0 library that implements sequential and computation graph neural networks with customizable layers, built from scratch with C#. It provides simple APIs designed for quick prototyping to define and train models using stochastic gradient descent, as well as methods to save/load a network model and its metadata and more. The library also exposes CUDA-accelerated layers with more advanced features that leverage the GPU and the cuDNN toolkit to greatly increase the performances when training or using a neural network. DISCLAIMER: this library is provided as is, and it's no longer being actively maintained. NeuralNetwork.NET was developed during a university course and it's not meant to be a replacement for other well known machine learning frameworks. If you're looking for a machine learning library for .NET to use in production, I recommend trying out ML.NET or alternatively TensorFlow.NET.

Support

Quality

Security

License

Reuse

Support

NeuralNetwork.NET has a low active ecosystem.

It has 501 star(s) with 73 fork(s). There are 33 watchers for this library.

It had no major release in the last 12 months.

There are 9 open issues and 15 have been closed. On average issues are closed in 123 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of NeuralNetwork.NET is v2.1.3

Quality

NeuralNetwork.NET has 0 bugs and 0 code smells.

Security

NeuralNetwork.NET has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

NeuralNetwork.NET code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

NeuralNetwork.NET is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

NeuralNetwork.NET releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of NeuralNetwork.NET

Get all kandi verified functions for this library.

NeuralNetwork.NET Key Features

No Key Features are available at this moment for NeuralNetwork.NET.

NeuralNetwork.NET Examples and Code Snippets

No Code Snippets are available at this moment for NeuralNetwork.NET.

Community Discussions

Trending Discussions on NeuralNetwork.NET

.NET Core Unit tests not shown in AppVeyor Tests window (and badge)

AppVeyor ignores explicit assemly name for Unit tests

Git showing unwanted folder that isn't there when cloning repo

QUESTION

.NET Core Unit tests not shown in AppVeyor Tests window (and badge)

Asked 2018-Nov-15 at 07:17

Follow up from this question, I'm currently setting up AppVeyor for my project (here) and my .NET Core tests are only shown in the console output but not in the Tests window.

This is the link for the AppVeyor project: ci.appveyor.com/project/Sergio0694/neuralnetwork-net

If some tests fail, the console correctly shows an error and the build is marked as failing, but the Tests window is empty anyways. Same goes for the badge from shields.io which shows 0 total tests, even if I can see many of them being executed from the console output.

Here's the console output:

And here's the Tests window:

Is there something else I have to setup in order for them to be reported correctly outside the console window?

...

ANSWER

Answered 2018-Apr-05 at 10:33

You can add the AppVeyor.TestLogger package to your project, but it can be done without changing your code. You need to output your tests results into an xml file format that AppVeyor understands and then upload it to their HTTP API. The following powershell snippet will iterate through your solution and find each test project, call dotnet test on the csproj and log the output to test-result.trx and then upload the file to AppVeyor.

Source https://stackoverflow.com/questions/48235374

QUESTION

AppVeyor ignores explicit assemly name for Unit tests

Asked 2018-Jan-13 at 00:02

I'm trying to setup AppVeyor for my project (here) and I can't seem to find a way to only have it run tests from the .NET Core Unit test project.

This is the link for the AppVeyor project: ci.appveyor.com/project/Sergio0694/neuralnetwork-net

I also have a .NET Framework Unit test project that executes some GPU-based tests, so they just fail when run with AppVeyor as they're missing both a CUDA GPU and the required cuDNN files.

This is my configuration:

...

ANSWER

Answered 2018-Jan-12 at 21:08

.NET Core tests detection works differently than detection of classic .NET Framework tests. When searching .NET Core tests, AppVeyor look for .csproj files with certain properties, not for assemblies. Assembly filter does not work for .NET Core tests (Categories filter works though).

Sorry for confusion. Created this issue to implement behavior similar to assembly name filtering, but based on .csproj file names for .NET Core tests auto-detection.

For now workaround is to do a "black list", e.g. list all .NET Framework assemblies you do not want to run under assemblies/except. You can use wildcard syntax to make it more compact as described here.

Source https://stackoverflow.com/questions/48233210

QUESTION

Git showing unwanted folder that isn't there when cloning repo

Asked 2017-Dec-23 at 22:09

I'm working on a repo on GitHub and I'm seeing an odd behavior, I'm probably missing something here. When I open the repo on the website, I see an "APIS" folder that isn't supposed to be there:

The only folder should be the "APIs" folder. If I clone the repo, that "APIS" folder isn't actually there (as I remember renaming it a while ago, even if it's still there on the website).

So, my questions are:

Why is it that I'm not seeing that erroneous "APIS" folder when cloning the repo, even though I see it on the website?
How do I get rid of that folder and merge the contained files into a single "APIs" folder, just like I have on my PC after cloning the repo?

If it helps, this is the link to the repo: https://github.com/Sergio0694/NeuralNetwork.NET/tree/master/NeuralNetwork.NET.Cuda

Thanks for your help!

...

ANSWER

Answered 2017-Dec-23 at 22:09

You are on Windows. And Windows treats APIs and APIS the same. So git is overwriting your APIS folder on checkout with APIs.

See: File paths in Windows environment not case sensitive?

To get rid of the folder you will need to checkout the folder on Linux (or an OS without this behavior), and then delete the folder there.

I cloned it on Linux, and it had both folders. You might also try Windows Bash prompt which uses Windows Subsystem for Linux, and it also has the case sensitive behavior you need (which I also verified). Just install git inside the Ubuntu Bash Windows Shell, via sudo apt-get install git.

Source https://stackoverflow.com/questions/47956316

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install NeuralNetwork.NET

The NeuralNetwork.NET library exposes easy to use classes and methods to create a new neural network, prepare the datasets to use and train the network. These APIs are designed for rapid prototyping, and this section provides an overview of the required steps to get started.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: