jAER discussions moved to Google Groups

Luca Longinotti — Tue, 05 Sep 2017 10:32:36 -0000

After moving all our code to GitHub, it became necessary to find a good replacement for the SourceForge discussion forums. To also support easy e-mail announcements, as well as a good mailing-list and web-interface integration, we decided to use Google Groups.
The following new groups are available:

https://groups.google.com/d/forum/jaer-users (for jAER support)
https://groups.google.com/d/forum/caer-users (for cAER and libcaer support)
https://groups.google.com/d/forum/davis-users (for DAVIS, DVS and eDVS support)
https://groups.google.com/d/forum/dynapse-users (for Dynap-SE support)

This covers all of our software, as well as hardware.
Announcements will be cross-posted as needed.
Subscription is open to everyone.
We encourage you to subscribe to all lists that apply to you!

jAER migrated to GitHub

Luca Longinotti — Wed, 24 May 2017 17:38:51 -0000

The jAER SVN repository has been switched to read-only and will continue to exist only for historical reasons.
Please use the new GitHub Git repositories, which can be found at:
- jAER/trunk/ is now https://github.com/SensorsINI/jaer
- scripts/ is now https://github.com/SensorsINI/processAEDAT
- devices/ has been split up, iniLabs supported devices can be now fond at https://github.com/inilabs/devices-bin and Sensors group devices at https://github.com/SensorsINI/devices
- utils/jaerfx2 is now https://github.com/inilabs/jfxaer
Please use these locations to report bugs too, using the GitHub Issues system.
If you want to send us code changes, either attach diffs to tickets or directly send us pull requests!

Some tips for new Git users:
For Windows users, install Git For Windows https://git-scm.com/download/win and then TortoiseGit as client https://tortoisegit.org/, it also has some useful documentation available at https://tortoisegit.org/docs/tortoisegit/.
Remember to always set your name and e-mail address correctly in your Git client! You can then create a user on GitHub and associate those e-mail addresses to it, as Git(Hub) tracks commits by e-mail.

libcaer, cAER, Flashy migrated to GitHub

Luca Longinotti — Tue, 10 May 2016 12:48:39 -0000

The libcaer, cAER and Flashy repositories have been migrated from SourceForge.net Subversion to Git, under GitHub. The repositories can now be found at the following URLs:
libcaer - https://github.com/inilabs/libcaer
cAER - https://github.com/inilabs/caer
Flashy - https://github.com/inilabs/flashy
Please use these locations to report bugs too, using the GitHub Issues system.
If you want to send us code changes, either attach diffs to tickets or directly send us pull requests!
The rest of the jAER repository may be moved in the future, though there are no definitive plans yet.

jAER 1.5: major DAVIS configuration backend update

Luca Longinotti — Wed, 27 Jan 2016 12:46:39 -0000

As of 27.01.2016, the davisconfig_rewrite/ branch of jAER 1.5 was merged back into trunk.
The purpose of this branch was to simplify and unify the configuration backend for all new DAVIS devices and other derivatives, so that all device configuration options could be exposed to the user (like it is done in cAER). This affects only the "Hardware Configuration" tab/window for DAVIS chips, reorganizing the options therein and adding new ones, such as the "External Input" tab or new APS related options.
The change required a migration of all hardware bias configuration files for the affected chips (for customers, this currently means DAVIS240 only), which was done for all files included in the biasgenSettings/ sub-folder. It is possible not all settings have been migrated correctly or jAER might not pick them up until you reload the bias file. If you have your own bias files, just try to load them and then check each option (especially the current biases) manually, re-set anything that looks wrong and save the file again.

libcaer 1.0.2 released

Luca Longinotti — Wed, 27 Jan 2016 12:11:42 -0000

libcaer 1.0.2 was released on 08.01.2016. It contains various bug-fixes and is required for the newest cAER versions that can be found in our Subversion repository. For more information, please read the ChangeLog file incuded in the archives.

libcaer 1.0.0 released

Luca Longinotti — Sat, 03 Oct 2015 12:35:13 -0000

libcaer 1.0.0 has been released and can be found in our Subversion repository under libcaer/trunk/.
libcaer is a simple and minimal C library that enables low-level access to our DVS128 and DAVIS devices and provides definitions for an efficient in-memory event and event packet format.
It was created out of the recognized wish from many of our customers to be able to access the devices in C or C++, without having to rely on the full cAER framework, and instead use their own software systems to process the incoming data.
cAER itself will be modified to use libcaer for low-level device access. The new in-memory event format that libcaer introduces is incompatible with the cAER one, as it improves various aspects of it. The cAER format was never final and will change accordingly with the migration to libcaer.
Documentation can be found for now in the form of examples in the examples/ directory and the README files.

Misha Mahowald Prize for Neuromorphic Engineering

Sim Bamford — Wed, 12 Aug 2015 14:04:35 -0000

This will be of interest to many people who actively work with jAER: a new prize has just been launched to recognise outstanding reasearch in Neuromorphic Engineering. The deadline for submissions is the end of the year and the prize is 3000 USD: www.mahowaldprize.org

SVN restructuring

Luca Longinotti — Tue, 07 Oct 2014 13:29:35 -0000

To clean-up old projects and address the situation of multiple projects (jAER, cAER, Flashy) calling the main jAER Subversion repository home, a significant restructuring of said repository has taken place.
Mostly only users of jAER will be affected by the move.
jAER 1.5 is now located at https://svn.code.sf.net/p/jaer/code/jAER/trunk/ and both biasgen and filter settings are now part of its directory structure, so that biases and settings are always directly available.
If you have a full jAER SVN checkout (recommended, URL https://svn.code.sf.net/p/jaer/code/), then just updating fully and re-adding the jAER project from its new location should be enough. If you have a separate checkout of jAER only, please check it out again from the above location.

Project web presence updated

Luca Longinotti — Wed, 26 Jun 2013 12:36:42 -0000

Wiki

The jAER web resources were fully migrated from Trac to the new SourceForge Allura platform. This mainly affects the wiki.
The old Trac wiki doesn't exist any more, please use the new one at:
https://sourceforge.net/p/jaer/wiki/
Links to the old system, such as jaer.sf.net or jaer.wiki.sourceforge.net, automatically redirect you to the new address.

Mailing Lists

The jaer-general mailing list was deleted, it was decided to only use the already present discussion forums on SourceForge for helping users (Help forum) and giving developers the possibility to openly discuss changes (Developers forum).

A new mailing list, called jaer-announce, was instead created as an easy means to reach all users; to announce big upcoming changes and other important events.
If you're using or interested in jAER, we urge you to subscribe right away!

Tickets

We've introduced tickets as a means to track bugs and feature requests, especially if long-term or coming from external sources.

jaerproject.net jaerproject.org jaerproject.ch domains

Tobi Delbruck — Fri, 29 Mar 2013 06:13:26 -0000

jAER has its own domain names now. These point to the jAER wiki and should be used for citations, e.g. "jAER project. (2007) Available: http://jaerproject.net"

Recent posts to news