BRIAN simulator

I Use This!

Inactive

Analyzed about 22 hours ago. based on code collected about 22 hours ago.

Project Summary

Brian is a simulator for spiking neural networks available on almost all platforms. The motivation for this project is that a simulator should not only save the time of processors, but also the time of scientists.

Brian is easy to learn and use, highly flexible and easily extensible. The Brian package itself and simulations using it are all written in the Python programming language, which is an easy, concise and highly developed language with many advanced features and development tools, excellent documentation and a large community of users providing support and extension packages.

In a Nutshell, BRIAN simulator...

...
has had 2,764 commits made by 12 contributors
representing 107,222 lines of code
...
is mostly written in Python
with a well-commented source code
...
has a well established, mature codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 28 years of effort (COCOMO model)
starting with its first commit in September, 2008
ending with its most recent commit over 2 years ago

Quick Reference

Project Links:

Homepage
Documentation
Download
Issue Trackers

Code Locations:

https://github.com/brian-team/brian

Similar Projects:

Managers:

Become the first manager for BRIAN simulator

Licenses

CeCILL Free Software License Agreement v2.1

Permitted

Forbidden

Required

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
in 2016, 47% of companies did not have formal process in place to track OS code
...
search using multiple tags to find exactly what you need
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog