Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface Enhancements #36

Open
uahic opened this issue Jan 31, 2017 · 1 comment
Open

Interface Enhancements #36

uahic opened this issue Jan 31, 2017 · 1 comment

Comments

@uahic
Copy link

uahic commented Jan 31, 2017

Hereby I would like to propose some minor changes to the interface;

@mdjurfeldt
Currently, there is no way to get info about the available ports in the config at an application which could be used to automatically instantiate it in a factory.

Use cases are any kind of plotting libraries/closed loop systems etc. But actually the info is available, its just accessible via an environment variable in a serialized format (a user library should not deal with that). Also info about the port type is missing. I think the port type should also be part of the config.

The second point is the Event callback for Event input ports. Would it be possible to make the buffer transparent to python or at least to have a callback that just returns two lists (times, senders) instead of one function call for each single spike? I guess this would be a great performance improvement!

For now I do all of this outside of MUSIC but it would be great if you agree on this and we can implement it at some point. Other features requests regarding the interface could also be linked here to develop an idea of how the interface in the next versions could look like.

@mdjurfeldt
Copy link
Contributor

mdjurfeldt commented Jan 31, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants