A "canonical" pyAEX-like module: lab streaming layer

[eneftci]

Hi everybody,

Those who has once looked into the pyAex modules remember that it is quite complex and at times difficult to understand and debug.

Recently, there was a talk here by one of the main programmers of BCIlab, a software project used for crunching EEG data. Interestingly, they have a layer called lab streaming layer that interfaces EEG signal acquisition hardware to their Matlab BCIlab interface.

The Lab streaming layer seems to be the perfect tool for replacing the AEX server and client:
http://code.google.com/p/labstreaminglayer/

But also the AMDA board communication.

It is compatible with linux, mac os, and Windows.

I'll try to get a toy ComAPI example soon.

E.

[fabioedoardoluigialberto]

I think it would be a perfect showcase for the API philosophy. Thanks!

2013/1/23 eneftci [email protected]

Hi everybody,

Those who has once looked into the pyAex modules remember that it is quite
complex and at times difficult to understand and debug.

Recently, there was a talk here by one of the main programmers of BCIlab,
a software project used for crunching EEG data. Interestingly, they have a
layer called lab streaming layer that interfaces EEG signal acquisition
hardware to their Matlab BCIlab interface.

The Lab streaming layer seems to be the perfect tool for replacing the AEX
server and client:
http://code.google.com/p/labstreaminglayer/

But also the AMDA board communication.

It is compatible with linux, mac os, and Windows.

I'll try to get a toy ComAPI example soon.

E.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12.

[sheiksadique]

It looks a little too facny(complicated). Are you sure it is worth the effort ? Ofcourse i haven't used it .. so i am only being skeptical.

PS: pyAEX / pyAMDA are only drivers and technically not part of pyNCS.

[eneftci]

The core of LSL is actually as simple to use as pyAex (see the example scripts). It takes care of all the mess of discovering the devices on the network with the proper (use-defined) ID. This means that we don't need to provide IP addresses anymore but specify for example 'setup zenzero', and the LSL will discover it on the network.

pyAex has its own host of problems (e.g. "blanks").

I know that the pyAex is not part of pyNCS, but an interface to a general purpose communicator like LSL would definitely add value to pyNCS. As Fabio points out it will be a good showcase.